Skip to main content
MarkHenryC
Up and Coming
February 11, 2018

Simulate Rift disconnection

Is there an approved way of doing this in software? I'd like to be able to test builds as regular Windows apps as well as test in Unity without always having to use the headset (using mouse control of camera). I've tried closing the Rift home app and shutting down the service, which does the job, but then after starting service when testing with Rift, it adversely affects the system (Windows and taskbar go invisible, Rift functions as gyro but no sound or image, requiring a reboot). Reaching around and unplugging the HDMI works fine but is a bit of a chore. Any suggestions? I seem to remember in an older Rift app you could set it to not kick in when an Oculus-enabled app starts.

2 replies

MarkHenryCAuthor
Up and Coming
February 12, 2018
Thanks for the response. Having left things running normally over about 30 hours since the last reboot the issue has just shown up again, so there may be another cause. Periodic reboots seem to be the only solution at this stage. The image stops working. Switching to classic Home brings it back but it blacks out every 5 seconds. I've submitted a report with logs in case there's a hardware problem. But thanks for letting me know about your position on dual-use dev.
MarkHenryCAuthor
Up and Coming
February 16, 2018
Hi Rodney imperativity. A quick follow-up:

Simply adding a menu item for toggling PlayerSettings.virtualRealitySupported does what I need with a single click. (A bit dumb of me to miss that.) Also, some suggestions from Oculus Support seem to have fixed the other issues I referred to (Explorer windows and taskbar going invisible, headset screen and audio cutting out) by rolling back the NVIDIA driver to 388.59 (as recommended on support entry page) and disabling USB power saving. They also recommend that primary monitor and Rift headset are on same video card.

Hopefully this may help others doing a search on similar issues.

UPDATE: now I remember why I didn't use PlayerSettings: OVRMoonlightLoader keeps switching it on (via EditorApplication.delayCall) so you have to switch it back off before playing.
Terms & ConditionsAccessibility statement