Search Issue Tracker
Third Party Issue
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.1f1
2022.1
2022.2
Issue ID
1379492
Regression
No
[DX11] ComputeBuffer doesn't return full buffer data when using one ComputerBuffer variable
Reproduction steps:
1. Open the attached user's Unity project "DX11Bug.zip"
2. Make sure that Graphics API is set to Direct3D11
3. In the Menu bar select Test > ProvokeBug
4. Observe printed Debug.Log in the Console window
5. Change Graphics API to Vulkan
6. Repeat steps 3 - 4
Expected result: Debug.Log prints "Final buffer data: 1 2 3 4 1 2 3 4" in the Console window
Actual result: Debug.Log prints "Final buffer data: 1 2 3 4 0 0 0 0" in the Console window
Reproducible with: 2019.4.36f1, 2020.3.28f1, 2021.2.11f1, 2022.1.0b7, 2022.2.0a4
Notes:
- Issue is not reproducible on macOS and Linux
- Issue is not reproducible with Direct3D12, Vulkan, OpenGLCore, OpenGLES2, OpenGLES3
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