Search Issue Tracker
Duplicate
Votes
0
Found in
5.2.0p1
Issue ID
728201
Regression
No
[Shader] Using small/large float numbers in property block breaks shaders
POSTPONED: I think this will be solved when we'll switch to binary shader serialization. For now, I guess avoid specifying too large/small numbers as default property values. Materials actually having these values are fine, just the defaults in shader text are not...
A shader that has very small or large floating-point number literals in its property block doesn’t work on the player.
Repro:
For example, a shader with the following property turns pink when built.
_Foo("Foo", Float) = 0.0000001
_Bar("Bar", Float) = 1000000
Note that it works on the editor. It seems to get broken when building player.
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