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
First impression is that the interface is much more responsive on my 2018 Mini (Intel, 64GB), and that makes a pretty big difference in the overall feel of the UX. New black/green, as a default, is easier to read and the contrast is markedly higher, too, and I can see myself adjusting a few things in it — but just the uptick in speed is a nice change.
I agree. I think it's a much better interface and I'm very much enjoying using Filament in 4.24, which is so fast!
Will the 4.23 PA addons work in 4.24 or they need to be updated ?
What do you mean by "addons"? Scripts, plugins. etc?
The SDK and script engine are essentially unchanged, but if a script (or a plug-in with metaobjects) uses undocumented features then all bets are off. or were you wanting to ask about Daz Studio 2025? If so see the "Evergreen" thread.
I think this question is about 4.23 vs 4.24, not 2025...
Is anybody else having issues with the view window acting like the render window? Is this a new feature? If it is is there any way to turn it off and go back to how the view window used to work? It was much better previously.
Yes I mean scripts and plugins. From the reply by Richard I understand scripts and plugins for 4.23 should work fine in 4.24. Thank you.
Yes, I realised as soon as I hit Submit - you replied while I was editing.
So, May 2025 and still no update with Font Size adjustment for the user interface like in Blender?
It has been stated many times over the years that it was not possible in the 4.x line due to the version of Qt used.
Update seems OK but everytrime I try to undo something the application goes "unresponding" for about 5 minutes, didn't get this before the update
Something else is wrong, when I try to select a character and pressing Ctrl to select the Head of another character (so I can use the Look at that custom action) daz studio selects the entire figure, is that a bug or a new "feature"? never had that trouble before, is there a way to deactivate that behaviour? I figured a workaround: while holding down the Ctrl key select the first figure then double clicking on the head of the second figure (it will select the 2 whole Bodys and the Head) Then click on the Scene tab the second character to deselect it. It's really annoying for posing since the scene tab is usually hidden while posing a figure
What is the Node Selection Mode in the Tool Settings pane? I suspect it is Root Node First.
I found in 4.24 that my Content Directory had been set back to a default state two days ago, and this morning all my scripts that I had added to the upper Scripts file line for easy access and two that had loaded characters and Bone Minions also gone, and my tabs were missing and others I never use were on the sides. They were there yesterday but gone overnight. This was brought up in the DS 2025 thread also. But as I added the scripts back, the last one crashed Daz Studio. After rebooting, I opened D|S and started again. Three hours lost. But once I started work, if I paused for even a few minutes or moved my mouse off of D|S, I found a swirly taking a time.
This is one issue I would like to ask why this happens, why is the default to put the Tips the opening window and 'Filter By Context' ticked? If I close D|S with the tab on Info and the filter by context unticked, shouldn't the program reopen that way?
Sorry about being grumpy. Some of these things have been ticking me off, others have just appeared since updating from 4.23....
Mary
4.24 has corrupted all animation files for me, can animate things just fine, but when I go to render it's like the file corrupts mid-render.
Both Image Seqences and Movies will pop an error saying the file cannot be saved, and ask me if I want to cancel or pick a new file location. Moving the location does nothing, and if I cancel it and try to open the file again, the file can't be opened and Daz tells me there's an error in the file.
Here's what I was able to find in the log about the errors:
About the Corrupted File:
About the Failure to Save:
Other Random Errors:
I have 124 Gb free on the drive where I save things, so I don't think it's my drive. Has anyone else been having these issues? I wasn't having any problems before the update, and single images are still rendering 100% fine and those files are not corrupting. I can save and reload them as normal.
Any help is appreciated! Full log is attached. Don't judge my file names too hard.
Have you tried an image sequence?
Oh my GOSH whatever you guys did in the new update made Daz Studio run SOOOOOOOOOO much more snappier than before. Please for the love of god keep this snappier UI the way it is!!!! I love it.
Thanks! That helped a lot :)
[deleted to file a bug report]
UPDATE: Bringing the nVidia Studio Driver current seems to have ameliorated the problem.
--- former problem below... ---
Hiya! Here's my specs, to get them out of the way:
* Daz3D 4.24.0.3
* RTX 3080Ti (12G)
* Windows 10 64-bit pro
* Ryzen 3700X processor (8 core 16 thread, should probably update it one of these moments).
* nVidia studio driver 566.14
I have 12 (yes, twelve) G8F figures (10x G8.1, 2x G8) and a volleyball on screen, 3 spotlights, total of 7 cameras; environment is the gymnasium from
https://www.daz3d.com/fg-school
(all other rooms/props are hidden or deleted)
Attempts to render this scene deliver the following in an endless loop (I had no frames rendered and no progress indicated in the dialog after 40 minutes):
2025-05-09 15:30:07.468 Iray [INFO] - IRT:RENDER :: 1.0 IRT rend info : Scene graph manager init took 0.000s
2025-05-09 15:30:07.468 Iray [INFO] - IRT:RENDER :: 1.11 IRT rend info : Iray interactive running with 1 device:
2025-05-09 15:30:07.468 Iray [INFO] - IRT:RENDER :: 1.11 IRT rend info : CUDA Device 0 - "NVIDIA GeForce RTX 3080 Ti" (compute capability 8.6, memory 0 MB/12287 MB)
2025-05-09 15:30:07.468 Iray [INFO] - IRT:RENDER :: 1.11 IRT rend info : Driver version: 566.14
2025-05-09 15:30:07.468 Iray [INFO] - IRT:RENDER :: 1.11 IRT rend info : OptiX Prime version: Native OptiX Prime or OptiX 8 RTX Adapter 5.0.1
2025-05-09 15:30:07.468 Iray [INFO] - IRT:RENDER :: 1.0 IRT rend info : -------------------------------------------------
2025-05-09 15:30:07.468 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(373): Iray [ERROR] - IRT:RENDER :: 1.0 IRT rend error: Dropping failing devices
It is so tightly wound in this loop that cancelling the render doesn't stop it, nor does force-closing the render diag window; the render window stays open. If I hit ESC, I get the "Cancel...?" dialog; if I hit [Yes], it keeps going, if I hit [No], it keeps going (of course)...
AND, of course, while the render window is open, I can't get my viewport window back, although I have enough focus that I can navigate through the other panes and to the main main toolbar (File, Edit, etc.) and select items. I'm not sure if Save works; Exit will quit the program but the render window stays open, and the log continues to grow. I have to force-terminate the render window thru the task manager.
I have managed to render another scene with 9 of the same 12 figures (3 of them out of focus) (OHS-001-1).
My MAIN question/subquestion is: I have 12 figures in a properly lit scene (OHS-PHOTO-OP, rendered here with the Viewport engine), and I would like to render the scene in iRay as I think it's pretty cool. Am I being too ambitious? Is it possible to do or would I have to acquire a second card and SLI the two?
My secondary questions are:
* why does the render not exit when cancelled?
* Is there anything I can do -- character baking or whatever it's called -- that would allow me to complete this render?
* would this situation be helped by more up-to-date drivers? I updated to 566.14 after reading the recommended drivers from about a month ago.
Any clues on how I can revert or is it enough for me to just replace the install folder from a backup?
I had this, too. I updated to the very latest Nvidia Studio driver this morning (576.02) and forced a reinstall of 4.24. Now all the buttons are fine.
why is it impossible to delete multiple objects from a scene?
each new version gets worse at this and I cannot do it at all in the latest build
longest I waited was 9 hours and ended up killing that in Task Manager
I haven't had an issue, but recently I have mostly been testing out prop sets so single nodes and simple figues with little ERC. But I have deleted some very large assembalges, as far as item-count goes, without issue.
it is a size thing, I can do about 50 at a time
this scene has thousands, grouping no help
I did eventualy do it in bits
It was! Thank you! Silly me
I'm running into the same problem too.
try saving the crash report, using the button on the right in the screenshot, and attaching it to a post. What are your system details? Does this happen if you launch a differently named instance with its own settings? Are you launching the application itself or double-clicking a scene file or using the launch command in DIM (or Daz Central)?
Hi. I've just upgraded to 4.24 and for some reason I now can't restore poses in the keyframes. To fix a position or pose I would 'memorise pose' and then restore and it would be set in that keyframe. 4.24 isn't doing that any more for me? Anyone else getting that or know how to fix it or is this a bug?