Search Issue Tracker
Duplicate
Votes
1
Found in
2019.1.0a11
Issue ID
1107388
Regression
Yes
[Gear VR | Go] Noticeable performance degradation
Unity 2019.1.0a11 has worse performance on Gear VR than other recent versions. This is noticeable to a lesser extent on Oculus Go. When moving my head quickly I see dropped frames or judder in several simple scenes.
-
Shane_Michael
Dec 17, 2018 09:16
I have seen this in 2019.1.0a12 with a simple scene from a 2018.3.0f1 project that runs at 72fps with extra headroom. It also happens if you import the Oculus Integration (both 1.31 and 1.32) into a new project and build & run the trivial "Oculus\VR\Scenes\Room" test scene.
Every few seconds there is disruptive judder for several frames.
The Remote Oculus Monitor profiler is giving me an "out of order frame index (prev = x, new = x+2)" warning. This coincides with a predictable pattern of one or two very short "WarpSwapInternal" calls (~3ms) and then a very long one (~26ms). This is happening with a GPU/CPU utilization at ~45% and ~55% respectively.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1135328