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
Does KeyMate still save the animation morphs? I like the direction of the new DS timeline, but it's still buggy, I agree not saving the morph animation is a show stopper, but it's better to discover the problems during Beta's. I find It's difficult to do keyframe animation in DS using the standard DS timeline, without KeyMate 2 (the paid version). I would continue to use keyMate until the bugs are worked out of the new timeline. I'm glad to see DAZ is finally addressing the DS animation capabilities.
My two cents worth...
It is not a beta problem. It is on both the beta release and the general one. Additionally, it has nothing to do with the new timeline, and KeyMate makes no difference. You can use the regular production version of Daz Studio with KeyMate all you want, it's still not going to save your morph keyframes properly.
I'm flabbergasted that something this critical still hasn't been fixed after such a long time.
It has been stated on one of the thread pages that it is a w.i.p.
The trouble is, there has been no tangible progress since these bugs were identified many months ago, no communication as to approximately when we can expect a fix, and no way to use the old (limited but at least usable) timeline in the current release of Daz Studio. It's a prettt frustrating situation for many of us.
Intermediate timeline. Not sure if this has been mentioned or not but when I am in intermediate timeline mode the timeline shows ALL the keys in a scene. The problem is that when you have multiple figures, cameras, lights, props it is impossible to find specific keys for whatever figure/object you are working on. Example....I opened up a scene I am working on in 4.1 and I needed to figure out where the keys for Camera 2 so I could st the render range. Impossible to do when ALL the keys for every single object/node is shown regardless of what is selected and if I use the skip to next key button it doesn't always work.
I mentioned 4.1 for a reason. The advanced timeline is great for people who want extra bells and whistles but not everyone needs or wants that and not having the simple functionality that 4.1 had makes the newer version impossible to use for myself and I dare to say perhaps others as well. Make intermediate have the same functions as it had in 4.1.
I use a portable version of 4.1 since it actually has a functioning timeline, I do not need a dope sheet and I find that just to edit a single key went from simple in 4.1 to a headache in the latest version.
For the record, I don't remember ever seeing Daz give an ETA on bug fixes in all the years I've been using DS (which would be since the first public beta ever), except maybe "soon".
Not sure if this has been reported, but I have encountered some strange issues with the beta. Sporatically, Nvdia Iray was not an option in the view (Draw Style Options). It simply disappears as an option. This seemed to occur when I was creating a plane in Z position and moving into the surfaces tab. When I tried to duplicate the scenerio Daz shut down and I got a fatal error report a bug pop up. Also finding having to shut down Daz via the task manager (seems to be taking longer than normal to create log files) and by doing this of course the log file is incomplete. Took a few screenshots (on offline PC) if needed. Also viewport blocks view of model at times.
Edit added pics. Fatal Error.Viewport no showing model. Iray Missing from view options and soemetimes all is well and NVDIA Iray is an option. When the viewport did not show the model, I was also creating a primitive plane z position. It seems as though somehow when making the primitive plane it defaulted to 3Delight and my understanding is since 4.11 the default is Iray. I have to date, never rendered in 3Delight and did not choose that option. In 4.10 when making a primintive plane I would choose preset shaders and Iray Uber which supposedly is not necessary since 4.11
x
I am not connected with DAZ but I know for a fact DAZ is having some store/bug issues. If I owned or ran Daz my priority would be fixing the store not a beta because the store is what fuels the betas.
The people who handle website issues and the people who develop DS aren't necessarily the same people, or even fungible.
Anybody else see this issue? I'm running 4.12.2.6 with Nvidia driver 452.06, Geforce RTX 2060 Super. I bring up a G8F and go to render in IRay - the image window opens but nothing is ever displayed in it except the checkerboard. The status runs as usual until it says it is complete in about a minute.
I go to the image window and do a save. Sure enough the image is complete on disk, but it was never displayed in the window. And, yes, it is not set to write direct to disk.
Good to know Daz has a separate team of developers handling back end vs software.
Oddly enough, the Nvidia driver install didn't require a reboot - that should have set off warning bells for me. After reboot the problem went away.
Is this similar to your experience. It happened with my 2080's.
As I said just a few posts above yours, this is a bug in both the beta and the general release. If it was just a beta bug, this wouldn't be a problem at all. As it is, Daz does not currently, and hasn't for several months, provided a version of their software that doesn't destroy keyframes on morphs. Just because you're not having this problem doesn't mean it's not critical. As a software developer myself, this is the kind of severe bug that my team would get a fix out for by the end of the week in which it was reported, and my team is roughly the same size as the Daz team.
Sorry if it's been asked or in another discussion somewhere. Has anyone else had or having issues with content in Daz Studio not working, but working if you download and install through DIM? To help clarify I installed content through/ inside Daz Studio directly and most worked, but some would not work and kept giving me error logs. So I downloaded and installed through DIM and the content worked fine.
"Installing through DAZ Studio" is using the built-in Connect system. Yes, there are a few things it can't handle right now and must be installed with DIM. IIRC it's some plugins, and the Generation 4 figures (Michael 4, Victoria 4, Kids 4, etc.) all of which are pre-Genesis, because their morphs must be installed in a way Connect can't handle. They'll install, they'll load, they just won't work. <headdesk>
Is it correct that there is still no change to the animation issue even in the private beta? http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log
It kinda feels like they don't really care about it.
"Working on it" is not something that will appear in the change log.
Understood, thanks for the reply.
Favorites saving were not working 2 versions before, that was also a problem as rendered favorittes nearly useless. One version ago they were fixed, and was possible to do something in animation. Now the current version breaks a basic animation feature, save morphs.No sure a new key editor should have been added when breaks a core feature that makes impossible many types of animation, specially when the version before was working fine. Feels rather a downgrade.
I have spend several hours tryign to figure out why was not saving the morphs . At least I know now.
I'm running Daz Studio 4.12 64 bit on Windows 10 Enterprize with Intel Core i5-4570T CPU @2.90GHz. And I have the Genesis 8 Model installed, and every time I load the base figure in, I get this creepy looking body and figure shape. And the only way I found to get rid of it is to uninstall Daz Studio, clean up the registry, and re-install. Is there something wrong? Is there another way around this? And what would cause it to happen?
Mod Edit :- Image deleted due to nudity
I may be wrong, so don't just do this, but I recall having to unistall and reinstall Genesis 8 Essentials, but maybe Haseltine would know if that's the case.
https://www.daz3d.com/forums/discussion/comment/4448441/
It has nothing to do with DazStudio, just a wrongly saved morph ...
Anyone know if they're going to be updating the version for the new rtx 3080 series sooner or later? I'm not familiar with their update priorities.
They don't tell us their update priorities. We just have to wait and see what comes and when.
Someone posted a link to an nVidia post saying that the new cards were supported in a recent update to iray, as I recall, and the DS change log shows it has a new version in one of the recent private/internal builds http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_12_2_31 Obviously we don't yet have that version, and we don't yet know if there are any issues with the Ampere support, but on the face of it it looks like there should not be too long a wait.
I feel you. I spent a lot of time trying to see why it wasn't saving the morph animations and ended up giving up. it wasn't anything wrong from what I was doing, it was the recent daz version that has a bug of not saving custom morph animations. Which for now makes it impossible for me to use it for character animation. I have to downgrade to older version which is fine in that regard. oh well.. we will just wait. : )
Any recent builds with fix for morph not saving available yet? (I'm not checking every new build)
and that's not what I was saying. After such a long time with several updates in between I would've expected to see a fix at least in the private build. There's some nice new stuff in the current version, nice new features and improvements, but a lot of ppl can't use any of it because we're stuck on .86 because of the animation problems.
I can imagine that you must be sick of reading such comments over and over again, and I understand that you probably can't do anything about it, but reading the changelog you can see how much other stuff has been improved, changed, implemented, etc, pp, and yet the biggest problem still persists, so you might understand that we're sick of it as well after months with no solution.
and you might also understand that for us it feels like it has absolutely no priority for Daz/Daz devs after such a long time.
If you check the change log http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_12_2_40 there is a fix for the saving issue listed