Search Issue Tracker
Fixed in 2021.1.X
Votes
1
Found in
2017.4
2019.3.12f1
2020.2
Issue ID
1244606
Regression
No
Terrain's 'Pixel Error' value has no effect when Orthographic Camera's Near Clipping Plane is set to zero
How to reproduce:
1. Open the "1244606_TerrainPixel" project
2. Enter Play Mode (Make sure Statistics are showing in Game view)
3. Select the Terrain GameObject and change the Pixel Error property between 1 and 100 in Terrain Settings
4. Observe the Tris value in the Statistics window in the Game view as you adjust the Pixel Error
5. Select the Main Camera GameObject, set Near Clipping Plane to 0 and repeat the 3-4 steps
Expected result: Tris value is changing accordingly
Actual result: Tris value is not updated
Reproducible with: 2017.4.40f1, 2018.2.23f1, 2019.3.13f1, 20201.0b9, 2020.2.0a11
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2021.1):
Fixed in: 2021.2.0a1