Search Issue Tracker
By Design
Votes
0
Found in
2021.3.34f1
2022.3.17f1
2023.2.5f1
2023.3.0b1
Issue ID
UUM-60690
Regression
No
Terrain surface has holes when its height is increased significantly
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/SampleScene“ Scene
3. Observe the Game view
Expected result: The Terrain GameObject is solid and does not have holes
Actual result: The Terrain GameObject has small holes
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.5f1, 2023.3.0b1
Reproducible on: Windows 11 (GTX 1650 (Laptop))
Not reproducible on: Windows 10 (Radeon RX 6800XT)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The hlsl Precise keyword must be used in shaders when leveraging tessellation to ensure that the resulting mesh is watertight. Precise positions and tessellation factors will ensure that different executions of each stage of the shader do not result in floating point differences resulting in gaps in geometry