Inadequate bake action #33424

New Issue

Aleksey Loginov · 2012-12-05T23:03:36+01:00

Aleksey Loginov commented

2012-12-05 23:03:36 +01:00

%%%Hello, I've found a bug with bake action. This works with 2.62, 2.63 and of course 2.64 (even test and the last builds).
To get an adequate result I should to bake the animation twice. I've tried this on Ubuntu 12.10.

Attached file ready for repeat this issue.

Hit spacebar and typing "bake action". Then we get a strange feminine gait in character, despite the fact that this is a man.
To fix this we should to bake the action again.

%%%

%%%Hello, I've found a bug with bake action. This works with 2.62, 2.63 and of course 2.64 (even test and the last builds). To get an adequate result I should to bake the animation twice. I've tried this on Ubuntu 12.10. Attached file ready for repeat this issue. 1. Hit spacebar and typing "bake action". Then we get a strange feminine gait in character, despite the fact that this is a man. 2. To fix this we should to bake the action again. %%%

Aleksey Loginov commented

2012-12-05 23:03:36 +01:00

Changed status to: 'Open'

Campbell Barton commented

2012-12-06 05:44:11 +01:00

%%%this works correctly for me, once baked the animation looks the same as before.
I checked this by exporting a video of baked and non baked versions and then comparing them.

The bones are in different positions but the model looks the same.

I would guess that any change would be caused by constraints/drivers on the bones being applied after the bake is done.%%%

%%%this works correctly for me, once baked the animation looks the same as before. I checked this by exporting a video of baked and non baked versions and then comparing them. The bones are in different positions but the model looks the same. I would guess that any change would be caused by constraints/drivers on the bones being applied after the bake is done.%%%

Aleksey Loginov commented

2012-12-07 03:12:31 +01:00

%%%I've tried this on Windows and got the same bug too.%%%

Sergey Sharybin commented

2012-12-21 12:42:14 +01:00

%%%Seems to be happening when baking from pose mode only. Going out of pose mode and entering it back makes everything looking as it should.

Assigning to Bastien who're familiar with armatures :)%%%

%%%Seems to be happening when baking from pose mode only. Going out of pose mode and entering it back makes everything looking as it should. Assigning to Bastien who're familiar with armatures :)%%%

Bastien Montagne commented

2012-12-22 12:41:07 +01:00

%%%OK, so, X and Y location fcurves of foot_ik.L and foot_ik.R bones are the issue here… Each time you run the bake action op, they get inverted (in values, i.e. around the 0 X axis in FCurve editor)!

Kinda odd, have to dig deeper to see why this happens!%%%

%%%OK, so, X and Y location fcurves of foot_ik.L and foot_ik.R bones are the issue here… Each time you run the bake action op, they get inverted (in values, i.e. around the 0 X axis in FCurve editor)! Kinda odd, have to dig deeper to see why this happens!%%%

Bastien Montagne commented

2012-12-23 12:38:57 +01:00

%%%Ok, so that script tries to always make some kind of 'visual keying'... First of all, I'd say this is not a good idea when we keep constraints, in this case simply keying loc/rot/scale values (i.e. matrix_basis) should be enough.

When we do want to remove constraints, visual keying is needed. But not by doing everything in py code! We already have that handled in C code (and it's something tricky when you want to cover all corner-cases), so it's much better to expose the needed stuff to python.

My first idea was to simply expose keying options ('NEEDED', 'VISUAL' and 'XYZ_TO_RGB') to the keyframe_insert function (easy to to, will commit that anyway), but unfortunately this does not work in our case, as we want to key animation from action A into action B :/

So I think I'll expose the nice BKE_constraint_mat_convertspace() through RNA too… ;)%%%

%%%Ok, so that script tries to always make some kind of 'visual keying'... First of all, I'd say this is not a good idea when we keep constraints, in this case simply keying loc/rot/scale values (i.e. matrix_basis) should be enough. When we do want to remove constraints, visual keying is needed. But not by doing everything in py code! We already have that handled in C code (and it's something tricky when you want to cover all corner-cases), so it's much better to expose the needed stuff to python. My first idea was to simply expose keying options ('NEEDED', 'VISUAL' and 'XYZ_TO_RGB') to the keyframe_insert function (easy to to, will commit that anyway), but unfortunately this does not work in our case, as we want to key animation from action A into action B :/ So I think I'll expose the nice BKE_constraint_mat_convertspace() through RNA too… ;)%%%

Bastien Montagne commented

2012-12-28 14:36:24 +01:00

%%%Fixed in r53369. Thanks for the report! :)%%%

Bastien Montagne commented

2012-12-28 14:36:25 +01:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2012-12-28 14:36:25 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Inadequate bake action #33424