You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
See VRDisplay.stageParameters.sittingToStandingTransform :
Current Behavior
Oculus browser returns default sitStand transform, we should consider doing this as well.
Expected Behavior
Not totally sure about this. But I don't feel there is any negative effects to having a default sitStand transform returned. The side effect of not having one is that some content will start at "foot level" if not properly handling the case where one is not present. Though rare, I have seen this in the past. Generally, it seems that it's expected from content creators to handle this case.
Possible Solution
Return sitStand transform.
The text was updated successfully, but these errors were encountered:
Note that on Wave and Daydream 6DoF platforms, we can provide this natively with real data. On Oculus Go, we just set the height to 1.7m and pass it through.
Did we decide to do anything here? I believe that this would just be for 3DoF / Oculus Go (since IIRC Randall said we get a height for 6DoF platforms). Or should we stick with the current default height for 1.1 and revisit later?
Just to be clear, we don't have a default height at all being returned since the sitStand transform is empty. We should probably return one or pass that through from the Oculus API if there is one provided. I'm guessing this is what Oculus browser does?
Hardware
Oculus Go
Steps to Reproduce
VRDisplay.stageParameters.sittingToStandingTransform
:Current Behavior
Oculus browser returns default sitStand transform, we should consider doing this as well.
Expected Behavior
Not totally sure about this. But I don't feel there is any negative effects to having a default sitStand transform returned. The side effect of not having one is that some content will start at "foot level" if not properly handling the case where one is not present. Though rare, I have seen this in the past. Generally, it seems that it's expected from content creators to handle this case.
Possible Solution
Return sitStand transform.
The text was updated successfully, but these errors were encountered: