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.
Comments (1)
-
shubhamswaraj2021
Aug 19, 2020 05:50
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
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.