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
Load time depends on how many G8F characters and morph packages you have installed, because it loads all the morphs from these.
I installed it using DIM.
First render stopped with error, probably because a Windows update (W10 64 home) downloaded in the background.
Installed the Windows update. Reboot.
Reinstalled Nvidia drivers (I do that after each Windows upgrade). Reboot.
Now my monitor goes black randomly when using Daz. Feature?
What is the driver version?
For Nvidia? Studio 456.71 released 10/20/2020.
I assume it randomly goes black during rendering? Iray or Filament?
I would hope you're doing that anyway. I lost my content drive twice in one year and, trust me, it's a total pain to have to rebuild it.
In general, how stable is it if you're not doing animation? Right now, I'm mostly interested in trying out Filament.
I use DS for approx 16 hours a day, it is stable. Which version of DS do you have installed now?
It randomly goes black on off before rendering.
Sounds like the scene may be too big for the GPUs memory. What are your render settings (Render Settings pane - Advanced tab)?
FYI: I have two computers using Daz Studio, an AMD based threadripper with 2180 TiX2 and 1080TiX1 which is my main rendering server, and an intel base with 1080 TiX2. Both were running the nividia driver 456.55. First off, the install itself was a bit of a chore. DIM didn't want to do it until 4.12 was uninstalled. After installation, the AMD based system did not use the video cards and just gave me a black screen. Didn't even fall back to CPU. The intel based system did in fact render. On the AMD system, I uninstalled the video driver with DDU, and did a clean install of the latest Nvidia driver, 457.30. Then it worked.
The iray section plane problem still exist for me too
DAZ, WHY WOULD YOU RELEASE THIS IF YOU KNEW THIS PROBLEM STILL EXISTS. [GOOD GRACIOUS]
Because it doesn't affect every user, and Daz can't reproduce it?
SDK version chnages are noted in the change log. The minimum version has not changed, so plug ins will still work.
How are you using the character preset - custom morphs are expected to load if you use the preset to load a new figure, not if it is applied to an existing figure in the scene.
Holy Moly you guys!!!
Well I've been incredibly hyped about everything that's been going into Daz Studio over the past years - ever since 4.0, but I never really used it as my animation/render studio - just all of the amazing, incredibly handy and powerful tools it has.
This whole Filament thing along with (I haven't found/figured them out yet) the new Animation tools has really got me jazzed.
When another Carrara user turned me on to the Beta with Filament, I gave it a bit of a try - not much time invested into it - but it was cool enough to get me to start putting a bunch of Daz Studio info on my site so that my readers and myself can learn and grow with this thing.
Well one of my awesome readers sponsored me a gift card, which I used to get a cool Genesis 8 Female character and hair for her just last night so I could install and try the new Daz Studio as soon as my Carrara renders were complete.
Oh Man!!!
Okay, I have a lot of Steph videos to watch so I can wrap my head around where things are. I used Filament just fine for getting an animation put together, but not well enough to run it for the render, so I switched to Iray. OMG!!!
Well my animation is rendering at roughly a minute per frame, give or take, and the results look fantastic!
Filament is amazing! Even if I stick with Iray for my final renders, Filament looks gorgeous at its absurdly fast render speed!
I know I saw Steph working in a Graph Editor and some other new animation tools. I have to look into that stuff and see how far this adventure takes me!
Now I need to get my hands on Linday's Classic Long Curly Hair with dForce and I bet I could make a Daz Studio Genesis 8 Female version of my Rosie character (My hero, fashioned after my lovely wife)! Lara makes a stunningly similar Rosie 8 - on the right is Rosie 5, a cross-generation Genesis 1 Female (click the image to see the intro video of her)
Wow. Just... Wow!
Great Job! Thanks Team Daz 3D!!!
I even have a meager system for this stuff -
So I'm running Iray using both GPU and CPU and it's running great!
I had one crash, but it truly felt like it was my fault, switching from Iray in my viewport to Filament right in the middle of a bunch of setting changes - Iray was busy busy busy.
Installation via DIM went without a hitch, but I just installed the latest nVidia driver to run the Beta. I wonder if that made the difference.
What happen to daz 4.13? is number 13 a superstitious thing for daz tech? lol Just kidding . Thank you for the bug fixes and update. look forward to messing with it
Hi all - this newest version is working very well for me with a couple of strange exceptions - if I close down studio for whatever reason...I'm unable to re-open the program unless I restart my computer. While performing the restarts, I'm randomly (not always) notified that a program is interfering with the restart and needs to be closed (I'm assuming this is Daz as this has not happened before the newest version install). Also, when closing down Daz - it prompts me to save even if a scene is not currently loaded - have not experienced this before the newest version. I'm sure these things will iron themselves out - just curious if anyone has experienced same. Thanks!
I have the exact same issue. A temporary workaround is to open up Task Manager and look under Processes for DAZ Studio Application and kill that process manually.
You could also wait a few mins or 3 and see if it will close gracefully before terminating the process.
failure to shut down fully is a known issue for some users. What isn't known is why it happens to them. DS will take a while to close after working on a busy scene, but that should be a matter of minutes, perhaps tens of minutes, on most systems.
This happened on a previous update too, but it didn't take too long to fix. It would be great if the known issues section in the first post could be updated, unless there is a different page for that?
This sort of thing also happens with most other applications that need a computer's full attention, especially if thhere are other things running at the same time. Windows (10) Update will totally bork a computer's behavior if it's doing its thing in the supposed background.
When I have rendering to to, or even when I'm working on a large scene, I disconnect from the internet, shut everything else down, run C-Cleaner, then launch my software to work. I look through hidden apps and shut them down as well, like Dropbox, for example.
Yes, they are saved with the scene. They always were saved with the scene. Those settings are scene+camera+frame specific however. If you load an existing (pre 4.14) scene on which any of the relevant options have been set it appears with Tonemapper and Environment options nodes. My understanding is that these are just the scene-global data copied to scene nodes. If you set "viewport" rendering in the Rendering tab the tonemapper and environment options disappear; mostly they weren't used with the viewport and *most* of them aren't used with Filament rendering, but now if you click on the relevant new nodes it is possible to set the settings.
Unfortunately this is half implemented; I can only have one "Environment", which is probably reasonable, but I can't animate the Sun-Sky settings (e.g. to do a time-lapse sunset). In fact the only properties that can be animated are translate/rotate/scale and these properties are actually hidden... Likewise I can't have per-camera tone mapping settings, I can move the Tonemapper Options node to a camera but I cannot create a second one. Much more important I can't animate the all important EV in tone mapping - this is the only part of TM that filament rendering uses (it uses a fixed gamma encoding and no true tonemapping). This means I still can't adjust the exposure as I pan a camera; a long standing issue with Daz which makes it all but impossible to do real-world tracking-camera type animations.
To make the point with a real example; I just stood in the middle of my living room with my camera and panned the camera through 360 degrees. The exposure (fixed aperture/shutter) went from ISO4000 to ISO200 and that is with a 36mm(35mm equiv) focal length. So that is an EV 4.3 exposure range from a single position and using what I consider to be a wide angle lens. For another example think of entering a building from the outside; there are about 5s of the room being dark before we adapt. It does seem that filament rendering is doing some kind of global adjustment to HDRI exposure; I generated a 360 degree rotate movie of a similar scene to my living room (actually an HDRI of my office) and the HDRI settings required in the environment were completely different to the Iray ones - the map intensity went from 0.01 with Iray to approximately the default (1.0) with filament. However the adaption is global - at EV13 the windows are over-exposed and the room under-exposed.
It's all very promising, but some work is required; these bugs (no per-camera exposure, no exposure animation) have been in Daz since I started using it and are very obvious; I can animate the camera aperture but it only affects the depth of field, not the exposure!
Yep, that's really annoying too, it applies to everything I think - "name" and "label" are synonyms in the language I speak but Daz seems to ascribe extra meaning to them.
Daz 4.14 launchs fine how after closing DAZ subsequent attempts to launch fail unless I reboot Windows.
I7-4770S - 32 gigs of DDR3 memory, GTX 1060 with 6 gbs of video memory - Windows 10 Home Premium 64 bit
Anyone else having this issue?
I appreciate everyone's feedback. Until newest version nothing like this had happened at all. I'm sure nothing to worry about - just curious if it had happened to anyone else. Again - thanks for all feedback.
See earlier posts. No need to reboot, either wait a min or 3 for DS to close, or terminate the DAZ process in Task Manager.
Thanks very much Doctor Jellybean, worked like a charm. Hopefully there will be a patch or update for this.