Search Issue Tracker
Third Party Issue
Votes
0
Found in
2019.4
2020.3
2021.2
2022.1
2022.2
2022.2.0a1
Issue ID
1399653
Regression
No
Shader compiler outputs wrong shader code when entering Play Mode
Reproduction steps:
1. Open the attached project "GreenRed.zip"
2. Go to Assets > Scenes > "SampleScene"
3. Enter Play Mode
Expected result: The game view flashes between green and red tones
Actual result: The game view flashes between black and white tones
Reproducible with: 2019.4.35f1, 2020.3.27f1, 2021.2.10f1, 2022.1.0b6, 2022.2.0a3
Add comment
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
Resolution Note:
Unfortunately this is a bug in the FXC which is a closed source compiler from Microsoft so there is nothing we can do about it.
There seems to be some confusion with optimizing the literal values in the calculations which means the issue can be worked around by refactoring the code a bit.