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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment