Search Issue Tracker
By Design
Votes
0
Found in
2020.1.0a8
Issue ID
1194810
Regression
No
Terrain geometry detail is permanently lost when switching to lower heightmap resolution
Steps to reproduce:
1. Download and open the attached TerrainHeightmapBug project
2. Select the Terrain game object
3. Go to Settings and set Heightmap Resolution to anything lower than 4097x4097
4. Notice the reduction in detail (this is intended)
5. Now switch back to the original Heightmap Resolution of 4097x4097
6. Notice that the terrain geometry detail is permanently lost
Notes:
- This issue is fixed by re-importing terrain heightmap again
- Tested in Unity 2020.1.0a8 on a Windows machine
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Unfortunately that is a limitation of the existing Terrain system.
We are working on the new DOTS based Terrain rendering system, which separates the edit-time representation from the run-time representation, and so doesn't suffer from this problem.
We don't intend to fix this in the existing Terrain system though.