Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2018.4
2019.2
2019.3
2019.3.0b8
2020.1
Issue ID
1197375
Regression
No
AsyncGPUReadback returns incorrect result on Vulkan
Steps to reproduce:
1. Download the attached project and open "Test" scene
2. Build a Standalone project with D3D11 or D3D12
3. Notice that AsyncGPUReadback.Request returns Vector4 of 1,2,3,4
4. Switch Graphic API to Vulkan
5. Notice that AsyncGPUReadback.Request returns Vector4 of 2,3,4,1 which isn't correct result
Results: On Vulkan, AsyncGPUReadback return incorrect results.
Reproduced with: 2020.1.0a12, 2019.3.0b11, 2019.2.11f1, 2018.4.12f1
Note:
- Issue also reproducible on PS4 and Editor
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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Resolution Note (fix version 2019.3):
2019.3.6f1