Thank you all for adding to the conversation. I too have some back issues and find seated to be preferable. I tried to browse some of the Oculus developer SDK documents for parameters on how the height is being set by the guardian process but did not have any luck. I also tried to run ProcessMonitor on windows (by Windows SysInternals) but did not isolate any parameters.I was hoping to find something in the .json or .xml oculus configuration files as I did not see any flags in the windows registry that seemed to be getting set. My intent is to at least get an idea what range value gets used for setting floor distance and possibly making a took that lets us bind the floor, as if from a standing height.
The 3rd party games tend to have seated support. Oculus Home and the major oculus backed games, are the ones that tend to not have seated support.
There are developer flags to have guardian setup utilize a seated mode option.
My point here is, Oculus Home itself does not use this, like many major games do. We used to have an offset height with the Rift CV, but with Rift S, it is not possible to physically lower the floor in guardian, since it's a physical check. That is the mitigation being asked for.