-
Notifications
You must be signed in to change notification settings - Fork 89
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
Support for control using combination of touch & motion as in Facebook #2
Comments
That's the intended behavior. When you enable motion control, the orientation of the camera is determined solely by the motion data according to some fixed reference point. Since the reference point is the same, keeping the device in the same orientation always results in the exact FoV of the camera. In short, you can't mix pan and motion as in the Facebook app. The reason I implemented it that way is to keep the correspondence between the physical orientation of the device and the FoV consistent. With all these said, I understand that not everyone would care about a fixed reference point, and prefer the Facebook way. That's why I might add that feature in a future release. |
I don't understand. I'm learning how to use SceneKit for 360 photos |
No, I'm saying that this library automatically sets the FoV according to the orientation of the device, regardless of how or when you modified the FoV before. As soon as you enable motion controls, it will immediately change the FoV to where it should be according to a fixed reference point. Therefore it's not possible to use touch controls without disabling the motion controls, or changing how the library works. |
I couldn't change location/position of motion, i.e, I'm trying that UIPanGesture when is ended, change to motion automatically, but the location must be the same as location(x,y,z) before that UIPanGesture has ended, just like Facebook.
But when is ended, the motion changes automatically but the position always resets depends of the orientation.
Sorry for my english
The text was updated successfully, but these errors were encountered: