Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
0
Found in
2018.3.5f1
2019.1.0a1
2019.1.0b1
2019.2.0a1
Issue ID
1123745
Regression
No
[Vulkan] Poor performance when using AsyncGPUReadback.Request
How to reproduce:
1. Open attached project
2. Choose Vulkan Graphic API
3. Enter the Play Mode
-- see that the frame rate is very low
4. Choose D3D11 Graphic API
-- frame rate is good
Reproducible with: 2018.3.5f1, 2019.1.0b2, 2019.2.0a4
Not compatible with 2017.4
Actual results: low frame rate
Expected results: normal frame rate
Notes: this happens in both the Editor and Build.
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2019.2):
This was caused by the fact that CPU readbacks were using uncached memory heaps, making memory reads from them very slow. Changed them to use cached heap whenever available, bringing the performance to be comparable to DX11.