Started the animation. At this point the feet slide along the ground as he moves forward and an animatic has been setup for the rough timing and layout.
The first problem I found was trying to use the null object scripts. The null is a marker object that does not render and behind the scenes is a modified camera. The unofficial updates has a camera background widget for opening a panel and exiting a camera view. This prevents selecting a camera and then ctrl selecting anything else in the 3d view. The second problem was from the way trueSpace works. If you have 2 cameras selected (or a camera and a null) the fov for both will be set to the same value. So when I had a camera and null selected the camera's fov got messed up by the null fov. I ended up converting the nulls to ordinary meshes and will manually make them invisible before the render is run. I deactivated the Exit Camera View portion of the camera widget.
The reason for the nulls in the first place is to use constraints to make the camera switch locations via the null locations. This process uses a new version of the constraints script that allows the unconstrained values to be animated. The new script is highlighted in yellow in the image. The camera position is constrained to each of the "null" positions in turn with the rotations available for animation.
One more problem when I started the animation. The meshes got keyframed and that made the whole thing kindof blow up after a couple of keys were set. The solution was to expand the Matrix connection for each of the meshes attached to skeleton bones.
On a side note I needed to use the ctrl script for link editor selections in a floating le window, but the button only exists on the main le window, so I plan to install the ctrl script to get the button and use the opportunity to check for a potential problem with the persistent installers found by trueBlue.
