Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.2.0a2
2018.2.5f1
Issue ID
1074421
Regression
Yes
Details are lost too early for Terrain Trees in VR
Steps to reproduce:
1. Download and open the attached project
2. Enter Playmode with VR enabled
3. Observe Game View
Expected result: all trees are fully rendered
Actual result: trees further away lose detail even though they are not far enough away
Reproduced on 2018.2.a2, 2018.2.6f1, 2018.3.0a10
Not reproduced on 2018.1.9f1, 2018.2.0a1
Regression introduced in 2018.2.0a2
VERFIED Fixed 2019.1.0a6
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