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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment