Skip to main content
svenneve
New Participant
June 14, 2018

OVRInput and Input blocked when virtual reality support is disabled

When I try to test a 2D / desktop mode version of our game built in Unity using the OVRInput class for player input with virtual reality support disabled, ALL input seems to be blocked (all inputs return false or 0).
(On top of that when VR is disabled OVRPlugin endlessly spews the famous 'ovrp_GetAppHasInputFocus return Failure_NotInitialized' warning', I thought this was fixed at some point?)

Is this a bug? Am I doing something wrong?

Unity 2017.2.0f3 with Oculus Utilities 1.21.0.
This topic has been closed for replies.

2 replies

svenneveAuthor
New Participant
June 14, 2018
Okay, 'solved' it, so in case anyone runs into this, here's the run down.

It seems in order to run desktop mode, you need to build with virtual reality support enabled, and start your build with '-vrmode none' (which didn't work), but what the manual fails to mention and the Oculus' 'Use Required Project Settings' script fails to do though, is adding the 'None' Virtual Reality SDK in your PlayerSettings.

And since OVRInput needs to have a HMD present or it will simply fail, building with virtual reality support enabled makes sure OVRInput will work.
mousebear
mousebear
Honored Contributor
June 20, 2018
@svenneve Thank you for the info and update! This is good feedback for us to add to our body of knowledge.
If you need immediate help or want additional support/context on an issue you are having with our platform or integrations: 1. Gather any and all logs , screenshots, and version numbers of relevant software (Oculus SDK, engine, etc.) 2. Please submit a ticket here through the "Contact Us" link (include what you've gathered in step 1). 3. Tag me @mouse_bear once you have done so!
Terms & ConditionsAccessibility statement