Skip to main content
sararag
New Participant
May 6, 2026
Question

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

Hi, I'm working on a VR app for a museum exhibition with Unreal Engine 5.6 on Quest 3. The experience is passive, no controllers needed, so I'm trying to disable Guardian completely.

I found that adding CONTEXTUAL_BOUNDARYLESS_APP to the manifest worked fine on Quest 2 with UE5.0, but on Quest 3 the app just freezes on the Unreal splash screen and never starts. If I remove that line everything works again.

I also tried the boundaryless settings inside the Meta XR Plugin. The headset shows "Boundary may be inactive in this app" but then immediately asks the user to set up a stationary boundary anyway.

Has anyone managed to fully suppress Guardian on Quest 3 with UE5.6? Is that manifest flag deprecated on Quest 3? Any alternative approach via Blueprint or C++?

Thanks!

1 reply

Degly
Degly
Inspiring
May 10, 2026

I don’t think fully disabling Guardian is supported anymore on Quest 3 for normal applications now as according to the docs, CONTEXTUAL_BOUNDARYLESS_APP appears to be restricted/internal now, and the freeze on launch likely means the app fails entitlement/runtime checks during startup.

For museum/LBE setups, most devs currently use:

  • Stationary boundary
  • Very large boundaries
  • Managed/kiosk flows
  • Or enterprise/device-owner solutions

Unfortunately Quest 3 is stricter than Quest 2 regarding boundary enforcement. I would not rely on the old manifest flag anymore.

Terms & ConditionsAccessibility statement