Search Issue Tracker
Fixed in 5.0.1
Votes
0
Found in
5.0.0a19
Issue ID
623708
Regression
No
SpeedTree example tree's LOD values do not match observed LOD thresholds
The Unity User's Manual states that the percentage settings in a LODGroup component in the Inpsector represent the fraction of the view frustum depth where that LOD level becomes active. However, these values do not match observed distances when moving a SpeedTree asset in Game view and noting the distances where its LOD states toggle.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Missing Render Feature "Full Screen Pass Render Feature" in any “Universal Renderer Data” asset when upgrading from 2022.3
- Inconsistent ParticleSystemVertexStream.PercentageAlongTrail data range in Trail Texture Modes except "Stretch"
- The Graph Debug Window can be right clicked through and the Node Workspace is manipulated instead
- [Linux] Top left corner of the screen is unresponsive when the Editor recompiles
- [Android] [Vulkan] Cubes stuck on the first few frames of rotation and application flickering when an Overlay Camera is added to the Camera Stack with MSAA enabled
Add comment