[sharing] 3D Camera Movements in Max 6

nice, can't wait for your gen recipes :)

thank you Andrew!!!

Hello Andrew,

First i want to thank for this wonderfull example !

But i have a litte problem:
I am trying to stare and recall different views of the camera.
I am grabbing the position and the rotatxyz attributes.

But the stored and the recalled views are not the same.

Is there an other attribute as position and rotatxyz, which
is set, when moving the camera with "move" and "turn" ?

Thanks for any help,
TT

here is my example patch:

hi timtom. the views are the same. it's just that every time you bang your preset, it is causing the scene to be randomly regenerated, because your preset is including the main toggle that triggers the scene randomization.

thank you very much for looking into the patch robert.
now it works !

one little thing is not clear from my point of view.

the pattr oblect, which is bind to the rotatexyz attribute of the camera
is not outputting the attribute if you change it with the mouse
(using the jit.anim.drive)

also the cameras attrui object does not update.

here is a smal example:

hi andrew - is there any way to set limits on an axis of camera rotation? - I'd like to be able stop the camera from looking too far up or down.

i am considering adding limits as a feature to jit.anim.node, so your request is registered.

in the meantime, you can to this yourself simply by keeping track for the current camera x and y rotation, and not allowing additional rotations when you've reached your limits.

the example patch Max6/examples/jitter-examples/render/anim/anim.camera.advanced.maxpat
give one way to do this in the "limit-orient" sub-patch.

Robert - thanks, but unfortunately the anim.camera.advanced.maxpat example you gave uses mouse movement as input, unlike Andrew's example, which uses jit.anim.drive, and so it's not at all obvious how the 'limit-orient' sub-patch could be repurposed for jit.anim.drive -- since jit.anim.drive has to be connected directly to the object/node that it's controlling.

actually, jit.anim.drive does not need to be directly connected.
it simply outputs animation messages (anim_turn, anim_move, anim_grow).

however, note that the fourth argument to the animation message is speed, and needs to be multiplied with the first three args for proper scaling of the animation.

you can set the @targetname attribute manually, and bypass the need for direct connections.

but yes, i agree limit attributes would be useful.