Skip to main content
dipRio
Up and Coming
July 16, 2024

The MetaXR plugin is broken in UE5.4

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.

    This topic has been closed for replies.

    10 replies

    dipRioAuthor
    Up and Coming
    July 16, 2024

    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!

    MartnDe
    New Participant
    July 16, 2024

    I have the same even in 5.1.1 

     

    Yesterday i was working and testing with a side-linked quest an 5.1.1 and today it doesnt work after the update at night.

     

    ????

    greetings Martn 

     

    domcoc
    Participant
    November 20, 2024

    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?

    BrotherOfPureEvil
    Inspiring
    November 20, 2024

    i have diffrent kind of error https://communityforums.atmeta.com/t5/Unreal-Development/UnrealEngine-meta-fork-don-t-like-plugins/td-p/1262504 but it also prevents me from working. im stuck

    dipRioAuthor
    Up and Coming
    November 20, 2024
    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.
    BrotherOfPureEvil
    Inspiring
    November 20, 2024

    are you able to build functioning apk with your cpu for oculus? there is no glitch in left eye after installing it on googles with metaxr enabled? 

    dipRioAuthor
    Up and Coming
    November 21, 2024

    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.

    domcoc
    Participant
    November 22, 2024

    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):

    https://github.com/fredemmott/OpenXR-API-Layers-GUI

      AdamUE4
      New Participant
      December 16, 2024

      You just saved me, thank you!! Opening SteamVR settings and disabling OpenXR API Layers fixed it for me

        Terms & ConditionsAccessibility statement