Help regarding boundary system for mixed reality
Hi a few questions regarding the boundary system. We are a startup company that wants to create Mixed Reality applications for the Quest 3. These applications are typically used in large open spaces like museums/castles. To make these applications work the boundary system has to be disabled (as the player can see with the camera feed and depth api). Is there anything we can do to disable the boundary for end-users? We managed to use the `CONTEXTUAL_BOUNDARYLESS_APP` feature but even that seems to have it's limits as we are sometimes hit with a "You have travelled too far from your original position" message. Could someone who has fixed this issue, or a mod clarify on how to achieve this and what the required steps are? I have attached a prototype video of our Mixed Reality game as reference to what happens at the end. https://www.youtube.com/watch?v=kMjll3Ymltc Also is there a way to disable boundary setup just to start an app? Best regards,836Views0likes1CommentDisable guardian in passthrough with shared spatial anchors not working
Hello, Adding this line to the manifest disable the guardian while in passthrough: <uses-feature android:name="com.oculus.feature.CONTEXTUAL_BOUNDARYLESS_APP" android:required="true" /> But for the Shared Spatial Anchors sample from github it doesn't work. Here is my full manifest : <?xml version="1.0" encoding="utf-8" standalone="no"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" android:installLocation="auto"> <application android:label="@string/app_name" android:icon="@mipmap/app_icon" android:allowBackup="false"> <activity android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" android:configChanges="locale|fontScale|keyboard|keyboardHidden|mcc|mnc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|touchscreen|uiMode" android:launchMode="singleTask" android:name="com.unity3d.player.UnityPlayerActivity" android:excludeFromRecents="true" android:exported="true"> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> </intent-filter> </activity> <meta-data android:name="unityplayer.SkipPermissionsDialog" android:value="false" /> <meta-data android:name="com.samsung.android.vr.application.mode" android:value="vr_only" /> </application> <uses-feature android:name="android.hardware.vr.headtracking" android:version="1" android:required="true" /> <uses-feature android:name="com.oculus.feature.CONTEXTUAL_BOUNDARYLESS_APP" android:required="true" /> <uses-permission android:name="com.oculus.permission.USE_ANCHOR_API" /> <uses-permission android:name="com.oculus.permission.IMPORT_EXPORT_IOT_MAP_DATA" android:required="false" /> <uses-permission android:name="com.oculus.permission.HAND_TRACKING" /> <uses-feature android:name="oculus.software.handtracking" android:required="false" /> <uses-feature android:name="com.oculus.feature.PASSTHROUGH" android:required="true" /> </manifest> Do you have any idea why ? Thank you !611Views0likes0CommentsDisable guardian in passthrough mode
We have an app that has passthrough enabled at all times so you can walk around your location and add virtual items to the real world. However, the player is required to travel across far distances in real life while using the app. Is there a way for the app to turn of guardian mode while passthrough is on?5.1KViews8likes10CommentsGuardian boundaries are displayed with a delay
Hi, I have 2 Quest 2, and the same problem appears on both of them : Guardian displays the boundaries with a 0.5s to 1s delay. This delay is very noticeable with fast movements, and it is extremely dangerous. I almost broke my hand 3 times because of this. I already did a factory reset on both headsets, it didn't change anything. I think this issue appeared since v44 or v45. Before that, Guardian was smooth as it should.671Views0likes0CommentsApp lab app guardian recquired
Hello, For some reasons my apps (applab) recquired the guardian to be activated and I cannot launch them without. This behavior is new as it's been working in the past. That's a big deal to me as my customers are not happy. I've done some research in the app metadata of my apps but could not find anything that is related to the problem. Do you have any info/ways to change this and be able to launch my apps with the guardian deactivated ? Thank you for your time, Cheers. Baptiste716Views0likes0Comments