Unreal Engine 5.4.3 VR apps seem to be "broken" with Meta release 66

Not sure if anyone else has this problem… but… my system updated to MetaLink version 66 about 7 hours ago. Since I got that update, ALL of my Unreal 5.4.3 projects no longer respond to motion controller (Touch controllers) movement or button presses. Not even the UE VRTemplate demo works now. The only Touch controller button that is responsive is the Meta “System” button.
Everything else works fine in the Meta home/eco-system… just nothing in UE.
I can assure you that NOTHING else has changed or has been updated on my machine/environment other than the Meta software update. A packaged build of a game that I built yesterday worked properly yesterday… does not work today. Any VR/OpenXR project that I I Play In Editor also exhibits the same behavior. I’ve rebooted, etc. etc. etc… to no avail.

I have opened a support ticket with Meta.

Is anyone else seeing this or has anyone else noticed this issue? Or is it “just me”?

Update: It turns out that ALL VR apps are unresponsive. This is NOT a UE issue. After posting, I downloaded the Meta installer application and ran a “Repair”. The repair installed Meta version 65. Everything now works perfectly again! I guess it’s “wait and see” if Meta updates to version 66 again and if this problem resurfaces…

1 Like

I had the same issue with Meta Quest Link v66.
I tried the “Repair” option but that did not revert back to v65 for me, and so did not fix the issue. However I’ve tried instead to enable the “Public Test Channel” under Settings/Beta, and I was glad to see that this immediately installed a beta v67 that indeed fixes the problem. Not sure yet if there are any other issues with the beta version but at least it fixes the major bug with the CV1 Touch controllers with v66.

Meta got harrassed well enough for V66 that they listened and fixed it with V67. The V67 release fixed the issues for me. Prior to that I replaced the two XR runtime DLLs with the ones from V65. I hear that V68 is rolling out (my friend already has it)… so… beware - again :wink: