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
- A black bar appears on the Game View toolbar when the Game View is resized vertically
- Double separation lines are present in Override Controls in a DefaultVolumeProfile Asset
- Silent crash when multiple child GameObject Colliders are triggered while attached to a Parent GameObject with Transform Scale set as (0; 0; 0)
- Numbers of output expressions does not match number of output error is thrown when converting node to property Output
- GameObjects with higher Render Queue values are being reflected on GameObjects with lower Render Queue values
Resolution Note (fix version 2021.1):
Fixed in: 2021.2.0a1