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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Yeah, there doesn't seem to be much urgency on Daz's part to fix this. Which is kind of surprising to me, since we're talking about actual *data loss* here. Bugs don't get more serious than that.
This is what it looks like to me. There seems to be a bit of "shiny new thing" mentality. I'm all for shiny new things, but I like to see existing features maintained and improved, too. dForce and Iray are features that seem to be continually updated. Others seem to languish after release.
It gets frustrating, but we have no visibility to the Daz Studio roadmap or Daz3D company priorities.
Besides moderators, does Daz look at these posts? I get that it's a free program, but we all pay money for the content and atm we animators cannot use that content due to these issues. That's not a good business strategy for keeping a healthy client base. I'm not trying to rally here. I'm genuinely curious because we don't get responses and we are left in the dark for very long periods of time. My business would fail if I pulled something like this. Truthfully, I'm very surprised by this. I've always looked very highly at Daz.
I am personaly not affected by the keyframe deletion bug as I stopped at version 4.12.086
However I remember there was a major show stopping bug with Iclone & NIVIDIA drivers with one of the early versions of Iclone 7 and Reallusion put the previous bug free version in the product downlodas of anyone who requested it.
IMHO Daz should do similar in this case as they have publicly acknowledged that this is a systematic failure of the current build
Jesus, iClone. Is there a program of theirs I've tried that doesn't crash when you try to import a Daz character into it? I don't think there is. Execs concentrate on the shiny because of cashflow. They don't have to deal with the bug reports and the cost of fixing problems hits the bottom line in six months time, not now.
I've joined the club of people deeply troubled by this issue after accidentally updating from 4.12.0.86. I have a CS ticket open to get the 86 install files, but haven't had a response in 2 weeks.
HOWEVER, I come bearing (moderately) good news and a little expanded info after a bunch of testing.
There is a workaround that has worked for me, though you've gotta be disciplined to not forget to do it. The morph keyframe data is lost in SCENE files, but NOT in PROPERTY PRESET files. Therefore, if you save a Property Preset with all keyframes of your figure before shutting down, then apply that preset after reloading, you'll get your morph animations back.
Also, it appears stock morphs are not affected by the data deletion. I know this doesn't mean much because lol...99.999% of the morphs we use aren't stock. Perhaps though it will help someone find the bit of code that isn't meshing so to speak.
Amen. I rarely use the spline graph editor, so it does nothing for me but take up priceless screen real estate.
Oh, please, please, how do you do that? I've just had DS 4.12 destroy hours of work animating morphing flame—which of course now doesn't morph. I tried copying the 4.11 zip from my old computer to my new one, but I can't get DIM to see it or install it. How are you reverting back to GraphMate and Keymate? I'd give anything to so I can SALVAGE this commissioned animation, and I have to do it on my new computer, not on the old one that has 4.11!
I save everything as an animated pose now, also so I can use it in Carrara
complained a while back in the beta forum my animations were not loading the same in saved scenes when nobody else was seeing it yet so just found my own workaround
there is also a hip rotation issue this script on this page fixes
https://www.daz3d.com/forums/discussion/comment/5582166/#Comment_5582166
Honestly, it's getting kind of ridiculous at this point. Daz has been aware of this bug, and other timeline-related bugs, for *months* now, yet we've received no word from them on when (or even if) it's going to be fixed. I don't think I've ever seen a software company take such a cavalier approach to a bug that causes actual data loss. It's not like this is some minor UI glitch or something... It's a *major* bug that is having a direct impact on many of Daz's customers' livelihoods. I mean... grrrr! /rant
The fact that they have not updated the Highlights thread for several version releases and there has been no update in the change log for weeks and weeks is also very concerning. It makes me wonder whether the main developers left the company or something.
another thing I must point out I discovered doing Dforce sims but applies to everything
DAZ studio no longer creates a keyframe at the beginning of an animation unless you click the add keyframe icon on the timeline
on anything
so you pretty well have so select everything and add a keyframe
Apparently things went sideways with some version after 4.12.0.86
It is all Moot to me as, I have migrated my Character animation& Figure clothing creation pipeline completely over to Iclone 7.x and Character creator 3 Pipeline and Blender 2.8x And will never even bother to install any version of Daz studio after 4.12.0.86
As far as Daz's response... There is this matter of a global pandemic and Richard has publicly reported that Daz inc is working remotely and for all we know the Daz programmers may have been personally affected by the Covid-19 virus.
Okay, thanks. I didn't know that GraphMate and KeyMate ever could work with any version of 4.12. Was that only up to 0.86, or can they still work with current versions of 4.12?
However from all reports, the crippling problems with animation Data loss are a separate matter and likely would not be solved by installing the older graphMate & KeyMate plugins in the recent builds.
Thanks, wolf.
Yeah. Can't say I blame you. What a vacuum.
We should be able downgrade to the version 4.12.0.86 until this issue is resolved
It can't be that hard, right?
No.
Well ..yes if you have saved your older Daz studio intaller .exe's
I have old installers goiing back to version 4.8
I managed to delete 4.12 and hoodwink DIM into iinstalling my saved 4.11 on the new iMac with Catalina, along with KeyMate. So far it seems to be working fine, and I am rid of the ineffable animation bugs infesting 4.12. Morphs are working, and keys stay where I put them.
Somebody should send the Daz team the "If it ain't broke, don't fix it" memo. I would, but somehow don't feel like sitting around for two weeks waiting for an answer.
UPDATE: I don't know why I was so foolish as to believe DS would actually work. Overnight I rendered a 360-frame animation out to a networked drive. That worked. But now DS suddenly refuses to open any DS scene file. You may think that is a typo. No, it absolutely refuses to see any scene file I've ever saved as an openable file. In the "Open..." requester, every file is greyed out an unselectable. I've quit and restarted DS several times. I've rebooted. Nothing. The Mac Finder sees the scene files as openable by DS, but if I double click on one, DS opens, but with no scene loaded. Most bug-ridden software I've ever used in nearly 40 years of computing.
Just been reading up on this method but it seems that the properties preset does not save geografts and, as some of my characters have them, I'm looking for a more comprehensive solution. Still no fix from the DAZ team though which is really disappointing.
[EDIT] - I should have tried it before I decided it wouldn't work. If I apply the preset to a character already in the scene it applies the pose/morphs, etc., as I saved them using the preset. The geografts remain attached. So many thanks for the tip.
Any news on the bug fix for this issue from DAZ?
Try disbaling AniMate.
There is a new entry in the Change Log http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_12_2_40
Thank you for pointing it out, Richard. It is encouraging to see some action on timeline bug fixes.
Well, this is of course the fruit of action that had been going on for a while - but nothing appears in the change log until there is a change to report.
... And the change says "fixed". So the burning question now is how long before we get a new beta? I don't remember such a long gap between beta releases.
I swear, I'm going to get the Daz logo tattooed on my forehead if they really did fix the Timeline / IK bugs
I didn't see any mention of IK fixes.
When I go to the link, there is no 4.12.2.40 entry?