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
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
- [HDRP] Volumetric cloud shadows disappear when there is no directional light shadows
- “Selector” column names in the Search window are lowercase when added
- Install List Project Counter Panel can be right clicked through and Install Context Menu can be opened disabling Project Counter Panel's buttons
- [MacOS] Scene is marked/flickering as dirty (with asterisk) when dragging a Material on a GameObject in Scene view
Add comment