New timeline breaks aniMate2
mastajappa
Posts: 20
Hi I finally figured out a nice workflow to create aniBlocks from animations but since version 4.12 it seams that the new timeline breaks the creation of aniblocks. Can anyone confirm this?
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
I also so noticed that once you use "Bake to studio keyframes" it breaks aniMate2 all together.
What do you mean by breaks?
I have found that the new animation system updates have really changed the aniblock <==> timeline behavior, and not in an obvious way, i.e. it's not like the paradigm used to be x, now it's y, but rather the interactions are not at all consistent in the 'master'/'slave' relationship between the two timelines.
I believe I can create aniblocks from the timeline, and I'm pretty sure I was able to burn aniblocks to the timeline in 4.12, but my efforts were fairly simple and for a quick project, so I didn't exercise it at any depth - but I was *not* the same as 4.11, and something I tried to do that had worked before in 4.11 did not work in 4.12, so I'm not surprised to see your comment.
Yes, something notable in the animate/DS timeline is changed and I don't know if it's intentional or a bug. DAZ doesn't really do documentation with their updates, so we have to kind of go blind until we figure things out again. And sorry, arcane 20 syllable release note mentions of such changes are *not* documentation.
Given the huge change in this part of the system in 4.12, I am pretty impressed at how well it is still working, because I think that level of update/integration was a truly massive undertaking - especially for a single-point update. But I'm also guessing these kinds of quirks will show themselves (and be fixed) over the next few updates.
Props to the devs for working on a better animation system, but it's safe to expect continued growing pains. Good bug reports will hep, but I'm still trying to figure out if these changes are bugs or a 'new way'. Updated docs would be the only way we'll know, so I'm not sure we will ever know.
it's not just you...
--ms
edit to add documentation comment
By breaks I mean that the functionality is not working or as it used to be working. But I found a workaround and I can get the results that I am after. I too wish stuff was better documented.