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
Ok, here's my take on the latest update -- Xeon w5-2455X at 4.6GHz, 64 GB DDR5, ASUS ROG ASTRAL LC 5090 RTX 32GB GDDR7 VRAM with 576.80 Studio driver.
Daz Studio 2025 viewport in texture shaded mode with one G8 figure -- rotation and panning are now smooth. I can even get smooth rotation and panning (albeit slower) in Iray mode. Out of bounds objects clipped by viewport border don't tear and visibly lag behind their corresponding parts inside it.
However, even in texture shaded mode with just a single G8 figure with only dForce hair and geograft + 2 geoshells dragging the figure around the scene is choppy. In Iray mode, that choppiness is dialed up to 11 and it basically unusable.
Let me add that in Iray mode, when you grab the figure by the abdomen and drag it around the empty scene, the selection highlight for that body part lags behind the mouse pointer but moves faster than the figure itself—thus appearing offset toward the drag direction (i.e. drawn off to the side of the figure) while the figure itself follows at miserable 1 FPS.
A basic render queue script should be writable, though this isn't the thread to discuss it.
Indeed, I've already started writing one for 2025. Do we we have any idea why this happens (iterations updating logarithmically only, 10, 20, 40, 80, 160, 320, 640 and nothing inbetween)?
I've noticed it also doesn't seem to update the render target if you cancel in between the "fat jumps" which take several minutes, for example between 300 iterations and 600.
For once, I'd blame this on Nvidia rather than Daz, but seems curious.
DAZ Studio 2025 latest Alpha version crashes during render (Iray) withe the latest Nvidia Driver 576.80 Studio.
I have a RTX4090 in my system. -It doesn't seem to make any difference if there is a figure or if there is nothing at all in the picture.
The Viewport draw style Iray works normal, spot renderer seems to work.
Selection of other render engine also get me to a fatal error.
Last Version of the 2025 Alpha has worked and rendered perfectly.
Is it just me? Any hints from the experts here?
Roll back to the previous driver and see if it is still an issue.
Thanks for the advice. I will try tomorrow. By the way. Any choosen Render engine will crash my system.
Only the viewport window remains visible. The main Program window crashes and is gone. (I use a dual monitor setting)
So I've gone back to Nvidia 576.52 -the version that has worked with the previous version of DAZ 2025 Alpha on my computer.
Unfortunately as soon as I press the render buton the DAZ still chrashes.
I guess I have to gamble a bit. Maybe I will find out what causes this trouble :-)
What makes me wonder is that the IRAY preview and the spot render (with the Iray Render settings are working).
Anaways thanks for the hint!
Even when I say in the render settings, that only CPU can be used für rendering, the system crashed.
I have deleted and reinstalled DAZ2025 Alpha via DIM. Same, Software crashes.
Does it crash for a specific scene, or for any render?
I've found that on macOS, DS 6.25.2025.17807 crashes when you eiher save a render that is rendered to new window, or you try to render to disk, always, consistent, on both Apple Silicon and old x86_64 HW, so there is something weird in that build that wasn't in thre previous. I don't know how it behaves on Windows, but on macOS it's always CPU rendering, which might be a hint for Windows too.
Maybe "everyone seem upset" BECAUSE it's just an alpha, after all? The only version which works with 50-series, and it's just an alpha..
Thanks again for the help and suggestions I have received!!!
The alternative would have been to wait half a year for the BETA and then being able use of the 50xx series.
Also it makes sense to use the general release and the ALPHA side by side.
The 2025 interface is laggy and some plug ins might not work, but I havn't encounter any issues on the final rendering yet.
So setting the scene in the general release, save it and render it in the ALPHA.
Any chance of fixing the scene subset not remembering poses for characters? It completely overwrites the poses in the scene and uses some other scene subset file's pose and mixes them up weirdly. I recognize some of the poses from the other scenes I've saved with said characters.
Also, this happens with scene files as well, even when you try to merge them with a scene. This has persisted since 4.24
A Scene Subset should simply load the items saved to it, so unless there are pose controls which have been modified since it was saved I am not sure how something along those lines could happen. Can you give simple steps to demonstrate the issue?
For what it's worth, same version of DAZ Studio, MacBook Pro M4Pro, Sequioa 15.3 and I just did a Filament test render of an animation saving it in .mov format. No crash, and I'm still able to open the .mov file in iMovie perfectly, complete with Audio track in place. Still loving the Alpha.
I've been saving test images for the last couple of days without any crashing.
UPDATE: I just rendered the same scene out in iRay, same result (albeit much slower
):
.mov file saved, then opened in iMovie complete with audio track in place, no crashes.
I had Daz Studio 2025 Alpha Build recognizing my 5090RTX and did a few renders with it. I needed to fresh install windows, on my new PC and when I reloaded everything, DS 2025 will no longer render with my 5090. The viewport works in Iray, but unfortunately when I render it takes 25 seconds and produces a black .png.
Did something change and DS 2025 Alpha build is no longer compatible?
Interesting - I have crashes when rendering, even just add a primitive and bam.
[Public Build Alpha] Tools not working in view port
My Universal and Rotate tool don't seem to be working in the Public build however If I load up the current version of Daz, the tools work as intended, i'm not familar with any settings and i might have changed something as i've attempted to type something into the search but it hasn't typed in but moved my viewer and perhaps selected a keyboard setting mode I would rather have off, I'm sorry If I'm not articualting my problem across well because I don't know how it's happened, suddenly it was fine for one second then not the next.
Reposting from a thread I started;
I had tried again this morning, when i go to click on the physical tool in the view port, i can't highlight anything say if i were to move the axis or rotate, the sphere wouldn't come up and when I go to click on a direction, it isn't highlighted and if i attempt to move i'll move just the selected joint or even the joint behind, nothing is locked in the scene aside the background.
You probably didn't install the latest NVIDIA Studio drivers. Windows installs whatever Microsoft thinks works fine, but that might not be enough for Iray.
I think that remains to be seen. I bought mine when I was able to get it at a fair price, but I still feel cheated by NVIDIA. Increase in performance from 4090 to 5090 is minimal in most workloads, and it turns out that locking the card power down from 600W it can chug to 400W sacrifices between 5-15% of performance getting it pretty much back to 4090 performance levels except that 4090 did not even need to peg 400W constantly to get that performance level. Yes, it's nice to have 32 GB of VRAM and 2x faster AI inference if you are into that, but to me this doesn't feel like a full upgrade -- more like a point release. Should've been called 4190.
What is the node selection mode in Tool Settings? If you have both an on-CPU GPU (probably Intel) and a stand-alone GPU which is handling the UI drawing?
Also worth checking the Render Settings, especially in the Advanced tab for hardware, as a new OS installation will mean you don't have the previous settings (though the defaults should work if you have left them untouched).
I litterially can't move the physical Rotation tool in the viewport, it doesn't highlight and there's no sphere, same if i try to move it via the axis with the translate tool, universal tool too, nothing is moving anything. i have no clue why
are you using one of the locked viewport modes?
Left, Right, Front, Back, Top, and Bottom are all locked to their respective position.
"Perspective View" or a camera are the only ones you can move around.
If the plugin is retired is there a posibiility of getting the original code published? and is there any timeline for the 2025 Alpha SDK release so someone can work on a new plugin?
Since I have upgraded my workstation without checking if Daz supports 50xx series I have to use this version and this is my input with a i9 14900K, 2x5090, 128GB.
As soon as I have two characters in the scene and a decent environment the viewport is no longer usable. Moving in it is very laggy. The same scene in Daz 4.24 is working without any problems.
Then for someone who got used to move in the scene with WASD, the fact that I can no longer keep pressing any key to move it's annoying. I have to press it many times to move slightly, but sometimes it moves too much.
Then the shading it's a bit confusing. Everything is too smooth, too well lit, which makes it hard to use. Then also if I have glass in the scene is completely transparent in the viewport. For example I have a glass table in one scene. Placing a mug on the table had to be done in iray, because I was not seeing the table.
The rendering works well. I pose on Daz 4.24 and then render on Daz 2025. I haven't noticed a problem with the renders and rendering animations works aswell.
A lot of scripts are not working which makes sense. I tried to do batch rendering but none of the scripts worked, so I tried to make my own script, but the code changed so much I can't even open a scene with the script anymore, let alone make it open multiple scenes and render them one by one.
My biggest problem is with the viewport. I know that it's been reworked from scratch and this is still an Alpha version, but in this state it's not usable.
I just done a test render using my RTX5060TI 16G, and it worked nicely.
When i use the texture display on the Viewport the characters are unlit, all dark. So I am using Filament for the time being which works. The IRAY mode works as well, through it can be a little strange when you change a Canera's "Dimensions" while using that camera, you will see it stretch for a moment, then correct itself.
I'll do more tests with more complex scenes and have crash reports on.
@Richard
I am hitting an error with almost all material copy scripts from one popular vendor (3rd party store) -- they all worked in 4.x just fine.
Error in log is:
Is this something that has changed in Daz Studio 2025 and will no longer work so they have to update the script, or is it a bug in Daz Studio?
Please advise.