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
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.
The text was updated successfully, but these errors were encountered:
Describe the feature
When rotating the viewer using compass navigation, the viewer's
pitch
is reset to0
(likely the current default value). This causes users to lose the previouspitch
context when navigating, which disrupts the experience. While it is possible to store the viewer’stextureX
andtextureY
by listening to thePositionUpdatedEvent
orBeforeRotateEvent
, 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
andtextureY
by listening to thePositionUpdatedEvent
(API Reference) or to theBeforeRotateEvent
(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.
The text was updated successfully, but these errors were encountered: