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
- [iOS] [Android] External library generics fail during IL2CPP build
- Animator State’s Multiplier field shows a Parameter that no longer exists when the Parameter was assigned and then deleted
- Shadows disappear and come back after couple frames when using OnDemand Shadows and OnDemand Reflection
- “Delete Selected Items” is still active in the menu when Label is not selected in New Sprite Library Asset window
- "View Generated Shader" button in Shader Graph Asset is not aligned with other buttons
Add comment