Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.

Bug Unity Editor and Oculus Crash When Pressing Play

Discussion in 'VR' started by blongo99, Jul 12, 2023.

  1. blongo99

    blongo99

    Joined:
    Jul 21, 2021
    Posts:
    3
    This is a new development with my current VR project in Unity. I've been able to test and run the project in the editor with no issues, but starting yesterday, seemingly out of nowhere, Oculus would crash whenever I press play, and when I press play again to end the test, Unity also crashes and pops up an option to send a crash report to Unity devs. I have not run any system updates to my knowledge - and again, this started happening while I was actively testing things. It seems like one minute, everything worked as intended, and the next, I'm getting constant crashes.

    So far, I've tried starting new scenes with just an OVRCameraRig to test - crash still happens every single time. I've also started a completely new project, with just XR Integration and Oculus's package installed. Same empty scene, only an OVRCameraRig - still crashes. I attached a screenshot of the error messages that pop up while in play mode, and there's also the log from my most recent run. From my Googling prior to writing up this post, it looks like there's some people that were having this problem back in February before more recent Oculus updates. I've tried what they suggested (as seen above) but still no luck. I'd really rather not have to completely uninstall & reinstall programs, but if anyone can prove that's a good way to fix this problem, I'll do it.

    upload_2023-7-12_11-24-6.png
     

    Attached Files:

  2. glenneroo

    glenneroo

    Joined:
    Oct 27, 2016
    Posts:
    228
    I fought this exact issue for 3 days straight and even submitted a bug report to Unity (IN-46876) which they closed (though i re-opened it with some new info, as well as linking to here... who knows, maybe they'll re-investigate).

    My "solution" was to use my backup Quest which still has v54 on it. I'm not sure if it's because my normal dev headset was updated to v55 or if it's because it has multiple users logged in, or maybe even the wrong user (you can only change the primary user/admin every 6 months, ugh). Unfortunately I still don't have a solid solution other than using my headset with v54 and only use user.

    I also noticed this issue didn't happen when I worked on a project using only OpenXR and foregoing all the OVR / Oculus SDK specific calls.

    I would recommend posting the same info over in the Oculus developer forums, maybe enough people will be having the same issue that they 'll look into it - I feel like it's both issue both with Oculus SDK/OVR (Link disconnect) and Unity (crashing).
     
  3. blongo99

    blongo99

    Joined:
    Jul 21, 2021
    Posts:
    3
    Yeah, unfortunately any other Quests at my disposal haven't been used for at least 6-9 months so they might be a few updates behind. I might still try to check them and see if they'd be usable. I've never had another user logged in on my headset so it seems like that's one possibility checked off. My project (that was supposed to be finished by Friday... ha) uses hand tracking, which I'm only familiar with using through the Oculus prefabs. I'll definitely post over on their forums. I'm hoping this is something they've already been made aware of, but we'll see!
     
  4. glenneroo

    glenneroo

    Joined:
    Oct 27, 2016
    Posts:
    228
    If they are old then that's a GOOD thing IMO! My suspicion is that some versions of v55 are buggy and the root cause i.e. dust off those old headsets and give them a try. For me it was a last resort, having tried pretty much everything else in Unity and code and even ruining my project a few times and having to rollback changes in git (that was not fun to say the least). I'm really curious if one of your older Quests will work.