Common Issues
1-"Failed to load RDSTLayerData from Resources" : ' Console error showing failed to load RDST asset'
Problem: RDST Layer Data asset not found
Solutions:
- ✓ Verify asset is in a `Resources` folder
- ✓ Check path in script matches asset location
- ✓ Use `Resources.Load<RDSTLayerData>("path/to/asset")`
2-"RDST: No layer data found" : Console warning about no layer data
Problem: RDST Layer Data not assigned to preferences
Solutions:
- ✓ Assign RDST asset in GIS Terrain Loader window
- ✓ Check `Prefs.RDST_layerData` is set in script
- ✓ Verify Texture Mode is `RasterDrivenSplatmaps`
3-Terrain Generated but No Layers : Terrain Inspector showing empty Terrain Layers section
Problem: Classification data not properly read or applied
Solutions:
- ✓ Check GeoTIFF file path is correct
- ✓ Verify classification codes in raster match RDST config
- ✓ Check Console for RDST processing messages
- ✓ Ensure textures are assigned in RDST Layer Data
4-Wrong Textures Applied : Terrain with incorrect texture placement
Problem: Mismatch between classification codes and raster data
Solutions:
- ✓ Open raster in QGIS to verify classification values
- ✓ Check classification codes in RDST match raster values
- ✓ Use classification display to click terrain and verify codes
5-Classification Display Not Working
Problem: Label doesn't appear when clicking terrain
Solutions:
- ✓ Check Console for "Classification display system initialized!" message
- ✓ Verify terrain has TerrainCollider component
- ✓ Ensure Main Camera is tagged "MainCamera"
- ✓ Check RDST Layer Data is assigned to display script
6-Performance Issues, Slow Generation: Progress bar showing slow RDST processing
Causes & Solutions:
- High alphamap resolution → Reduce to 1024 or 512
- Large terrain size → Split into multiple tiles
- Complex blending → Reduce blur radius
7-Memory Issues
Causes & Solutions:
- Multiple large terrains → Generate sequentially
- High resolution textures → Use compressed formats
- Too many terrain layers → Combine similar classifications