Search Issue Tracker
Active
Votes
0
Found in
2021.3
2021.3.0f1
2022.1
2022.2
Issue ID
1420375
Regression
No
Shader.SetGlobalInteger does not work when used with Compute Shaders
Reproduction steps:
1. Open the attached project "setGlobalInteger-bug.zip" and load Scene "SampleScene"
2. Enter Play Mode
3. Observe the Game View
Expected result: The Game View is not black
Actual result: The Game View is completely black
Reproducible with: 2021.3.2f1, 2022.1.0f1, 2022.2.0a12
Could not test with: 2019.4.39f1, 2020.3.34f1 (SetGlobalInteger is not available)
Notes:
- Shader.SetGlobalInt works as intended
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
Add comment