OrbitControl becomes less responsive the more you use it about three-d HOT 4 CLOSED

Ah, that makes more sense! It works great, thanks!

from three-d.

To be honest, I'm not sure if the magnitude of the up vector of the camera is used, but this solution normalizes the vector so the original magnitude is lost. If the magnitude is needed, I think it could just be calculated beforehand and then added to the vector at the end.

from three-d.

The up vector should always be a unit vector so I'm a bit puzzled why it's necessary, but it's a nice fix anyway 👍

from three-d.

Took a closer look, and it's probably because your up vector is not a unit vector when you call Camera::set_view, so normalized the up vector in that method instead in asny/three-d-asset@52d9a06 . That means we only normalize it once on input and ensure that it's always a unit vector, also when used in other places. Is it still working as expected?

from three-d.