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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.