Forum Discussion
Solved
Meta update v68 & OpenXR - xrEnumerateInstanceExtensionProperties fail to return any valid extension
A critical issue has arisen with the recent update of the Meta Quest Link application to version 68.0.0.433.361. In summary, all of our applications based on Khronos OpenXR and Unreal Engine 4.27.2 can no longer be run via Link. This means that the vast majority of our customers can no longer access our applications. Additionally it prevents our Unreal Engine developers from being able to use tethered Meta devices.
This issue has been confirmed for Meta Quest 2, 3 and even Rift S devices.
This issue has been confirmed in vanilla Unreal Engine projects also.
We have traced the failure to the OpenXR runtime layer. OpenXr API calls such as xrEnumerateInstanceExtensionProperties fail to return any valid extensions, which prevents the Unreal Engine being able to communicate with the headset.
We believe that other people may be having the same or similar issues with the recent update:
- https://steamcommunity.com/app/1849250/disussions/0/4515506358400756962/
- https://www.reddit.com/r/oculus/comments/1e6lq00/comment/lecf5bu/
- https://communityforums.atmeta.com/t5/Get-Help/Open-XR-Toolkit-was-broken-with-v68-Oculus-Link-code/td-p/1223235
Are you aware of this issue? Are you looking into a resolution or is it an intended change?
Repro Steps:
- Create a VR template project using Unreal Engine 4.27.2.
- Make sure the active OpenXR runtime is set to the Oculus runtime.
- Observe that the Unreal Editor will not let you run the project in VR with a Meta headset connected via Link. (Option is greyed out because it cannot detect the headset.)
Meta put a hotfix version of the Meta Quest Link app up on the PTC that fixes this issue.
The version is: 68.0.0.474.361
I tested it out this morning and it fixes the issue for us.
8 Replies
MetaLoc we are experiencing this exact same issue with our Unreal 4.27.2 + OpenXR game. It's the exact same issue where I'm seeing a failure in OpenXRHMD::EnumerateExtensions().
The repercussions you laid out are correct. The game is unplayable if you select Oculus as the active XR runtime and attempt to play the game via Quest Link or Airlink. It's a pretty serious issue for us as well. It essentially means Quest PCVR players can only play our game via SteamLink.
We also noticed connecting your Quest headset via QuestLink but setting the active XR runtime to SteamVR also "works" since this problem seems to be some sort of OpenXR plugin incompatibility with the recent v68 changes BUT there's a separate OpenXR Unreal 4.27.2 bug where tracking is jittery and broken down that path, so it's not really a viable alternative.
One other interesting tidbit from my testing. Unreal 4.27.2's OpenXR plugin is impacted by this Oculus XR runtime bug but Unreal 5.3's OpenXR plugin seems unaffected. I've been trying to track down why this is the case but in general this means games built with Unreal 5.3 shouldn't have any issues in the Quest headset + OpenXR HMD + Oculus XR runtime + Quest Link configuration but Unreal 4.27.2 games will fail until the issue is fixed.
In Before Meta suggests "Upgrade your engine build to fix our problem"...
We're built on 4.27 and about 75% of our customers are Meta Quest users. Our current suggested workaround is to use Steam Link + Steam VR, but it's not viable for many of our customers on lower-end hardware (especially laptops).
Not a developer myself but this issue affects more than just Unreal projects, it means OpenXR toolkit, Racelabs overlays, and any other tool using these APIs (properly I might add) don't work. Apparently reported well before release but left in. Feels bad.
a mí me ha pasado anoche. Trabajando con UE tanto al versión 4.26, 4,27 y la 5,03. En todos los casos aunque conectando con quest link, no se activa la previsualización en UE (se ve en gris y desactivado). Tengo quest 3.
We were informed by Meta that they are aware of the issue and are looking at the mitigation plan. We do not have a timeline or a description of the mitigation plan.
Meta put a hotfix version of the Meta Quest Link app up on the PTC that fixes this issue.
The version is: 68.0.0.474.361
I tested it out this morning and it fixes the issue for us.
