Forum Discussion

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

Oculus Link crashes on Play mode with OpenXR OVR Plugin and Oculus Developer Runtime Features

Steps to reproduce: Quest Pro (factory reset), probably any version of Unity (tested with 2020.3.48f1, 2021.3.20f1, 2022.3.2f1), XR Plugin Management > Oculus, Oculus Integration 54.1, Oculus App > Settings > Beta > Developer Runtime Features ON

Oculus Link & Unity Editor crashes on Play Mode with a fresh project (settings described above).

Disabling Developer Runtime Features in the Oculus App fixes the issue. However, this is not an acceptable workaround for developers who need to make use of these features.

Thanks!

6 Replies

Replies have been turned off for this discussion
  • This seems possibly related to the following known issue:

    • When using Unity OpenXR Plugin and have “Developer Runtime Features” enabled in the Oculus app, Unity editor might crash when starting the VR preview. The workarounds are (1) Switch to Oculus XR Plugin, or (2) Disable “Developer Runtime Features”, or (3) Start Quest Link before using play-in-editor.

    However, starting Quest Link before using play-in-editor does not appear to be a valid workaround, nor does 'Switch to Oculus XR Plugin' (already enabled).

    • amir.blimey's avatar
      amir.blimey
      Explorer

      Having this issue as well, but for me it started after my Quest 2 upgraded to v55. Confirmed that disabling "Developer Runtime Features" solves the crash issue, but obviously that won't do when trying to develop for Passthrough and Scene Model APIs...

      Did you have any luck solving this?

  • Anonymous's avatar
    Anonymous

    You could try to switch to the public test channel in the oculus desktop app (Settings > Beta > Public Test Channel). The beta seems to contain a fix.

    • amir.blimey's avatar
      amir.blimey
      Explorer

      Can confirm - Meta support told me the Quest OS and PC App need to be syncronized but the PC App was still in version 54. Enabling the test channel and updating the PC App solved the issue and Link is usable with Dev features once more! Thanks for the tip Anonymous.

      • moritzjenny's avatar
        moritzjenny
        Honored Guest

        Anonymous YES! can confirm that this works. This post really saved my day.
        - Settings > Beta > Public Test Channel
        - Wait for 1 min so that the dialog for the update pops up
        - Update to newest 🙂

  • I can confirm that the solution above does not work anymore.
    Performance goes to trash if enabling Developer Runtime Features, but is restored if disabled.

    Tested in
    Unity 2022.3.35f1, MQL 69.0.0.501.353, Quest 69.0.0576.352