Skip to main content
g221
New Participant
July 12, 2023

Quest 2 headset link and unity crashing when hitting play when developer runtime features enabled on

Unless developer runtime features are off on the oculus app, I cannot run unity on it. I put the quest 2 into link mode and then run unity and it shows the loading screen for a second and then exits link mode and the unity game engine crashes when I stop it from play mode. It was just working about a week ago and I don't know what happened but now it doesn't work, I need developer runtime features for passthrough integration on my app. I have tried:

  • Creating a new project in (2020, 2022, 2023) with out any other assets but the oculus integration.

  • Factory resetting the headset

  • Updating the oculus firmware

  • Reinstalling the oculus app

  • Reinstalling the unity packages

I don't know what to do now, I read on the oculus integration unity website that this is a known problem but does anyone know of any fix?

 

Update:

I posted this bug on the unity website and a staff member responded with this

Hi,

Thank you for contacting us.

I found this in your Editor.log file:

 

 

 

0x00007FF85CFA980B (RuntimeIPCServiceClient_64) ipc_GetClientStateClientMemoryIdFromServerMemoryId 0x00007FF85CF9D49C (RuntimeIPCServiceClient_64) ipc_GetClientStateClientMemoryIdFromServerMemoryId 0x00007FF85CF249E5 (RuntimeIPCServiceClient_64) Ordinal0 0x00007FF85CF33AFF (RuntimeIPCServiceClient_64) Ordinal0 0x00007FF85CFB3508 (RuntimeIPCServiceClient_64) ipc_GetClientStateClientMemoryIdFromServerMemoryId 0x00007FF886737614 (KERNEL32) BaseThreadInitThunk 0x00007FF8884E26F1 (ntdll) RtlUserThreadStart

 

Judging from this stack trace, it looks like the crash was caused by a third-party library "RuntimeIPCServiceClient_64", which is part of the Oculus runtime. Since we do not support third-party plugins, I recommended reaching out to the developers about this issue.

Regards,
Katrina
Customer QA Team

      This topic has been closed for replies.

      4 replies

      bridgiel
      New Participant
      July 12, 2023

      I was just about to post with this exact same issue. It seems like it could be caused by the most recent V55 Oculus update. Someone over on the Unity forums said they were able to get it to work on another headset that was still on V54, but other than that, there's been no real solution. Hopefully posting on here will make the Oculus Devs catch it a little faster so they can work on a solution.

        deepansh96
        New Participant
        July 13, 2023

        Two people in our team are facing this exact issue. It was working fine a week ago. We had turned on the "update before restarting" option on our headsets and after the update this issue came up. One of them faced this issue on Quest Pro and another on Quest 2. For the time being we're either relying on XR Emulator or using a quest which hadn't been updated. But this is extremely frustrating. 

          amirblimey
          Participant
          July 13, 2023

          If your quest device has updated to v55, you need to ensure the Oculus PC App is on v55 as well. Check the bottom of the Settings->General page to see the version. If it is still on v54, enable the Public Test Channel in Settings->Beta, and hopefully it will download the update. This resolved the issue for me!

          Bethsheba
          New Participant
          December 15, 2023

          I've been getting the exact same difficulty for the past 2-3 days. It's lost me three days of work on the game I'm developing, and it happened directly after the Oculus update. I've reinstalled the PC app. I've reinstalled and upgraded the Unity editor. It will work for the first time, but every time after that when I hit play in Unity it makes Link crash out and the PC Oculus App crashes too. It's making VR development impossible so I hope they get it fixed soonest!  

            Terms & ConditionsAccessibility statement