Skip to main content
KrzysztofBociur
New Participant
March 15, 2018

Problems turning off Oculus Rift - it keeps thinking my app is still using it

I'm making a C# WPF application with Oculus Rift integration using the (now obsolete) OculusWrap Oculus SDK  runtime adapter and SharpDX.

Recently, my application started to have issues when turning off. While running, everything works well. But after stopping Oculus usage, the last submitted frame keeps being displayed and Oculus Home says my application is "Now Playing". Even though it's already turned off. Sometimes instead of the last frame, a hourglass symbol is displayed in the headset.

I have gone through the documentation and as far as I see, all my ovr_...Create are matched with their ovr_...Destroy counterparts. Both ovr_Destroy and ovr_Shutdown are also called after everything is done.

The integration I used is old and abandoned, so perhaps there is something it does not do? Can't find it, though. The last updated Oculus SDK runtime they had was 1.3.2.0.

Also posted this to StackOverflow

    4 replies

    KrzysztofBociurAuthor
    New Participant
    March 20, 2018
    I might have mislead with the post a bit: OculusWrap is a managed wrapper over the runtime (LibOVRRT64_1.dll and LibOVRRT32_1.dll), not a direct SDK wrapper. I don't think I even have the SDK installed at the moment. The runtime is up to date.

    Attached is a minimal example of the bug and the sources to regenerate the project.
    If you want to open the sources, remember to install nuget packages and change the active project to OculusWrapDemo-DX11.

    As for the logs, a quick look at them before didn't expose anything interesting. Don't have access to them at the moment, but will try to not forget to send them soon as I get to that machine. You can regenerate them yourself anyway with the demo.
    kersk
    Meta Employee
    March 25, 2018
    Try using the "ovrInit_MixedRendering" flag on the ovrInitParams Flags field passed in to ovr_Initialize(). It allows apps to toggle between 2D and VR.
    kersk
    Meta Employee
    March 25, 2018
    I took a quick look at the OculusWrap project you are using and it does not look like it was built against a version of the SDK with the ovrInit_MixedRendering flag. You'll likely need to update the wrapper to be compatible with a newer SDK version in order to fix this issue.
    KrzysztofBociurAuthor
    New Participant
    March 26, 2018
    Just OR-ed a 0x20 into InitParams and it started to close properly.

    This seems to have fixed this, thanks!
    Terms & ConditionsAccessibility statement