Forum Discussion
Guardian system and seated experiences
With the release of Touch last week, I'm running into an issue with my seated app when building against the 1.10 runtime. Consider a person that has their sensors placed on their desk. They have set up Guardian for when they are doing standing, room-scale type applications, and note that the location of their desk is not a safe area. However, for seated applications, the Guardian system will still be running. So now when they are seated, at the edge of the safe area, the guardian system will be active, resulting in the user always seeing the cyan mesh. This is extremely distracting.
Is it possible to have some kind of way to switch the Guardian system on/off depending on whether we are supporting Touch or are a seated experience? Or at least to have some way to tell the Guardian system when we are seated and when we expect the person might be moving around? Right now the only option to disable Guardian comes from the user themselves, and it's a global setting.
Is it possible to have some kind of way to switch the Guardian system on/off depending on whether we are supporting Touch or are a seated experience? Or at least to have some way to tell the Guardian system when we are seated and when we expect the person might be moving around? Right now the only option to disable Guardian comes from the user themselves, and it's a global setting.
7 Replies
- I'm having the same issue. I agree it should be corrected.
- I totally agree. I need to be able to switch off the guardian system for my seated experiences. It's not practical to have to put a seat in the middle of the room so you dont activate the guardian system. I tried to watch a film on Big Screen and and then Virtual Desktop but gave up in the end because my seating area is just outside the guardian system, so was on constantly totally interupting my view of the screen. It's crazy that this was never considered when in developement. Not every experience is for touch and this should be taken into consideration.
imperativity said:
Hello again,
At this time there are no plans to allow toggling the guardian system on/off. This is due to limitations in the system with regards to correctly identifying room-scale apps.
Let me know if you have any other questions.
I would add my stone to the wall ( 2017 is the year of wall and guardian is one no ? )
In my case, i feel like the guardian looks more like a debug draw than anything else and i would love to see a way for an app to disable it under the guarantee than it render their own ( and may be a per frame flag for when an app is in the limbo to let the driver take over ). Why i want that ? Because guardian render on front of object and create depth conflict. to lower the conflict it is possible to do various things in the app that the driver cannot do, like testing depth buffer and adapt transparency for example.
The SDK is already half way here as it allow to query the control points.
imperativity said:
Hello again,
At this time there are no plans to allow toggling the guardian system on/off. This is due to limitations in the system with regards to correctly identifying room-scale apps.
Let me know if you have any other questions.
Hopefully I am just misinterpreting your comment, but I am reading this as you saying that users with Touch that use seated applications at their desk (a room-scale boundary) will just have to deal with the mesh wall in their face?
Why can't verification of seated/room-scale be part of the submission process?- I appreciate the explanation, but I'm not sure you guys are recognizing that this affects currently released apps. As a developer, my only recourse right now is to tell users to disable the Guardian System, but ultimately that is a poor user experience. In addition, many users will not know how to do this, or, will not want to be bothered to switch the system on/off.
I do hope that the future improvements will include a way for developers to specify seated versus standing through OVRManager so that developers can have some more control in automating this process.
imperativity said:
Hi,
@delphinius81 from what I can understand from the teams in charge of this feature, the guardian system sometimes has trouble identifying room-scaled apps effectively. Apps that want to make the virtual content line up with a specific point in the real world (like the floor) will use floor-level tracking, but there are also room-scaled games that the need the world in a specific place relative to your initial head pose, so the guardian can't just be disabled for all apps that use eye-level tracking.
I've been told that there are plans to improve the guardian system's functionality going forward, however.Why can't verification of seated/room-scale be part of the submission process?I believe that would be a good question to ask the submissions team.
EDIT: Does this help address the issue with toggling the guardian system?
https://developer3.oculus.com/documentation/pcsdk/latest/concepts/dg-guardian-system/
- If you need to disable the Guardian System, toggle Guardian System Enabled/Disabled on the Universal Menu.
We've just encountered this ourselves, we'd like to offer the ability to play seated or standing in game
rather than disable it could you not just allow us to turn the renderer off so you don't get a big blue cage in your face on seated mode games?- Isn't there an option now (on the user side), to only show the guardian boundaries on the ground, rather than ground + wall?
