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
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Resolution Note (fix version 2021.1):
Fixed in: 2021.2.0a1