Search Issue Tracker
By Design
Votes
0
Found in
2021.3.36f1
2022.3.21f1
2023.2.13f1
2023.3.0b10
Issue ID
UUM-65770
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“
3. Observe the Game View
Expected result: The “Terrain_Amplify” GameObject is solid and does not have any holes
Actual result: The “Terrain_Amplify“ GameObject has pixel sized holes
Reproducible with: 2021.3.36f1, 2022.3.21f1, 2023.2.13f1, 2023.3.0b10
Reproducible on: Windows 11 (GTX 1650 (Laptop)), macOS 14.1.1 (M2 Max) (By user)
Not reproducible on: No other environment tested
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
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