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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2022.1.X):
This is the limitation of the current implementation.
We'll prioritise this as a feature request.