07-16-202412:40 AM - last edited on 07-17-202409:50 AM by TheAntiSocializer
The MetaXR plugin is broken in UE5.4.
I downloaded UE5.4.2, created a new project from the VR template, made a Plugins folder, and imported version 66 of the plugin into it. However, the moment I turn on the MetaXR plugin, I can't open the project and it crashes. The crash shows "Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000058."
It crashes every time, around 75% of the OculusXR loading (though I don't understand why it's an Oculus plugin when it's MetaXR...).
I tried placing the plugin in the project and also under the marketplace folder of the UE5.4 plugins, but nothing changed.
Is there something wrong with my PC? Please help. I can't work if this doesn't get resolved.
I did the same procedure on another laptop and somehow it booted up. The only difference between the two is whether or not I have already installed MetaXRPlugin on MarketPlace. What a trap!
I'm struggling with this issue for days! I've tried the plugin from marketplace as well as from meta website. I always occur in this error. Did you manage to understand how to fix this?
I apologize to everyone reading this, but the fundamental issue wasn’t with the Marketplace (or FAB), but rather that my PC’s CPU generation was too old. It seems that Version 66 cannot be opened on a 9th-generation Intel CPU. (I recall reading somewhere that there’s a generational cutoff for CPUs, but I can’t remember where…)
The PC that successfully opens it has a 13th-generation Intel CPU.
I’m not sure about the Google-specific use case, but I have successfully packaged a project with Meta XR plugins 66 and 65 enabled into an .apk file. I installed the .apk using SideQuest or Developer Hub, and it worked perfectly as a standalone application. However, when enabling Passthrough functionality, I needed to remove the OpenXR plugin before packaging the project.
So you mean it is an hardware limitation? My CPU is Intel(R) Core™ i9-10885H CPU @ 2.40GHz, I know it's not the newest but it is neither so old. Do you remember where you read about such limitation? Thanks
ok, after 4 days of headaches finally I got the solution thanks to the support on UE forums. Apparently the problem is due to the presence of some OpenXR API Layers, that were still active by the time I was using SteamVR to develop on my old Vive HMD. Disable such layer should do the job. You can disable them both by SteamVR setting as well as by using this tool (recommend):
