Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.2p2
Issue ID
931163
Regression
No
[Daydream] [Android] Performance issue on VR.WaitForGPU (takes 40ms+)
From Google:
Latest on this is that
it's an issue with the Qualcomm graphics driver (i.e. 2-4ms extra GPU time
beyond what's expected for MSAA). It will be a permanent problem for
Snapdragon devices running Android N, and will be fixed in Android O.
---
Steps to reproduce:
1) Download attached project and open in Unity
2) In Player Settings, make sure Stereo Rendering Method* is set to Single Pass
3) Build and Run project on a device with Autoconnect Profiler enabled
Observe Profiler, VR.WaitForGPU takes 40+ms
Expected result: VR.WaitForGPU should not take that much memory (check attached image 'expected(Pixel).png')
Actual result: VR.WaitForGPU takes 40+ms which causes performance issues (check attached image 'PixelXlActual.png')
Reproduced with:
5.6.3f1, 2017.1.0p2
I wasn't able to test with 2017.2.0b5 because images on the Canvas are not rendered after deploying on a device
Application crashes using 2017.3.0a2
Devices under testing:
Reproduced with:
Google Pixel XL, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:google/marlin/marlin:O/OPP2.170420.019/4021594:user/release-keys
Not reproduced with:
Google Pixel, OS:7.1.2, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:google/sailfish/sailfish:7.1.2/NJH47D/4045516:user/release-keys
Comments (1)
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] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [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
dustinkerstein
Oct 11, 2017 14:45
Do you happen to have any more info on this issue? I'm trying to debug some performance issues we've been having with the Pixel (and not on a Moto Z).