Forum Discussion

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

Oculus on OSX with different User accounts

I successfully downloaded and installed the Oculus Runtime from SDK 0.4.2 for Mac OS, and configured displays so that the Demo Scene (launched from the OculusConfigUtil) runs just fine on my DK2.

However, if I log out then log in to a different account, the Oculus is not detected. When I open the OculusConfigUtil, I get an error, "The Oculus Service is not available." If I log back into the original account, everything works fine there.

Is this an expected limitation, only the installer account is able to access the Oculus? Does anyone know a way to manually launch the "Oculus Service" from a different account? Both accounts that I'm using are Administrators.

Thanks.

3 Replies

  • Sylane's avatar
    Sylane
    Honored Guest
    11 years ago
    I have exactly the same problem. If you ever find out how to fix it, please post how you did it. Thank you !
  • ssiva's avatar
    ssiva
    Honored Guest
    11 years ago
    I have found that running the Agent script (under /Applications/Oculus/Agent for my install) can get around this, but I want a better solution.
  • pizthewiz's avatar
    pizthewiz
    Honored Guest
    11 years ago
    Yes, I believe this is a limitation of the current runtime installer on OS X and have contacted support with a few suggestions. The existing installer installs the Launch Agent into the installing user's home directory:
    ~/Library/LaunchAgents/com.oculusvr.ovragent.plist

    I'd really like to see a native Installer.app package instead of the weird Bitrock Installer app and by default install into /Library for all users instead of just the installing user. Regardless, Installer packages can easily allow the installing user to select if components should be installed for all users or only the current user, so that is nice as well.