-
Notifications
You must be signed in to change notification settings - Fork 20
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
Camera Controls changes position very slowly over time #4614
Comments
Thank you for reporting, we will have a look. |
Hi, @joao-mbn - we are aware that the default camera manager have a few issues, and it seems that this is one of them. We do have another camera manager under works. You can try this one out by setting the "useFlexibleCameraManager" option to |
Appreciate the feedback. Since we're going to put this in production soon, I'll better stick with the devil I know. In any case, I'd love to know if the fix for this is on your schedule any time soon; or you have an idea of what's the problem, in case we have to roll-out our own camera manager. |
I see. Unfortunately we are currently not planning any improvements to the current camera manager. Rather, we aim to replace it by the new one in the next major version of Reveal |
I see, thanks. |
Camera controls may become very slow over time, specially for zooming (dolly) and going sideways (truck). It happens with mouse, ASDW keys and touch screen. Pressing shift while controlling with ASDW will make it faster, but only in comparison to the other methods. It remains nonetheless slow.
I was able to consistently reproduce this by scrolling towards the horizon on the view, but it persists when I again focus towards nearby nodes (Gif 1). If I go back and forth, always focusing on the nodes, it gets very slow over time too (Gif 2).
Gif 1
Gif 2
If I reset the camera state with Cognite3DViewer
setViewState
method, it gets back to normal (Gif 1, when I click the Home button). Tests changingautomaticControlsSensitivity
anddollyFactor
parameters didn't make a difference. We use theDefaultCameraManager
without changing any parameter.We ruled out memory or CPU problems by monitoring them while reproducing the bug, with no noticeable change in either. We tested in Windows machines and also with a Mac using an Apple Silicon chip (with Christian Flasshoff from Cognite), and it could be reproduced in all instances.
As for the relevant packages, we use:
As for configuring the
Cognite3DViewer
, we have basically this setup:The text was updated successfully, but these errors were encountered: