Forum Discussion
Solved
Unity crashes when running Quest 2
Oculus Quest 2 connected to PC through link cable. Has been working for over a year. Now run Unity project. On Oculus Screen clears, a box appears. On the bottom it says Loading... Then screen goes jagged. In a second, link disconnects and Oculus goes to home screen. On the computer, a Unity crash screen comes up. Then when I click the Run/Stop button on Unix, the project closed and a crash collection screen comes up. I did submit a crash dump to Unity. Collected Quest Logs but can't figure out whom to email them too.
Experiencing the same issue after Quest 2 updated to v55 yesterday. Can you check if disabling "Developer Runtime Features" in Quest PC App allows you to run play mode without crashing? This is the case for me but it is not a valid solution since I am developing for MR...
Today I tried to factory reset my quest but it did not fix the issue. Hopefully Meta will provide some support soon.
15 Replies
Replies have been turned off for this discussion
Experiencing the same issue after Quest 2 updated to v55 yesterday. Can you check if disabling "Developer Runtime Features" in Quest PC App allows you to run play mode without crashing? This is the case for me but it is not a valid solution since I am developing for MR...
Today I tried to factory reset my quest but it did not fix the issue. Hopefully Meta will provide some support soon.
Thank you so much. That worked. Not I can get back to developing. Adding you solution to the Unit Crash Report.
Thanks! That's solved my immediate problem.
Let's hope they fix it soon, and maybe test the next update before releasing it.
This solved my issue, cheers!
I was about to post a new topic reporting exactly the same problem.
Unity projects that I try to run via Quest Link (USB or WiFi) cause Unity to crash and in the headset I'm kicked out of the Quest Link interface. Before crashing Unity outputs a series of warnings in the console (and in the Editor log) of the type XR_ERROR_INSTANCE_LOST and XR_ERROR_HANDLE_INVALID.
All this suddenly started to happen last week on a project that was running perfectly before. And now it occurs with every single Unity project, including sample scenes in the Oculus package.
I can still build and run on the device. That works. But I can't play directly from Unity through Quest Link.
I did a factory reset, but that didn't solve the problem.
I have the most recent software on the device (55.0.0.130 etc.) and I'm using Unity 2021.3.28f1 on Windows.
It looks like Oculus/Meta might have screwed up again by delivering a faulty update.
Frankly, I've been experiencing so many problems with my Quest Pro, its apps and development tools that I'm deeply regretting having bought the device. I used to develop with a Vive Pro and while I had occasional issues with Steam VR and Unity, that was nothing close to the unmitigated disaster that my experience with the Quest has been. Boundaries that get suddenly lost, buggy proxy sensor disabling, Quest link connections which on exit completely disconnect the device (necessitating a restart), selective passthrough which works only on rainy days, keyboard tracking which tracks nothing, the hand pinch system menu whose buttons hardly work, repeatedly asking to allow USB connections... I could go on and on. It's been one frustration after the other.
I'm really surprised and extremely disappointed that a company like Meta with its immense resources has produced such a flawed product and mediocre customer/developer experience. Did they recruit engineers from CDPR or what?
Better answer: ensure that the Oculus PC App is ALSO on v55 (version is listed at the bottom of the Settings->General page). The App and the Device need to be in sync for these features to work correctly. If it is not, enable the Public Test Channel in Settings->Beta and go to Library->Updates to ensure it gets updated. I am now able to use Quest Link with Developer Runtime Features once more!
Thanks to David from the Meta team for the tip.
That is probably the issue, but when I check my Oculus PC software, it says it is Ver 54. When I go to Library Update, it says it is up to date. I uninstalled the Oculus PC and reinstalled and it put the same one on. This work around will work until Oculus gets the sorted. Thanks!
Also Unity Oculus Integration is 54.1.
Wow, you'd think there'd be a check on this! When I enabled the public test channel, the Oculus app updated directly to v56! Did they forget to validate v55 on the Oculus app when committing the system update for the headset?
It scares me (and it also explains a lot) that there is apparently no verification process at Meta to check that the headset and the apps are running compatible system versions. And the user should definitely not have to enable a beta channel to get that compatibility!
I did this update - so desktop app is at V56 and headset is at V55 - and now Unity isn't crashing, but freezing! Still a problem, but I guess its a different one? So something happened with the updates. Hopefully tomorrow we'll see a V56 for the headset getting pushed out.
Thanks for the additional info, unfortunatly when I did the update I was provided with V56!! Given you comment that the headset (V55) should match the desktop (now V56), I guess I can only try it.... who knows what will happen...
