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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2022.1.X):
This is the limitation of the current implementation.
We'll prioritise this as a feature request.