Troubleshooting

intermediate troubleshooting

Grids 2D · Troubleshooting & FAQ

Troubleshooting

This page covers the most common issues users encounter with Grids 2D and how to resolve them.

Grid not visible in the scene

SymptomYou added the Grids2D prefab but no grid appears.
CauseThe camera may not be facing the grid plane, or the grid is hidden.
Solution
  1. Select the Grids2D GameObject and press F in the Scene view to frame it.
  2. The grid renders on the XY plane. Ensure your camera looks down the Z-axis (for 2D) or is positioned appropriately.
  3. Check that Hide Objects is not enabled in the Inspector.
  4. Verify the prefab was dragged from Grids2D/Resources/Prefabs.

Cells not highlighting on hover

SymptomMoving the mouse over the grid does not highlight cells or territories.
CauseSelection mode is set to None, or a UI element is blocking input.
Solution
  1. Set Selection Mode to Cells or Territories in the Grid Behavior section.
  2. If Respect Other UI is enabled, ensure no uGUI Canvas element is covering the grid area.
  3. Confirm the correct Camera is assigned (or left blank for main camera).

Slow performance with territories enabled

SymptomNoticeable lag when the grid is created or during runtime with territories active.
CauseTerritory mesh generation is expensive with high cell counts.
Solution
  1. Reduce the number of cells or territories.
  2. Disable Show Territories and Colorize Territories if not needed.
  3. Pre-warm the geometry at load time using the API to avoid runtime lag.
  4. Ensure Internal Territories is disabled unless you specifically need enclave detection.

Voronoi grid looks different each time

SymptomThe Irregular (Voronoi) grid generates a different layout on each play.
CauseThe randomization seed is not fixed.
Solution
  1. Set a fixed Seed value in the Grid Configuration section.
  2. Using the same seed guarantees identical cell layouts across plays.

Pathfinding returns unexpected results

SymptomFindPath() returns null, an empty list, or a non-optimal path.
CauseCells may be blocked, the cost limit is too low, or the wrong algorithm is selected.
Solution
  1. Verify that cells on the desired path have canCross = true (use CellSetCanCross()).
  2. Increase Max Search Cost and Max Steps.
  3. Try a different AlgorithmEuclidean typically gives the best results.
  4. Check cell groups: FindPath() can accept a group mask to filter traversable cells.

Textures on cells appear distorted

SymptomTextures assigned to cells look stretched or warped.
CauseCell shapes (especially Voronoi) are irregular, causing UV mapping issues.
Solution
  1. Use Box or Hexagonal topologies for more uniform UV mapping.
  2. For Irregular topology, increase the Relaxation level to create more regular cell shapes.
  3. Use the Canvas Texture feature for seamless texturing across the entire grid.

Still stuck?

If your issue is not listed here, visit the Kronnect Support and post your question. The team typically responds within 24 hours.

Was this page helpful?