Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2018.4
2019.3.0b3
2020.1
Issue ID
1185630
Regression
No
[Vulkan] ComputeBuffer data is corrupted when ComputeBuffer.SetData is called
How to reproduce:
1. Open the attached project "1185630.zip"
2. Open the Test Scene
3. Enter Play mode
4. Press Add data button multiple times
Expected result: Console logs numbers in a sequence adding one number after each button press
Actual result: Console sometimes writes random numbers (usually 1s and 0s) after some button presses
Reproducible with: 2018.4.14f1, 2020.1.0a16
Notes:
Unity Collections package is not available on Unity 2017.4, therefore the issue is not reproducible.
Could not reproduce using Nvidia graphics card drivers 431.60, however, the issue reproduced after updating to the latest 441.66 version.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Graphics.DrawProcedural doesn't work like in DX11 when used with DX12
- [Quest 2] Running Entities Graphics/BatchRendererGroup under Vulkan results in a frame rate drop compared to OpenGLES 3 and causes Tile Binning to cost more
- Filters dropdown: Window doesn't rescale on items collapse
- Sprite Preview is broken when the Sprite is too tall or too wide
- Objects are invisible in Scene view when using Wireframe Shading Mode
Add comment