My Keyframe Breakthrough
laststand@runbox.com
Posts: 866
I thought I understood what a "keyframe" was. That was my mistake.
I took for granted that when assigning a keyframe to a selected entity, the keyframe would, by default, be assigned to all the children of the selected entity. That's the way some programs work. Today, after scratching my way through years worth of posts I learned that was not the case. If you want the children selected, which will be most of the time, you have to go through the selection ritual. Otherwise you may get goofy results, as I have gotten for a long time. I found it, read it, tested it, and got perfect results for the first time ever. I was stunned. I may celebrate this day every year. If I had a cigar I would light it.
I would have made "Select Children" the selectable default. If I was a code jockey I would write a script that did this.
Maybe this will help you. Keyframing is easy. Discovering things like this, not so much.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
I'm not sure why you would want to kety children by default, except in the special case of applying a pose and wnating to key all the bones at once to lock it for that frame - which could probably be handled by a script.
dunno it's one of the things Carrara does by default and one of the reasons I dislike animating in DAZ studio
... mind you there are so many others
There are two reasons I would do that.
First, I learned keyframing in Flash. Flash does it. It's what I got used to. Keyframe means keyframe. No ifs, ands or buts.
Second and moreover, if it's a user-selectable setting, it is irrelevant why anyone would choose it. Usability rule of thumb = let the user decide. RESET TO DEFAULT is always there for those who prefer it.
:-)
.................
In my life I have been accused of imposing simplicity on inherently complex subjects... an accusation I am proud of to this day. ;-)
Poser does it too
The Daz Studio timeline has key type choices of Object, Node Recurse, Node and Properties, but I can't find documentation on what the difference is or when each should be used.
At first glance, Node Recursive (one post called it 'node reclusive') seems to get 'em all, selected or not. I can't find docs either. I'll experiment with this.
THIS from NOV19:
"Well, I think I may have figured it out, if anyone else has keyframes mysteriously changing on you for no reason you can decipher, check to make sure the box right next to the create keyframe button says "node recursive" in it and not just "node".
See https://www.daz3d.com/forums/discussion/comment/4870561/#Comment_4870561 for some basic definitions
This is valuable information Richard. Thank you. This is a fairly recent change.
I see that once this selection is made, it doesn't revert. It remains when the program is closed and reopened. This is handy.
Thank you, Richard. What is the difference between "for all nodes of the primary selected object" (Object) and "for the primary selected node and all of its decendants" (Node Recurse")? Does the second one include parented objects, like clothing and smart props, or have I guessed wrong?
I think that Object affects all nodes, not just those thata re descenfants of the selection, while Node Recurse affects only the selected node and its descendants - so if you had a figure seleced they would do the same, but with a bone selected they would be different. {Edit: yes, confirmed.]
Is it possible to disable automatic keyframing?