Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1354852
Regression
No
Missing function to reset or unset a specific resource in the local binding space of compute shaders
Currently there is no way to avoid using a previously set Texture, Buffer etc in the local binding space of a compute shader if you can only set the global one. As soon as it is set once (previous frame) it will take precedence over the global one set the same frame. It caused a bug on vulkan, but the issue remains valid I believe.
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 (2022.1.X):
This is the limitation of the current implementation.
We'll prioritise this as a feature request.