Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.2.13f1
Issue ID
1091430
Regression
Yes
[XR][Android] Draw Call VR performance regression across all mobile devices since 2018.2.13f1
Steps to reproduce:
1. Open user attached project
2. Integrate the Oculus Utilites package (https://developer.oculus.com/downloads/package/oculus-utilities-for-unity-5/)
3. Build the CPUPerf scene for mobile
4. Run the apk until it quits itself, it will report results to the logcat
5. Observe draw call difference between 2018.2.13f1 and 2018.2.12f1
Expected result: 2018.2.13f1 version should not cause a Draw Call VR performance drop
Reproduced in: 2018.2.13f1, 2017.4.14f1
Not reproduced in: 2018.2.12f1, 2018.1.9f2, 2017.2.4f1
Regression since: 2018.2.12f1
Tested and reproduced devices:
VLNQA00109, Xiaomi MI NOTE Pro (MI NOTE Pro), Android 7.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00155, Meizu PRO 7 Plus (PRO 7 Plus), Android 7.0, CPU: MediaTek Helio X30 MT6799, GPU: PowerVR Rogue Marlowe
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment