Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.1.0a19
2023.2.0a1
Issue ID
UUM-21613
Regression
No
Different decimal point placement between Terrain Overlay and Terrain Inspector
Steps to reproduce:
- Create a Terrain
- Set brush opacity to some non 0 value
- The Overlay fits the value into the range of 0-1 while the Inspector fits it into 0-100
Expected result: both fields have the same range of values
Actual result: the fields have a different range of values
Reproducible with: 2023.1.0a19 and up
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
- 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
Resolution Note:
Too minor of an issue for us to address