Timeline for Delete armature bone specific keyframe using python
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jul 3, 2023 at 15:46 | history | suggested | Sadern Alwis | CC BY-SA 4.0 |
"keyframe not in fcurve error" fix by reversing the keyframe_points
|
| Jul 2, 2023 at 22:56 | review | Suggested edits | |||
| S Jul 3, 2023 at 15:46 | |||||
| Jun 13, 2021 at 12:39 | vote | accept | Ahmed Ali | ||
| Jun 13, 2021 at 12:23 | comment | added | Ahmed Ali | I preferred to remove keyframes rather than copy and evaluate the keyframes span I'm after because in my use case the keyframes I tend to remove are much less than the ones I need to keep, so I thought it might work faster, but now I think it might be a cleaner way to start fresh and evaluate since in your linked answer you are using numpy for doing the heavy lifting. So thank you ;) | |
| Jun 13, 2021 at 12:22 | comment | added | Ahmed Ali | This question was a bit irrelevant to the other one I had posted earlier because I used a different simple action for testing it other than the motion capture animation. The keyframes were equally distributed along integer frame numbers in this file, the keyframe delete in both cases is frame agnostic anyway so it should still be deleted regardless, yet it didn't work. and your code still gives me the error "RuntimeError: Error: Keyframe not in F-Curve". | |
| Jun 12, 2021 at 17:56 | history | edited | batFINGER | CC BY-SA 4.0 |
added 58 characters in body
|
| Jun 12, 2021 at 17:49 | history | edited | batFINGER | CC BY-SA 4.0 |
added 432 characters in body
|
| Jun 12, 2021 at 17:42 | history | answered | batFINGER | CC BY-SA 4.0 |