Troubleshooting

intermediate troubleshooting

This page covers the most common issues users encounter with Hexasphere Grid System and how to resolve them.

Symptom	You added a Hexasphere but nothing appears in the Game or Scene view.
Cause	The hexasphere may be behind the camera, too small, or obscured by other objects.
Solution	Select the Hexasphere GameObject and press F in the Scene view to frame it. Check the Transform scale — ensure it is not set to zero. Verify the camera is positioned to see the hexasphere (the default sphere has a radius of 0.5 world units). Ensure no other objects are blocking the view.

Symptom	Moving the mouse over the hexasphere does not highlight any tile.
Cause	Highlighting is disabled, or the collider/raycast is not configured correctly.
Solution	In the Inspector, confirm Enable Highlight is checked. Ensure a Collider component exists on the Hexasphere (it is added automatically). If using extrusion, enable Raycast 3D in the Inspector for accurate detection on extruded tiles. Check that EventSystem is present in your scene if using UI overlays.

Symptom	FPS drops significantly when increasing the Divisions parameter.
Cause	High division counts create exponentially more tiles, increasing geometry and draw calls.
Solution	Use the minimum number of divisions that meets your visual requirements. Avoid enabling Smart Edges with very high division counts if you do not need the feature. If using extrusion, keep Raycast 3D disabled unless required for accurate selection. Use `Hexasphere.SetTileColor()` in batches rather than individual calls in tight loops.

Symptom	Extruded tiles show gaps, z-fighting, or incorrect gradients.
Cause	Extrusion multiplier too high, or conflicting shader settings.
Solution	Reduce the Multiplier value. Very large values can cause visual issues at tile edges. Ensure the camera near/far clip planes are reasonable for your scene scale. Try toggling Gradient Intensity — sometimes reducing it eliminates side-face artifacts.

Symptom	Tile selection does not work in VR mode.
Cause	VR raycasting is not enabled or the VR SDK integration is missing.
Solution	Enable the VR Enabled checkbox in the Hexasphere Inspector. If using specific VR SDKs (Google VR, Samsung Gear), uncomment the corresponding define in `HexaspherePriv.cs` (see VR Options). Ensure your XR plugin (OpenXR, Oculus, etc.) is properly configured in Project Settings.

Symptom	`FindPath()` returns `null` even though start and end tiles exist.
Cause	Tiles may be blocked, the search limit is too low, or the cost exceeds the maximum.
Solution	Check that neither the start nor end tile has `canCross = false`. Increase the Search Limit in the Inspector. If using extrusion costs, verify that the extrusion weight is not creating impassable barriers. Use `FindPath(startIndex, endIndex)` with valid tile indices (check `tiles.Length`).

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? |