Property Spacing
- Namespace
- GrindFest
- Assembly
- GrindFest.dll
Spacing
Marker gap ceiling: one MapMagic tile, in metres. The widest a gap between two markers may be, and the unit the callers measure their distances in.
public float Spacing { get; }Property Value
Remarks
Derived, never authored, and that is the point. Until 2026-09-15 the spacing was a hand-set 41 while the tile is 128 m, so all 9 markers collapsed into 3 tiles - measured LOADED-TILES = 3 - while the camera's ground footprint is 211 x 212 m. Re-baking the SAME 9 markers at 128 took it to 10 tiles and 9 distinct coords in a clean 3x3, and the four frustum corners went from "no terrain under 4 of 5 rays" to terrain under 4 of 5. No new GameObjects.
It matters in both directions. A gap narrower than a tile is redundant but harmless - two markers in one tile just deploy that tile once - which is why the square is filled with more markers than it has tiles. A gap wider than a tile is worse than wasteful: the scene runs with tiles.generateRange = 0, so MapMagic deploys only the tiles that hold a marker, and every tile between two markers is skipped without a word.