Skip to main content
New Participant
May 6, 2026
Question

[UE5.6 / Quest 3] CONTEXTUAL_BOUNDARYLESS_APP breaks app launch — how to disable Guardian?

Hi everyone, I'm developing a VR app for a museum/art exhibition using Unreal Engine 5.6, targeting Meta Quest 3. The experience is fully passive (no controllers, no room-scale movement), so I need to completely suppress the Guardian boundary system.

What I tried:

Following the suggestion in this thread (https://communityforums.atmeta.com/discussions/dev-unreal/disable-guardian-at-runtime-in-mixed-reality-apps-unreal/1186665), I added this flag to my AndroidManifest via ManifestRequirementsOverride.txt:

<uses-feature android:name="com.oculus.feature.CONTEXTUAL_BOUNDARYLESS_APP" android:required="true" />

Results:

-Quest 2 + UE5.0 → works perfectly, Guardian suppressed

-Quest 3 + UE5.6 → app gets stuck on Unreal splash screen and never launches

Without this manifest flag the app runs fine on Quest 3. As soon as I add it, it freezes on splash.

I also tried enabling the boundaryless/passthrough options inside the Meta XR Plugin settings in UE5.6. The headset shows the message "Boundary may be inactive in this app", which sounds promising — but then immediately after, it prompts the user to set up a stationary boundary anyway, completely defeating the purpose.

Questions:

  1. Is `CONTEXTUAL_BOUNDARYLESS_APP` deprecated on Quest 3? Is there a replacement flag?
  2. Has anyone successfully suppressed Guardian on Quest 3 with a recent UE5 version?

Any help appreciated, Thanks.