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.
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!
This worked for me, but I'm not sure of the side effects of having disabled "Developer Runtime Features". Please let us know if this bug is fixed and we can re-enable the "Developer Runtime Features". Thanks.
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...
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.
