Timeline for Efficient way to programmatically copy shape key animation from one mesh to another
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 20, 2022 at 16:48 | vote | accept | FamousSnake | ||
| Sep 20, 2022 at 16:48 | answer | added | FamousSnake | timeline score: 2 | |
| Nov 9, 2021 at 20:44 | comment | added | FamousSnake | Oh my god, I just spent so much time writing new version of my script that would create fcurves identical to the base action. I was not realizing that actions are not attached to the mesh and I could have just rename all shape keys and that would work. Thank you! PS Never heard of foreach_set method before know, it might actually save some time in the future, thanks. | |
| Nov 9, 2021 at 20:06 | comment | added | scurest | Well, it kind of matters. keyframe_insert is for inserting into existing fcurves. If you're making a new fcurve it's much faster to use foreach_set. And it's even faster to just copy an action and rename the keyblocks its fcurves target. | |
| Nov 9, 2021 at 20:02 | comment | added | FamousSnake | @scurest kind of | |
| Nov 9, 2021 at 19:47 | comment | added | scurest | If you have one action on the base sk that you want to copy over to one new action on the dest sk, renaming keyblocks, there's a much faster way. Is that what you want? | |
| S Nov 9, 2021 at 17:49 | review | First questions | |||
| Nov 9, 2021 at 20:11 | |||||
| S Nov 9, 2021 at 17:49 | history | asked | FamousSnake | CC BY-SA 4.0 |