No the constraint is only there to help me to find the right camera position inside blender.
All my camera's have a coupled empty, it is realy convenient in use.
Then i make an ipo for position and rotation , and because pyprp does not support constraints the result follows the path.
Here is an example of the setup including an camera ipo path.
hmm, the new camera is activated when the avatar enters a region but the animation is not triggered yet.
then the avatar clicks on an object which is only possible if its inside that region.
That triggers ( under more) the camera animation.
it follows the path correct , but also keeps track of the avatar and it should not ., because i want the camera to zoom into a note i left inside a drawer.
The camera returns after a few seconds to its initial position, after you had the chance to read it.
It alll works, only when it zooms to the note the camera also turns 180 degrees unexpected.
The drawer itself is also animated and is used as a constraint to the cam instead of a focuspoint as in the example.
This helps to make me a smooth ipocurve .
The note is actualy nothing more then a texture on the bottom of drawer.
May be i post the script later but the same script also triggers some more things.