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

GlobeControls: Understand why controls seem less responsive / slower depending on framerate #656

Open
gkjohnson opened this issue Jul 25, 2024 · 1 comment
Milestone

Comments

@gkjohnson
Copy link
Contributor

Even though pointer events are being used.

@gkjohnson gkjohnson added this to the v0.3.37 milestone Jul 25, 2024
@gkjohnson
Copy link
Contributor Author

This may be specifically when the framerate is lower due to low battery meaning even events are fired less frequently and therefore (should) have larger values since more motion has happened between events. I've noticed this only with zoom and it's likely due to this zoom speed normalization function:

const normalizedDelta = Math.log( Math.abs( delta ) + 1 );

which attempts to normalize zoom speeds by using a logarithmic scale. That means that larger movements will be scaled down causing a difference in apparent speed.

Not exactly sure what to do here.

@gkjohnson gkjohnson modified the milestones: v0.3.37, v0.x.x Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant