Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
MeriemKalank's avatar
MeriemKalank
Honored Guest
2 years ago

[META QUEST 3] Bypass the "you've moved too far" popup

Hello, 
 
I'm currently working on a unity app for the meta quest 3 using spatial anchors in mixed reality with passthrough. I use them on a large zone, however I can't reach them without having this "you've moved too far" popup that I have to close if I want to see my app again which break the immersion.
Is there a way to disable it? 
 
Thanks for your help! 

19 Replies

Replies have been turned off for this discussion
  • jtriveri's avatar
    jtriveri
    Start Partner

    Only way I know of is disabling the guardian in developer settings, but this may mess up your floor level. 

  • Yes - if you go into MQDH (Meta Quest Developer Hub application on your PC with your headset air/cable linked) you can disable boundaries. 
    This will let you walk outside of your boundary, however without boundaries enabled you will not be allowed to record/stream mixed reality passthrough. It will only let you record the virtual aspect and all 'passthrough' camera data will be absent, which can be a game-breaker for recording an advertisement/demonstration

    • jtriveri's avatar
      jtriveri
      Start Partner

      You can also disable the guardian in in-headset developer settings. You don’t need to connect the headset to your computer every time

  • The "you've moved too far" pop-up is a huge problem for one of my applications as well. We use VR to distract pediatric patients as we move them on a gurney throughout the hospital, and it used to work well. I only noticed this message recently, and it's currently interrupting a study we're conducting and causing problems for our patients. One kid's VR gurney experience was going well, and then the application stopped, went to passthrough and showed that message right when they got to the operating room. 😬 Not great.

    Meta, this is a huge hindrance, and it also just seems like a pointless message. Disabling the guardian in developer settings works in a pinch, but it's a terrible user experience - and terrible user experiences make VR less likely to be used, especially in a healthcare setting. Please let us disable this message, or just remove it altogether! 

    • shubacurry's avatar
      shubacurry
      Protege

      To disable the boundary BS just go into your Android.xml file and add this line:

      <uses-feature android:name="com.oculus.feature.BOUNDARYLESS_APP" android:required="true" />
      make sure your Unity app actually uses your custom Android.xml file - Go into Unity - Edit Project Settings,
      Player
      Android,
      Scroll to the bottom of publishing settings
      and under"Build" make sure use custom Main Manifest is enabled
      • childlifetech.dev's avatar
        childlifetech.dev
        Protege

        Thank you shubacurry! I'll test it out next week when I have a big enough space. I did have com.oculus.feature.CONTEXTUAL_BOUNDARYLESS_APP in my manifest which worked for a while, maybe they just decided to remove the "contextual" part? Really wish Meta had better (or any?) documentation about this...

  • jtriveri's avatar
    jtriveri
    Start Partner

    I don't think this disables the 'you moved too far' message unfortunately. I'm using this manifest flag in my own app and I still receive the message when moving more than a couple rooms from my origin (spot where I launched the app)

    • childlifetech.dev's avatar
      childlifetech.dev
      Protege

      Yeah, I just tested it after changing from com.oculus.feature.CONTEXTUAL_BOUNDARYLESS_APP to com.oculus.feature.BOUNDARYLESS_APP. The message still pops up when I move far enough from my starting position. 😞

      • shubacurry's avatar
        shubacurry
        Protege

        Do you have any boundary data set on the headset?
        I wonder if there's no boundary data -completely empty, and you have boundary disabled as well. Then run the app would it still give that error?