Is there a way to prevent keyframes in a Matchbox animation channel outside of the inherent Flame Animation Channel tools?
Such as a flag within the Matchbox XML code itself?
That would actually be a great feature request: to be able to disable autokey by node.
Alternatively you can globally disable all key frames and explicitly set them in the required channels.
That’s all a pain in the ass and often leads to stupid errors. I (and I imagine many others as well) frequently build batches with element constructions up-stream and animation down stream. I probably don’t want autokey for the element constructs, but I do for the animation parts. It would be great for each node to remember its auto-key status.
2 Likes
It’s true.
but autokey right now is only a button push.
i’m assuming that if you get this autokey per node functionality that might also be a, umm, button push…
1 Like
Yes, it’s a button push that you need to keep pushing as you navigate between nodes. The node based solution means you can push it and, umm, leave it. Currently the autokey button is so global that if I turn it off in a batch node, it’s still off when I go to the timeline.
I always hoped that grouped animation channels would go some way to doing this - group all of the objects that should have no keyframes, select that group, delete all keyframes…
grouped animation channels is remarkably unintuitive in flame and fraught with failure.
anway - the labor saving idea of a no-animation pref button push quickly becomes increased labor when you have more than two nodes.
for the same quantity of button pushes you could also brainwash yoursefl to using ‘]’ or ‘k-click’
personally i commit pre-composited, non-animated feeder chains into a multi-channel openclip openEXR, kind of like BFX without the memory overhead.
but you know, cats, skinning…
FL-03610
1 Like