Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Manzalab's avatar
Manzalab
Honored Guest
7 years ago

[Oculus Utilities] Changing the variable 'OVRManager.instance.monoscopic' does nothing

Hello,

We are currently developing an Android application using GearVR.

Since we migrated on 2017.3, the variable OVRManager.instance.monoscopic of the OVR plugin utilities has no effect.
On Unity 2017.1, if we changed this variable to true, we would effectively see our application in monoscopy.

Since 2017.3, we are always in stereoscopy and we can not manage to change that.

We use OVR 1.18 and it does the same on 1.21

Thanks in advance !
bug
monoscopic
ovrplugin
Unity 2017

2 Replies

Replies have been turned off for this discussion
  • Manzalab's avatar
    Manzalab
    Honored Guest
    7 years ago
    I want to update this thread with a temporary but clean enough solution.

    So we found that the problem was coming from the OVR utilities.

    When you build your project to an Android APK, the OVR plugin used is found in
    "YourUnityInstal/Editor/Data/UnityExtensions/Unity/VR/Android/"
    and is named
    "OVRPlugin.aar"

    When we installed Unity 2017.3 to migrate our 2017.1 project, the 2017.3 folder was populate with a new version of the OVRPlugin, the 1.25.x
    Since then, the monoscopic boolean stopped working.

    After a lot of debugging, research and such, we found this hidden folder with the OVRPlugin.aar
    We took the 2017.1 OVRPlugin.aar (version 1.18.x) and put it in the 2017.3 folder replacing the 1.25.x version.
    The boolean worked again.
  • joaquin's avatar
    joaquin
    Protege
    7 years ago
    I have the same issue with windows, monoscopic is not working anymore. When I do 
    OVRPlugin.monoscopic = true;
    OVRManager.instance.monoscopic = true;
    something do happens: everything shows in double.
    I tried to revert to a previous version of Oculus Utilities for Unity + previous version of OVRplugin but without improvement: hence the error must be in the oculus driver.