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
Very frustrating. The version was updated to 4.15 and the purchase date bug has not been fixed in DAZ Studio. I still cannot sort by recent purchase under Smart Content/DAZ Connect without my purchases showing obviously wrong purchase dates. The dates are correct within DAZ Install Manager as well.
This is a huge regression in usability within DAZ Studio...
It isn't, as far as I know, a DS bug - it's an issue with the data supplied by the store since the software change. It broke without requiring a new versions of DS.
Does the backend provide two different sets of data to DAZ Install Manager and Daz Connect then? Or even the store? It seems to me that Studio itself is either reading/querying an incorrect field or reading the timestamp improperly. Possibly both, as some items return the exact same date for release and purchase date. Conversely, DAZ Install Manager grabs the correct time and date. Same with the store.
How do I roll back to version 4.14? 4.15 is terrible
Bugs, errors, rendering by the processor instead of the map... Is rollback possible?
Even if the data is accessed in a different way or is outright different, the issue showed up following the store update with no DS update.
What is your GPU, and what driver version is it using?
Timeline can't move keyframes until they are recreated with the "create keys" button. Puppeeteer don't register aliases. Frame Selected button tosses the viewport miles away from the selected props. IK pins suddenly and wildly appears on figure's feet and hands on scene load. Sliders randomly jumps on extreme negative values when posing a char. Recalling a pose from puppeeteer inverts the rotation values on the root. Autofit doesn't work properly anymore on certain items when the char isn't at 100% size. Undo randomly don't "save" camera position/orientation. Perspective view suddenly and randomly jumps in unpredictable directions when trying to move it forward.
How can these issues be caused by the GPU drivers?
Just to be clear, I opened tickets about these issues in the past. They never got fixed.
I'm noticing some grouped props don't exhibit proper visibility in iray viewport when using the hide/show on the group in the scene tab. I'm not 100% sure what is broken, and it's not consistent. Some groups will hide/show in iray viewport, but others do not respond at all. Additionally, if the group was hidden prior to starting iray viewport, the group will unhide properly, but then not hide itself when the group is set to hidden once again.
Hiding individual props within the group works though.
Also, this was a saved scene from 4.14.
Frame Selected is a known issue, in my experience it affects only items thata re away from the origin (which can be a problem for Iray) and can be worked around by making sure that the camera/view is looking towards the origin. What certain items isn't AutoFit working on? Which figures is the IK pins affecting? Are you sure you were using a camera, not a view, when the undos failed to be stored? How many of the other issues have been confirmed by other users? In any event, I was asking a different poster about their GPU as they were mentioning crashes and render issues - I wasn't suggesting it was relevant to all issues.
After 18 months of happily using 4.11, I've now bought an RTX 3090, which unfortunately means I've had to upgrade to 4.15. One of my main reasons for holding off upgrading was that you can only have one instance (without the script kludge) of Daz running in 4.12. Is this still the case? It seems to be, but surely not after all this time?
Instances still need to have a unique name, which can be handled via the script or by manually creating a suitable shortcut or from the command line.
That's what I was afraid of. Guess I'm now torn between constant crashes/render queues not working, but insanely fast rendering, or returning the RTX and having slow rendering but keep my sanity. Thanks for the quick reply :)
You can use the script to set up a set of shortcuts for future use, you don't have to do it each time you want a new instance of DS.
2080S.
I checked with old scenes with which I worked earlier - the effect is one. Processor (CPU) rendering begins. Although, before, rendering was a video card (GPU).
The latest nvidia studio drivers are installed.
P.S. I apologize for the previous comment, the chair just burned out when Daz began to do "undesirable" difficulties for me ...
DazCentral does not allow you to choose where you install DAZ Studio. Not everyone wants to install to their C drive.
Yes, I can do this. But they aren't properly separate instances, are they. My normal method of working is set off a render queue in one instance of DS, forget about that instance, and then work on new images in one or more other instances as time allows throughout the day. The render queue doesn't work with more than one instance of 4.15 open.
It also seems to be the case of if one instance crashes, so do the others. Several times yesterday, I was rendering in one instance and working in another. The instance I was working in crashed and froze the rendering instance too. Very frustrating.
I still have the install files for 4.11 on my PC, thankfully. I'm very tempted to go back to that again.
Sorry, probably I have expressed myself the wrong way, but the "Update your GPU drivers" it's the new Panacea for every issue. I asked the helpdesk about the timeline and they answered me "Check your GPU drivers and be sure they are the latest"...
About the issues, I'm pretty sure other users have the same as me.
I'm a DAZ Studio user since 11 years now. I'm pretty sure of what worked fine before and what doesn't work now. I'm still on version 4.12.0.86 like all other animators.
Sorry if I sounded a bit harsh, but it's three years I have to fight against the Frame Selected and two years the timeline's bugs, not mentioning the Pupeeteer broken since always. I'm a bit tired.
And, sorry, I forgot to tell you about the Autofit: It affects mainly hairs. If the figure's body isn't full at 100% size (especially the torso/abdomen) they gets deformed, resized or moved away from the right position. I have some saved chars that loads correctly i 4.12.0.86 but if I load them in 4.15, their hair aren't in the right place or have been resized to sinking in the head.
Can't install. Tried multiple times. Sometime it reach 70%. Sometimes even 92%. But the progress just ends and goes back to install button.
This is under Windows 10 Home Edition.
After uninstalling and deleting the DAZ3D folder and starting all over, I manage to sucessfully install Daz Studio 4.15 by avoiding installing all those Blender, Maya,etc.. extensions.
Stand-alone isntaller, Install manager, or Daz Central? From your next post I guess the last of those.
3090 works amazingly in 4.15. It's insanely fast! I believe you need the latest drivers from the Nvidia site though.
Can I ask how you reverted back to 4.14 please? I want to do the same, this 4.15 is a bloody mess and I'm hating it already.
This 4.15 is a total disaster as far as I'm concerned. Every scene I have saved for use, everything I'm loading in and especially hair is now a complete mess. All my renders are coming out almost obliterated with fireflys. Never once have I had a problem with fireflys before but now everything I'm trying to do is covered with them. Hair is coming out an absolute mess. And on top of this my render times have jumped up by a huge margine to, an average test render, say one figure with clothes and hair used to take around 3 to 4 minutes, it's now anywhere from 7 to 10.
I have no doubt the answer to this question is going to be 'no', but is there anyway I can get back to 4.14 please?
I'm glad it's not just me with the hair fireflies. It's driving me mad. How does this even get through quality control!?!? Anyway, for a workaround you can set SSS amount to 0 which may help with the fireflies.
Thanks I'll give that a try.
Is the GPU actually being used? Have you checked that your driver matches the current minimum?
Yes Richard, it is most definitely being used and it also has the latest drivers because I only updated them earlier this week.
Update :- I have now tried some renders with the SSS turned down to 0, very strange! My render times are roughly back to what they were, around two minutes with the single figure/hair/clothes, fireflies now are not as bad as they were but are still clearly visable and hair is still looking a big mess compared to how it used to turn out. I've tried several different hair products and all are the same so it's not the hair causing this issue and in fact it isn't only hair that I'm having this problem with, there are plenty of things within my scene that are also now not rendering to the same standard that they were before this 4.15 mess appeared on the scene. Why the hell is it that everytime they 'update' DAZ one thing or another goes stupid? Do they ever test things before throwing it at us?
Of course it is tested - and yours is not the universal experience. it may be driver related, especially if you are using the latest-latest driver rather than the latest Studio driver (game drivers sometimes add new bugs as they are tweaked to cope with the latest games; the Studio drivers should be versions that have been found to be stable and trouble free). Do you have soem examples of content that causes these issues (on a sinple load and render)?
Well it seem extremley starnge to me how everything was working perfectly fine until now. Examples probably will be numours if I start listing them because it's even having the same effect on default stuff that comes with Daz Studio.