2.4x port by Ivo Grigull (loolarge)
from the tracker:
It should be working ok, but it does not have all options that the old script had. You can only specify the start frame
where to insert the animation, but not skip frames for have a different fps.
However, like the old script this will bloat the memory a bit, at some later point i would like to write a script that
only reads the current frame from the file when you move the timeline.
ported by Aurel W (aurel)
made adjustments to have this as a package in the extensions directory since this format isnt commonly used for interchanging data but still useful at times.
Example which is similar to interactive lamp adjusting in 2.4x ...
wm.context_modal_mouse(path_iter="selected_editable_objects", path_item="data.spot_size")
Added lamp Wkey menu back.
- euler/quat rotation option
- scale, startframe options back.
- fix for adding an armature which used operators can could fail, use the data api instead.
- remove old junk
Examples.
euler = Euler(1, 2, 3)
euler.order = 'ZXY'
euler = matrix.to_euler('XZY')
Still missing rna support. this still wont give the right order, defaulting to XYZ.
eul = object.rotation_euler
* Added a user-preference setting which disallows setting the current frame number to a negative number. This setting only applies when setting the current frame by scrubbing the time cursor in a timeline view, or by typing a value into the current frame number field.
* Made the minimum frame number for the start frame to be 0, which should make setting keyframes by a regular step size less confusing. Also changed the MINFRAME define to 0 for consistency. Hopefully this doesn't cause any problems with any output formats.
* Fixed some missing channel selection cases in animation editors.
Running scripts directly didnt call the register function, even though this is not essential its good to be able to run a script directly and see changes in the UI.
Added a tail control rig.
For now, you have to manually hook the resulting controls up to a separate spline IK rig that you make by hand. Perhaps this can be automated in the future.
For anyone using this: keep in mind that you need separate armatures for the tail deformation bones and tail control bones. Otherwise you create a cyclic dependency like so:
tail deform bones <- spline object <- tail control bones
reloading bpy_types was causing reload to fail. also unregister all modules in the reverse order that they were loaded, so when reloading removed files done hang around.
