OrbitControls rotates object confusingly when camera.up is (0,0,1)

[jasongrout]

It seems that when I set the camera's up vector to (0,0,1), OrbitControl's mouse behavior is very confusing. The object moves in a different way than the pointer moves, etc.

[WestLangley]

OrbitControls only supports the default (0, 1, 0) up-vector.

three.js r.65

[jasongrout]

Thanks for confirming this. Okay, then perhaps this issue is more of a feature request (and reminder to me to work on this or assign a student to work on it). It seems like it should be pretty straightforward to hit any movement with a transformation matrix to orient it relative to the camera's orientation.

[ekatzenstein]

I agree this would be really helpful to make these updates!

[mortenjust]

Thanks for that update. It seems to act a bit odd in two ways after camera.up.set; Auto rotate is on the browser's x axis (expected y axis), and when dragging from up to down, it isn't possible to do more than one orbit, while from right to left is not a problem.

[jasongrout]

1. I thought this should be closed, since Set camera.up vector as the orbit axis in OrbitControls #4530 was merged a long time ago and fixed the issue.
2. @mortenjust - I think that's how orbit controls work. You can cap the up/down motion angles to other angles if you like. If you want freeform movement, look at the trackball controls instead.