Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X, 2018.3.X
Votes
0
Found in
2017.1.0a6
Issue ID
898992
Regression
No
[VR] Vsync gets turned off when Oculus is off head on a Standalone build with "Run In Background"
Steps to reproduce:
1. Download and open the attached project
2. Build for standalone
3. Turn on the build
4. Activate/Deactivate Oculus HMD sensor
5. Observe UI image and rotating cube changes coming from Update
Expected result: framerate stable when sensor is on and off, Vsync is kept on
Actual result: with sensor off, Vsync gets turned off, fps rises, all calls from Update in scripts are processed accordingly
Reproduced on 5.5.3f1, 5.6.0f3, 2017.0a6, 2017.0b1
Notes:
-This does not occur in Editor play mode due to the sensor not having an impact there
-Only happens when the Player is set to "Run In Background", otherwise build pauses when Sensor is off
Issue is on Oculus side, to be fixed in their SDK
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
- [iOS] App crashes when trying to use WebCamTexture depth data on back triple camera
- [Mobile] Only second base Camera out of two base Cameras with priority 1 and -1 is rendered in the Player
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
Resolution Note (fix version 2017.4):
Fixed issue where Vsync gets turned off when Oculus is off with Standalone build with "Run In Background"