Autokey doesn't work for local Z-Axis in Camera view with MotionPaths enabled #37755

New Issue

Sebastian Koenig · 2013-12-09T15:55:49+01:00

Sebastian Koenig commented

2013-12-09 15:55:49 +01:00

System Information
Operating system and graphics card
OSX 10.9 GTX 660ti

Blender Version
Broken: Blender 2.69 964252c
Worked: don't know. was broken in 2.68 already

Short description of error
If you are in camera view and want to animate the camera moving forward / backward with autokey by doing g+zz, it doesn't fill in a keyframe as long as you have motionpaths enabled.
It does work fine if you move the camera along local z-axis in any other view.

Exact steps for others to reproduce the error
Open the attached file, press g+zz in lower 3D-Viewport and hit enter. You'll notice the camera jumps back to original position.
If you move the cam along local z in upper viewport, it fills in the keyframe just fine.
Seems to be caused by having motionpath display enabled
motionpaths_autokey_camera.blend

**System Information** Operating system and graphics card OSX 10.9 GTX 660ti **Blender Version** Broken: Blender 2.69 964252c Worked: don't know. was broken in 2.68 already **Short description of error** If you are in camera view and want to animate the camera moving forward / backward with autokey by doing g+zz, it doesn't fill in a keyframe as long as you have motionpaths enabled. It does work fine if you move the camera along local z-axis in any other view. **Exact steps for others to reproduce the error** Open the attached file, press g+zz in lower 3D-Viewport and hit enter. You'll notice the camera jumps back to original position. If you move the cam along local z in upper viewport, it fills in the keyframe just fine. Seems to be caused by having motionpath display enabled [motionpaths_autokey_camera.blend](https://archive.blender.org/developer/F37879/motionpaths_autokey_camera.blend)

Sebastian Koenig commented

2013-12-09 15:55:49 +01:00

Changed status to: 'Open'

Joshua Leung was assigned by Sebastian Koenig

2013-12-09 15:55:49 +01:00

Sebastian Koenig commented

2013-12-09 15:55:49 +01:00

Added subscriber: @sebastian_k

Joshua Leung commented

2013-12-10 07:35:53 +01:00

Looking into this, the keyframes do seem to be getting set correctly as expected. This can be checked by stepping forward and back, or checking the motion paths.

Instead, what is happening is that after the paths get recalculated, a hack is applied to restore the pre motionpath bake transform values (5847 in transform_conversions.c). This is needed because the motionpath baking process will overwrite anything that hasn't been keyframed already (which may still happen, even after enabling autokeying).

Looking into this, the keyframes do seem to be getting set correctly as expected. This can be checked by stepping forward and back, or checking the motion paths. Instead, what is happening is that after the paths get recalculated, a hack is applied to restore the pre motionpath bake transform values (5847 in transform_conversions.c). This is needed because the motionpath baking process will overwrite anything that hasn't been keyframed already (which may still happen, even after enabling autokeying).

blender-admin commented

2013-12-11 04:19:42 +01:00

This issue was referenced by blender/blender-addons-contrib@fcdc04af4f

This issue was referenced by blender/blender-addons-contrib@fcdc04af4f7c7c799dab5e5a38942ad6cc55b3d5

blender-admin commented

2013-12-11 04:19:42 +01:00

This issue was referenced by fcdc04af4f

This issue was referenced by fcdc04af4f7c7c799dab5e5a38942ad6cc55b3d5

Joshua Leung commented

2013-12-11 04:21:24 +01:00

Changed status from 'Open' to: 'Resolved'

Joshua Leung closed this issue