Akihiro Oyamada

The function applyCameraUp triggers several calculations, as seen here: https://github.com/yomotsu/camera-controls/blob/cf392955edfec75e45c6a2dc36f53891319f3918/src/CameraControls.ts#L2475-L2491 I am concerned that making it animatable within the tick function might lead to performance issues. Typically, changing the camera's...

Did you already check https://yomotsu.github.io/camera-controls/examples/fit-to-rect.html ?

Thanks for using camera-controls. I think it's because setOrbitPoint calls setFocalOffset internally, and focalOffset causes many problems, like - https://github.com/yomotsu/camera-controls/issues/303 - https://github.com/yomotsu/camera-controls/issues/316 TBH, I would like to remove `focalOffset` and...

> setOrbitPoint with dollyToCursor Come to think of it, that's right. Would you mind providing a **simplified** working demo using codesanbox or so to just reproduce your problem? `setFocalOffset` will...

Thanks for your report. So, it only happens with a mouse wheel + shift key on macOS. (I need to prepare a mouse device for Mac then

As long as you use the cameraControls method, I don't think the "fighting" will happen, because each method will overwrite the final destination. Would you mind providing a simplified live...

you can call multiple methods at the same time to combine the camera movement.

I think that is intended. setLookAt does not change the viewport of three.js renderer. it just moves the camera position.

Sorry, I don't get the point of "viewport dimensions update". Could you elaborate a little more? I think you could just use an event handler or promise.

Sorry for the delay, I think you can just animate the boundary size in the user-land using other tween libs. Then set the animated result to the boundary of camera-controls...