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
- Editor freezes after some time when using NavMeshQuery::Raycast
- Cube is rendered green when its color is set to black and using the Lift Gamma Gain Volume interpolation
- Inner and outer exceptions are not unrolled correctly
- [iOS][WebGL] Audio Clip doesn't play when Load Type is set to Decompress On Load and iOS Silent Mode is enabled
- Crash on EditorBuildSettings::GetConfigObject when closing a specific project
Add comment