Search Issue Tracker
By Design
Votes
1
Found in
2017.2.0f3
Issue ID
973508
Regression
No
[Win] First StructuredBuffer will be deleted when calling ComputeShader.SetBuffer twice giving the same buffer
Steps to reproduce:
1. Open attached project "973508.zip"
2. Click on "TEST BUFFER/Add numbers" menu item
two identical int arrays will be added with each other
two lines will be printed in the console: one of the input int arrays and the result of added numbers
3. Observe the console
Actual result: when calling ComputeShader.SetBuffer twice giving the same buffer, the first StructuredBuffer will be deleted, so the result line in the console is exactly the same as the input line
ComputeShader.SetBuffer(kernel, "array_1", buffer);
ComputeShader.SetBuffer(kernel, "array_2", buffer); - at this point the StructuredBuffer "array_1" will be deleted
Not reproducible on OSX
Reproducible with: 5.6.4p3, 2017.1.2p3, 2017.2.0p4, 2017.3.0f1, 2018.1.0a7
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
Add comment