Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
2
Found in
2018.4
2019.3.13f1
2019.4
2020.1
2020.2
Issue ID
1256992
Regression
No
Terrain trees are not being culled by the camera's view transform therefore having the same lower performance
How to reproduce:
1. Open attached project "Tree perf (HDRP).zip" and scene "TEST_SCENE"
2. Enter Play mode
3. In Profiler window, observe "PrepareSceneCullingParameters"
Expected result: PrepareSceneCullingParameters is more performant when the camera is not looking at the terrain
Actual result: camera view does not matter, the performance is the same
Reproducible with: 2018.4.24f1 (LWRP 4.10.0-preview), 2019.4.2f1(7.3.1, 7.4.1 HDRP and URP), 2020.1.0b14, 2020.2.0a15 (URP 8.1.0, 9.0.0-preview.14, HDRP 8.1.0, 9.0.0-preview.13)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment