FAQ

For hexagonal and box grid types, use tgs.gridScale *= 2; to double the size of cells. Setting cellSize to a Vector2 will calculate the correct gridScale automatically. Note: this does not work for irregular grid types.

Ensure your terrain GameObject has a scale of (1,1,1) rather than (2,2,2), as non-unit scales can cause rendering issues. Also verify you're using the latest version of TGS. If the grid still doesn't cover the entire terrain properly, use the reset buttons in the inspector to reset the center and scale, or ensure the terrain mesh resolution is set appropriately (greater than the base 1000x1000).

Use tgs.CellGetAtPosition(position, worldSpace: true) to get a cell at a specific position, tgs.CellGetPosition(cellIndex) to get the position of a cell, and tgs.terrain.GetInterpolatedHeight(worldPosition) to get the height at a world position.

Call the CellGetGameObject() method passing the cell index you want. The surface is created dynamically if needed and returned by that method. Reference the terrain grid system object and use this method in your scripts.

CellDestroyBorder should only remove custom borders and not affect the general cell borders, which are rendered as a single mesh for all cells rather than per-cell. If the regular borders disappear after calling CellDestroyBorder, this may indicate an issue. Check the console for errors. As a workaround, ensure the grid has been drawn at least once before calling CellDestroyBorder (the issue only occurs if the grid hasn't been drawn previously).

Check if the 'Respect Other UI' option is enabled, as a canvas might be blocking interaction. If that doesn't work, test the grid in an empty scene to isolate the issue. If it works in an empty scene but not in your main scene, verify you have selected the correct camera for the grid.

To have an outline around districts, create a territory and assign the cells to it. Alternatively, if you don't need an outline, you can toggle cell colors or textures to visually distinguish districts or groups without using territories.

maxSearchCost limits the total path length based on crossing costs. It returns paths where the sum of all cell crossing costs does not exceed the specified value. By default, each cell has a crossing cost of 1, so maxSearchCost: 3 returns paths of maximum length 3. If no path exists within that cost limit, it returns null.

The callback should return only the *additional* cost, not the base cost. The base crossing cost of a cell is already factored in by the pathfinding algorithm. Only return extra cost on top of that (for example, penalties for difficult terrain or obstacles).

Use a partial class in C#. Create public partial class Cell : AdminEntity { } in a new file. Partial classes allow code to be split across multiple files, so your custom code in separate files won't be replaced when you upgrade TGS.

Instead of directly extending Cell with public abstract class Cell, create an intermediate class that inherits from Cell: public abstract class NewCell : Cell { }. This preserves access to all original Cell properties and methods while allowing you to add custom functionality.

Use the 'Mesh/Cell Offset' sliders in the inspector to adjust the depth position of the grid lines. These sliders raise the lines up to render above the terrain surface, preventing them from appearing below it.

The method uses collider or renderer bounds (which are axis-aligned). With checkAllVertices=false, it only checks if the center of cells is inside the bounds. With checkAllVertices=true, it checks if any vertex of the cell is within bounds. If you're getting unexpected results, verify your colliders are correct, as corrupted colliders (e.g., from copying objects between interfaces) can cause this behavior. You can also use the padding parameter to expand or reduce the bounds size.

When enabling Regular Hexes, the asset computes the scale automatically and lets you specify the hex width. Changing to another topology or disabling regular hexes doesn't automatically restore the scale to default (1). You can manually reset the scale by clicking the 'Reset' button next to the Scale field.

Disable the Mesh Generation option in TGS settings. This will invalidate input handling as well, allowing the asset to run properly in server-only mode without requiring mouse input or shader resources.

The minimum and maximum altitude filters hide cells outside of the range by not generating meshes for them, though the cells are still internally generated. The cell.visible property will be false for filtered cells.

Disable the 'Include Invisible Cells' option in the inspector to ignore invisible cells during pathfinding. Note that this will return a cell-based line rather than a continuous path.

The clearance option ensures there is space of x cells on either side of the path, but it does not make the path itself wider. If you need a path that is 2 cells wide, consider widening the grid resolution instead.

Make sure you're passing different seed values to the Voronoi generation. Additionally, check if relaxation is enabled - try setting relaxation to 0 if cells are too similar. Also ensure the Voronoi data is not baked; clear any baked data first so the grid regenerates based on the random seed.

Move your custom attribute initialization and coloring code from Awake to the Start method instead. TGS may not have finished generating the grid during Awake, so using the API in Start ensures the grid is fully initialized before your code attempts to access or modify cells.

The visibleByRules property controls visibility based on grid settings (altitude, slope, height difference, etc.). To override this for specific cells, you need to save the visibility state of individual cells to a data structure (such as a dictionary or custom serializable class) and restore it when the scene loads. Disable the altitude rules if you want manual control, then programmatically set cell.visible for the cells you want to show and persist this data outside the grid system's automatic rule evaluation.

Probably not, since edges are shared between territories. To ensure a position falls within a cell belonging to the territory, you can add a tiny shift towards the center of the territory. Alternatively, get all cell centers in the territory to which the vertex belongs, find the nearest one to the vertex point, and scale the vertex position towards that cell center.

The grid is a world-space mesh and doesn't automatically scale with camera changes. For 2D orthographic cameras, use the FitToScreen() method: grid.FitToScreen(cam, margin, keepAspectRatio). Alternatively, manually adjust the grid size and center using: float height = cam.orthographicSize * 2f; float width = height * cam.aspect; grid.SetSize(new Vector2(width, height)); and then reposition the grid center to match the camera position.

Please visit the Support Center and use our AI Support Assistant to get answers. If the issue persists, submit a reproduction project so we can investigate further and help you.