Congratulations! You are a March Madness BONUS BUYER!

Enjoy 10% OFF* ALL PURCHASES STOREWIDE or enjoy 30% OFF items with a SKU number lower than 16000 & 30% OFF items from Runtime DNA.

Buy any "Newly Mad" or "Still Mad" and get an EXTRA 60% OFF**:

Star 2.0 Stellar BundleCallie 6 Pro BundleToon Generations 2 Essentials for Genesis 3Karen 7 Pro BundleCaptain Charisma for Genesis 3 Male

Offer valid for intended recipient only
* 10% discount DOES apply to Gift Cards and Memberships. **Items must be in cart simultaneously for discount to apply.
[ collapse ]

Using the DS4 Timeline to craft a "photoshoot"

edited December 1969 in Daz Studio Discussion

I'm still pretty new to 3d art and Daz Studio etc. but I have decades of professional software development experience and tend to "play" pretty hard when getting into something new.

One thing I've tried to do starting early on, is to use the timeline to organize a "photoshoot", a series of still images. DS seems to somewhat invite this, e.g. in the built-in "series of still images" options in the render settings tab. I sometimes found the animation on the timeline useful for this, as the interpolation of poses and camera positions can "find" views that look good to me that I did not specifically create. But I also often found I wanted to have a series of images with figure(s) in precise and stable poses in themselves and in relation to props and other figures. But the timeline, in my attempts, did not seem to be well suited to this usage.

It slowly became clear to me that that is mostly "by design" in that the timeline is intended for animation and not for a series of static poses. For example, suppose in frame 5 you have a figure precisely posed and it happens that the Abdomen has a twist of 0. Then later in frame 12 you for the first time apply a non-zero twist to it. If you go back and look at frame 5 after doing that, the pose has changed because a non-zero twist has been interpolated back onto the Abdomen. And that can move the arms, and if the hand on one of those arms was supposed to be on another figure's shoulder, well it isn't anymore. OK (actually ouch!) after some study it seems I must accept that DS is working the way it was meant to, but that's still a 'problem' for me in this kind of project.

Through several iterations I have crafted working versions of scripts that I can use to "force", "guard", and "repair" keyframe values down through the entire figure across the timeline as I work frame by frame, so that the poses should remain stable. This was a lot harder that I expected; the biggest problem being that "some actions" (I have not nailed down which) reach back through the timeline and remove some of my keys in earlier frames. So the latest version of my scripts actually save a private copy of the translation, rotation, scale, and morph values in each node by frame and can check and "repair" the pose in each frame if it finds that later changes moved the figure in some unintended way.

Well, that was a lot of work and I'm not exactly sure it was really necessary (as I still wonder if someone has an easier way), but it was very worthwhile to learn enough about the DS object model and scripting to be able to do all that [there are a few dark corners and some gotchas! that I hit, but overall I rate the DS scripting capability as "awesome"]. But now I wonder if it was really necessary, and if it is of interest to anyone else. I have these questions to toss out here:

1. Is this use of the tools - to create a "photoshoot" as a series of still images of figures and props with precise and coordinated poses and positions - not common? Is it, perhaps, too "novice-level" as an approach?

2. Or, do more experienced and knowledgeable users have some preferred way to do this kind of thing, either having tamed DS in some way I did not recognize or using some other tool? Did I miss something basic?

3. Or, do lots of other users want to / try to do this with the DS timeline and more or less either struggle or give up?

I'll be very pleased to hear back from the community with any thoughts on all this.


  • Oom FooyatOom Fooyat Posts: 0
    edited July 2012

    I use the time line for setting up developing scenes and "posing sessions" all the time.
    I had the same problem and found a solution in the Edit drop down menu by using first Memorize Figure Pose and then immediately Restore Figure Pose. This will "lock" all bones in the frame but not all shapes, so you still have to be a bit careful. The two commands are now in one of my tool bars for easy use. To lock a prop or camera use the small + key in the time line control bar.

    Cheers! Oom

    Post edited by Oom Fooyat on
  • edited December 1969

    ... first Memorize Figure Pose and then immediately Restore Figure Pose. This will "lock" all bones in the frame but not all shapes...

    Thanks for the comment, Oom.

    Indeed, the very first version of my scripts just used Memorize/Restore Figure Pose to stomp keys for all(?) the bones for all selected figures; I had options to stomp the current frame itself, or to stomp from the prior frame (useful when I made a mess and wanted to start over on a frame ).

    But then, well into a multi-frame shoot, I looked back and still found my coordinated poses back at a number of earlier frames appeared to have been corrupted. My second version of scripting walked the skeleton and explicitly set each property to be "sure" it had a key at that frame. Alas! that still was not enough to be completely reliable for me. By dumping data to the debug log using still more scripting, I eventually found that "something" can "sometimes" reach back through the timeline and delete the keys on rotation properties on "some" nodes; this frees them for the animation to take hold and the effect, given what I am trying to do, is to destroy the poses. I'm still not sure what removes the keys, but it seems it must that some native action in the DS GUI (active pose? 'reset' property?...) is coded to be too clever. At least that's the way it appears to me.

    I found this vastly frustrating. But my latest version, in the process of walking the skeleton and stomping those keys, saves (in custom data) a copy of the property values in that node at that moment in that frame, and can verify and restore them later if / when "something" decides to unkey them. (I hope eventually this will let me nail down the actual culprit(s), too).

    Heh now it seems I'm having so much fun learning to correctly script this thing that I've nearly forgotten what my actual DS project was about :)

  • cridgitcridgit Posts: 917
    edited December 1969

    Thank you for sharing that story. I've followed a very similar path and also started scripting for similar reasons. I also almost forgot what the original project was about - I guess we fall back into our comfort zone eh? :-)

    Anyways, I just kept adding and adding functionality to my scripts and that eventually became PoseMaster - my first (and only) product. If you've done some cool stuff for the timeline you should consider releasing it as a product - I'd be interested. I'm no CG or animation expert, but I find both the timeline and Animate+ quite difficult to do what I want them to - even for my fat fingers.


Sign In or Register to comment.