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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment