-
Notifications
You must be signed in to change notification settings - Fork 324
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
Mobile has trouble with "forward" in landscape mode #59
Comments
My temporary workaround for this was to apply the screen rotation Q in
Unfortunately, that wouldn't work on Android because of the screen locking stuff. It seems that My workaround there was to just disable screen locking, though then I had to mess with the instructions display to make it work with the fullscreen wrapper. |
Just to clarify this issue, it happens only when starting in landscape mode—"forward" appears 90 degrees to the left or right depending on device orientation. |
I've tinkered with this a bit more and still haven't come to a satisfactory solution. To summarize, the initial world transformation should account for the device orientation, as should calls to resetPose. Unfortunately, when the orientation is locked on Android, it always returns the locked value, not the true orientation, which makes it difficult to account for. I'm not sure how to fix this without knowing the "true" orientation. |
We are using a "preparation" step to access the VR mode:
We have a trick to detect the orientation even if it's locked at the OS level, we use the We are still using an old version of the WebVR polyfill, without the |
I addressed this slightly, but it's still not perfect. c6720ed |
Alright, should be fixed now: 716f8a1 |
Great news! Thanks! |
When viewing the boilerplate demo on both iOS and Android devices, the rotating cube appears in front of me when holding the device in portrait mode.
When in landscape mode, the cube appears either 90 degrees to my left or right depending on whether I'm in landscape left or landscape right.
This happens even when I manually call for a resetPose. It seems that device orientation needs to be accounted for in the pose reset.
The text was updated successfully, but these errors were encountered: