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
- Rotation Property collapses after changing Interpolation Type In Animation window
- It is possible to enter impossible Scope name in the Scope Registries of Package Manager Project settings
- 'EditorSceneManager.sceneCount' reports the wrong count when called by an 'EditorSceneManager.sceneClosed' event
- Entering large values in keyframe “Value” causes Curve to disappear and spams Mesh Bounds errors in the Console window
- [Android][iOS][UnityPlayerActivity] Legacy InputField.onEndEdit is not called when ending text edit
Resolution Note (fix version 2019.3):
2019.3.6f1