Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.44f1
2021.3.16f1
2022.2.2f1
2023.1.0a25
Issue ID
UUM-22916
Regression
No
[mobile] The shape of a Terrain differs when using Draw Instanced with default Shader precision model
How to reproduce:
1. Open the attached Project "TerrainInstancing" with iOS or Android as the Build Target
2. Open the Scene "SampleScene"
3. Enter Play Mode
4. In the Game View, switch between "Draw Instanced" using the Buttons on the screen
5. Compare the shape of the Terrain with both options
Expected result: the shape of the Terrain remains the same
Actual result: the shape of the Terrain differs
Reproducible with: 2020.3.44f1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a25
Reproduced on:
- MacOS Editor (Intel); iOS Build Target
- MacOS Editor (Intel); Android Build Target
Did not reproduce on:
- MacOS Editor (Intel); Standalone Build Target
Notes:
- Changing the Shader precision model makes the issue no longer reproducible
Comments (1)
-
gilley033
Dec 17, 2025 23:10
Still a problem on Unity 6000.3.0f1.
This reads as "we won't fix it because it's too hard." Really disappointing take to be honest with you.
It would be fine if you were working on some kind of overhaul of the Terrain System, however that doesn't seem to be the case. So why wouldn't you fix such a crucial issue?
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:
This issue is deep within the Terrain system and we will not be able to address it without a major rewrite. Due to the complexity and risk associated with that we will be marking this as won't fix.
However, you can work around this problem by lowering your Terrain Height variable in the Terrain Settings > Mesh Resolution. The lower you set the range, the more precise you modifications should become.
Resolution Note (2023.1.X):
This issue is deep within the Terrain system and we will not be able to address it without a major rewrite. Due to the complexity and risk associated with that we will be marking this as won't fix.
However, you can work around this problem by lowering your Terrain Height variable in the Terrain Settings > Mesh Resolution. The lower you set the range, the more precise you modifications should become.