Search Issue Tracker
Fixed in 4.5.X
Votes
0
Found in
4.3.0f4
Issue ID
576855
Regression
No
The built-in EncodeFloatRGBA() and DecodeFloatRGBA() functions contain a typo that leads to reduced precision.
The built-in EncodeFloatRGBA() and DecodeFloatRGBA() functions contain a typo that leads to reduced precision.
The problem involves the number 255^3, which equals 16581375, not 165081375. I assume the extra "0" is a typo.
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