-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sittingToStandingTransform may be a misnomer? #26
Comments
Comment by Sneagan I agree completely with the point and do like |
Comment by toji sitting/relative/start-point-local has to be the default space, because it's the only common space between all the systems we want to support. Works for everything from Cardboard to Vive. |
Comment by Sneagan Awesome, that's what I was hoping. That said, though,
Reading these I realize I may be conflating sitting and standing with fixed position and room scale VR unnecessarily, but that feels like the real distinction we're making. |
Comment by toji I don't have a problem with the That's why I like the term "stage", because it's a pretty good analogy (I feel) for the configured play space. A theatre stage is a confined space that the actors have to move in, but through clever scenery changes and theatrical tricks can feel as though it represents a much larger world than the actual floor space suggests. Describes the room-scale VR experience pretty well! |
Comment by Sneagan Ah that's clearer. I'm completely behind |
This is being addressed by #149 |
Issue by toji
Wednesday Mar 02, 2016 at 21:45 GMT
Originally opened as MozillaReality/webvr-spec#18
A bit of feedback I've received is that the concepts of "sitting space" and "standing space" that we've borrowed from OpenVR may not be accurate representations of the values we're providing. For example: It's definitely possible to stand in place while using an Oculus Rift, and you probably want to when using controllers like Touch. Since there's no sense of where you are in relation to the room, this would still be reported in "sitting space", though. Similarly, you may want to sit down with a Vive but still have the scene oriented to your room using "standing space." The actual values reported right now in either case should be fine, but the verbiage is weird.
I propose that we run with the verbiage of "stage" that we've already defined. So
sittingToStandingTransform
becomesstageTransform
. We'd also have to come up with a term for the default space ("relative" comes to mind but may be too vague) and change some verbiage in the spec, but otherwise everything continues to work the way it does now.Or we could just decide that this is a silly thing to worry about and move on. :)
The text was updated successfully, but these errors were encountered: