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
You can save it as a custom layout (Window - Workspace - Save Layout As). However, there is a bug in the current release, which has been fixed in the new Public Beta 4.20.0.3 release.
Hi all,
I have massive issues with DAZ since the update. Rendering is extremely slow, I had to go down to FullHD and still there's almost no process. What could have happened here?
I'm a fairly new user, so far it's been great but now since 4.20 rendering has become almost impossible, even with much lower settings than I had before - it used to be fast on QHD, now FullHD takes forever.
Appreciate all help.
Cheers,
M.
Nevermind, info was totally messed up, after further testing.
At a guess, your renders used your GPU before and now use the CPU. Try updating your GPU drivers.
As you can see I made changes yesterday, so the date says 02/24/2022 but problem is still there
Means that DS is reading files that are installed to another location. (...Data\Cloud\1_xxxxx\)
Since the Nvidia discussion has been closed for the 4.20 release, thought I would ask here what the driver requirement was for 4.20? Not going to download it yet, just wondered what the requirement was. I have an older GeForece GTX 1080.
Thanks.
Looking at the Daz Change Log, it looks like the Minimum driver is 471.41 on Windows for GPU rendering.
I'm running 471.68 on Windows 7 pro and Studio 4.20 works with both my 980 TI and 1080 TI.
Thanks for the info.
Edit to add: I have 465.89. Will update when I'm sure it's safe.
Thanks!
Lots of problems, I see.
I really have one question: Does Pin actually mean Pin yet?
This must be the worst update Daz ever has done. Today decided to do a fresh installation. As I read before here, you save your workspace, when Daz loads ignores it.
That has been fixed in the Public Beta release.
I'm affraid I also got that issue somebody mentioned here, the menus changed , controls disappeared, had to move back to 4.16 and everything is fine there.
Sorry for my late answer to your question, I have some custom characters that use FWSA components, and when loading the path is also missed
So I downloaded the update for the general release today that was supposedly going to fix the layout not being saved upon closing issue or the fact that Daz no longer sees saved layouts at all. It didn't fix it. It works GREAT in the beta version though. I think they forgot to put the update into the general release version.
I'm not seeing an update for neither the general release nor the beta.
I checked DIM and my account page.
The beta is version 4.20.0.3
General Release is version 4.20.0.2
Are you seeing an update to version 4.20.0.3 for the general release?
Right, the General reelase has not been updated. The Public Build has, but there is a new build pending which fixes some remaining issues so I would wait for that now.
Then the DIM is messing up because it had both an update for Daz Studio General release and Beta release.
Hi guys , maybe some one can help me, i have these scenes that take 12~16 minutes to render before i update, now i have notice that they are render in 50~60 minutes.
I just found this on my log
2022-03-07 11:06:41.591 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3060): Optimizing for cooperative usage (performance could be sacrificed)
Never see this message before, and also my Gpu usage keep dropping during the render, before as always 100% usage, someone can help me?
Studio 4.20.0.2
Gpu Driver 511.65 Studio
If i post on wrong place , just let me know.
Already fixed, sorry to bother.
I update daz studio to get last update version of iray .
Otherwise, I don't need to update the app and i don't need the features.
Here's an update on @jag11's light leak problem, i.e. this problem:
https://www.daz3d.com/forums/discussion/comment/7362561/#Comment_7362561
I did a complete repro from scratch to eliminate any possible gremlins in the original .duf:
With those settings I get convergence to 85.49% in a matter of a few frames then convergence stops increasing. After about 20 minutes (this is a TitanXP) I see this:
Changing the base color of the outer sphere from white to black results in a black render after 35 iterations.
We know from @jag11's previous test that it isn't an issue of the edges of the outer cube ending up non-aligned because of iteration differences (a classic computer science problem). So, having eliminated that and verified that the base color of the outer cube is having an effect, it certainly seems likely that the outer cube has a very, very small translucency, of the order of maybe 1 part in 1 million. I don't know if this is new in 4.20; maybe it always was that way.
This has to be translucency, not transmission (refraction weight), because the light intensity and behavior is affected by the base color; for example a base color of blue produces a black inner cube with a blue background.
My current hypothesis is that this is caused by internal calculations of the translucency value somehow causing the value used to be not-quite-zero. I can manually set the translucency to 4E-8 and I get a well lit scene, if I set it to 3E-8 I get the same as above. Those values are close to the precision of a IEEE 4 byte floating point value, but that would only matter if they were used in arithmetic with a value close to 1.0, supporting my hypothesis.
In a scene with a low light level the light penetration does certain affect the rendering and produce fireflies, here's the scene with translucency 4E-8, it's 32.91% converged after 2977 iterations:
The effect on real scenes illuminated to EV13 is minimal; as an experiment I added a point light parented to the camera and at Z offset -10 (to it's in full view) then turned "render emitter" off. With the default settings (1500lm) I get pretty much instant black with tonemapping at EV13. After multiplying the pointlight luminous flux by 8192 (to take account of the EV I get complete convergence in 736 iterations (default environment map, rendering quality still 0.1):
Unfortunately EV values of 0 or, indeed, lower, are common indoors when there is no external illumination (e.g. night). Typical domestic incandescent lighting produces EV levels around 0. Switching off the dome; setting the environment map to "None" does not fix the problem, neither does setting the dome to a "night time" HDR! Changing to "Scene only" does work. Sun-sky only does not (with the default settings), although as might be expected it does if I change the time to 6AM.
My conclusion is that this is a serious bug for low light level renders; it is counter intuitive that rendering at the physically correct luminance level would result in significant spurious extra rendering time to produce convergence and arithmetic errors of this sort really should be eliminated.
@jbowler Good analysis of the problem.
I would just add that I have noticed when working with emissive surface luminance value that the floating point value entered in the property is truncated to 32-bit float precision after you press <Enter>.
For example, if you enter 100000000000 as luminance, it will be truncated by Daz Studio to 99999997952.0 which is the limit of 32-bit float.
I am not sure if this is the limitation of the GUI widgets used for numeric value entry, but if true that means any value you enter will be slightly misrepresentted to Iray backend and could lead to incorrect results or at least results different from those we expect.
Even the simplest, commonly used value such as 0.1 is impossible to represent exactly in a 32-bit float, which means that any value other than 1.0 and 0.0 you enter anywhere in Daz Studio could introduce slight calculation errors further down the pipeline. That is, of course, assuming that Iray expects double precision values, and that those 32-bit, truncated, values get promoted to double when passed to Iray.
Out of curiosity, did you perhaps try to change the shader for the outer cube surface? Does switching to Weighted or PBR Specular / Glossiness from PBR Metalicity / Roughness change the outcome?
Does anyone know whether the latest version(s) of DAZ Studio improve the wait time for closing the program? I know that the problem is due to the number of morphs that need to be loaded (or unloaded) but I seem to remember reading somewhere that this has been addressed. I can't find the thread in which it was discussed though.
Some people haev reported seeing a change. The log is certainly more detailed about what is being done during shutdown now.
Has anyone else noticed slowdown issues with the viewport? It seemed at first like the update had actually sped things up, but now scenes that had no issues before are lagging a ton even if I'm not using the Iray preview.
I suspect this may be an issue with my hardware, unfortunately, but figured I'd ask.
Hello DAZ3D, I haven't been active for quite a while now and have a question regarding Studio. With all the changes I've seen so far, is it safe to say that Studio does all and more than Carrara does these days. I.E. rigging, morphing, shading, modelling etc..Thanks in advance.
No, Carrara is much more fully featured than DS. DS has no modeling capabilities whatsoever, no solid body physics (and dForce can be used to approximate soft body physics, but that's not what it's for), no native particle system, still a pretty buggy and rudimentary animation system, etc. I've never used Carrara, so I can't speak to how easy or difficult it is to use, but for me, the ease of use is the biggest benefit of DS, and the fact that it's still being developed does arguably give it a leg up over Carrara.
DAZ provides hexagon for free as a modeler with a bridge to studio, so both of them together can probably replace carrara. Most of us use blender though instead of hexagon. Or to export daz assets to blender with diffeomorphic then render and animate in blender.