Skip to content
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

Keep current pitch on compass navigation #1437

Closed
juanbrk opened this issue Sep 20, 2024 · 1 comment
Closed

Keep current pitch on compass navigation #1437

juanbrk opened this issue Sep 20, 2024 · 1 comment
Labels
Milestone

Comments

@juanbrk
Copy link

juanbrk commented Sep 20, 2024

Describe the feature

When rotating the viewer using compass navigation, the viewer's pitch is reset to 0 (likely the current default value). This causes users to lose the previous pitch context when navigating, which disrupts the experience. While it is possible to store the viewer’s textureX and textureY by listening to the PositionUpdatedEvent or BeforeRotateEvent, it’s not possible to discriminate between rotations from compass navigation versus other types of rotations.

viewer.compass_rotation_pitch_change.mov

Alternatives you've considered

I have tried storing the viewer' textureX and textureY by listening to the PositionUpdatedEvent (API Reference) or to the BeforeRotateEvent (API reference), but cannot discriminate between the rotation from navigation using the compass or any other kind of rotation.

If I could detect that the compass has been clicked and the viewer has rotated by listening to any available events, I could simply restore the viewer's pitch to Its previous value.

Additional context

When rotating the viewer using the compass, the previously set pitch should be maintained to avoid losing context. Detecting compass interaction should allow restoring the viewer's pitch to its prior position after rotation.

@mistic100 mistic100 added this to the 5.10.1 milestone Sep 21, 2024
Copy link

This feature/bug fix has been released in version 5.10.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants