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
Attach your crash reports to a technical support request. Avoid language in the forum that could get your post deleted.
Studio driivers should be more robust in genreal, the game ready drivers get updated more often because new games need support but as a result they are generally less well tested and more prone to stability issues - but the key phrase is "in general".
Your crash appears to be in Filament
Many, many pages back I received advice to post a technical support request about a bug in the 2025 alpha build and this turned out to be incorrect. The tech support people were polite when communicating with me but they didn't know what to do with it. The next day they told me to post it here instead and closed the request. I posted the bug report here but no one acknowledged it. I don't know if the bug report ever made it to the development team, maybe yes maybe no. After this experience I decided not to bother reporting anything about the 2025 alpha. I think it's a little strange that DAZ publishes an alpha build for people to use but are disorganized about receiving feedback. Maybe the purpose of publishing the 2025 alpha is just to have something that works with the current Nvidia video chips?
After reading comments on this forum about changes being made to scripting breaking many of the products I've purchased from DAZ I expect to use 4.24 to build scenes forever and the 2025 version only to render them. This is no more difficult than using 2 PCs with one to build scenes and the other to render them. I really hope they don't decide to change something that makes it impossible to share files between the two versions.
I agree, I mean, I see issues but I don't know if it has been reported somewhere (and the forum is just a nightmare to search something in).
Iray preview performs slightly worse than 4.24 when using same draw settings on my 4090. I wish we could get near the same performance in Iray preview (or something of quality between Filament and Iray preview) that performs more like iClone.
I imported an OBJ. After import, it was not selected in the Scene pane, but I didn't notice that. I selected UV View. It defaulted to View by Material. I changed to View by Node and the whole DS Alpha application window disappeared from my monitor. It is still highlighted in the Windows 10 Task Bar. The Task Manager says it is not responding. I killed it. I repeated the scenario with the same results.
> I would recommend that people do NOT use the STUDIO drivers! The Game Ready drivers are more up to date and have fixed issues which cause Windows to crash, where as, for some strange reason, the Studio drivers have not been updated.
I disagree, using latest studio drivers with RTX 5090 and I've had no crashes whatsoever. Version difference is also minimal 576.80 for Studio .vs. 576.88 for Game Ready. NVIDIA is about to release R580 branch anyway.
Can confirm that the same thing happened when i performed your test. The difference is that the crash occured after I chaned View by Node and then selected the obj in the scene pane.
I noticed that if i added a primitive to the scene prior to selecting anything in the scene tab, Studio didnt crash immideately, but did on closing out the scene.
UPDATE: It's ver unstable sometimes it crashes with the primitive sometimes it doesnt weird.
I can't replicate barbult's example, but it does crash once I selected the obj in the scene pane.
I encounted a very funny bug and re-produced it several time after the latest update.
Let me explain it.
First of all, universal tool is not working sometimes. The arrows and spheres will disapear completely after keyboard navigator.
Second, the movement marks will appear after I hit the focus botton for any node. But when I try to use the marks like rotate. The whole scene jump "changed" to the scene many steps of changes back. This is so cute.
3rd, another bug, universal change was not logged in the change log means they cannot be undone...
Edit: I think I propably know why. Theres a few keys interferences across different panels
@Richard
I managed to get Daz Studio latest alpha to hang -- empty scene, rendering mode doesn't seem to matter (I tried texture shaded and Iray preview).
To reproduce:
1. Maximize Daz Studio window on the primary monitor by clicking the Maximize button
2. Press Win+D (this minimizes all programs and shows desktop)
Switching back to it with Alt-Tab or a click on taskbar icon causes it to hang.
Note that:
1. Clicking Minimize button when maximized and then restoring doesn't cause a hang
2. Pressing Win+D if the window is not maximized.and then restoring doesn't cause a hang
I know this doesn't help you, but for the Mac version, I'm able to import an .obj, check the UV view and select and assign texture and emission maps without any issues.
I get this too, I wonder if it is an issue with how Qt receives or sends on the minimise command in this non-default case
Can you give a sequence of actions that will trigger these?
It didn't crash for me. The application window just disappeared. I didn't get any crash report and the process was still active in the Task Manager and "not responding".
Edit: I didn't have an opportunity to click on the node in the Scene pane, because the whole application window was already "gone".
We are told this has been fixed for the next build.
Thanks for the notification. That is always appreciated,
Just to add that Win+M (Minimize all windows) also hangs it on restore. One other thing to note -- if you click minimize button when program is maximized, and then restore it, the primary viewport won't be visible for a couple of seconds (for me the viewport client area shows as black during that time). Sometimes it even stays that way until you do something like say change zoom by mouse wheel. This might have something to do with recent change which disables viewports if they are not visible (minimized -> not visible). Perhaps not all paths in the code enable it (or it is getting disabled in a wrong way so that it doesn't process window messages anymore) and the app gets stuck waiting for window messages which never come so it can't repaint the client area.
I encountered a very serious bug. In the latest version of Daz Studio 2025.19807, the iray preview and rendering become very blurry, as if displaying 1080p content on a 4K monitor. The interface font also has a similar issue, but it cannot be consistently reproduced. I am using an RTX 5080 graphics card with driver version 576.88. I hope someone can tell me how to solve this problem, as I am almost unable to use Daz Studio for creative work now.
Have you checked you NVidia control pannel to determine how the global settings are vs Daz Studio settings?
If you are on an an AMD system there is a tool to optamize your PC configuration along with the GPU configuration/
Check with CPU-Z or GPU-z to see how it reports on your system settings.
I noticed that the Texture view is black all the time. I noticed in this release that is partially fixed, but you have to either be using your normal viewport view, no camera, or, when you are using a camera view, the camera cannot have the visibility switched off. If you switch it off, as I prefer to do so I don't see it in the viewport or see the lines, the scene will appear black. Click the visibility icon in the scene view so it is visible, and when viewing through a camera, it will be okay, though it looks a little light now, with less contrast than it used to be.
I was using the filament view, which I like, but it doesn't seem to take into account any spotlights or even camera lights, which is annoying. If that alone was fixed, I would use it all the time. But with some fiddling with the Filament settings, you can get it to look pretty nice for scene building and it is plenty fast enough.
Oh, and one last thing, the reason why I recommended the Game Ready Drivers over the Studio Drivers, at least until the Studio drivers are updated, is because with certain CPUs, in my case, a Ryzen CPU, you can get a black screen and Windows is unusable. If you don't have a Ryzen CPU, you may be fine. I installed them, and had to jump through some hoops, go into safe mode and use some software to uninstall the Studio Drivers then install the Game Ready Drivers in order to even get back into Windows normally again. I have been keeping an eye on the Studio Drivers to get updated, then I will install them as I agree, they are the better choice, once they are updated.
If you do have the same issue I had with Windows going black on you, I used the ChatGPT app on my phone and asked it what to do, and it gave great, step by step advice on solving the issue without problems. I knew what to do, it's just been many years since I last had to.
What I'd give for a little bit of viewport lag. I still haven't been able to move around it more than one key at a time. I know others were having that problem with the first alpha release but haven't seen any mention of it since then. My drivers and alpha version are all up to date.
I've gotten the same issue a couple of times this weekend, but haven't been able to identify any specific cause for it. It just randomly happens as I'm working on the scene normally. It seems to happen right after using the universal tool to move something. It moves, then the on screen controls go away. It's been 3 different scenes the tool disappeared on, only one full reset though. And absolutely nothing about any of it shows up in the log. *edit* Ok, just got the reset again. It appears to happen when the universal tool comes back from whereever it disappears to. As soon as I use the tool after it reappears, then the scene jumps back several steps. This time I did get an entry in the log:
2025-07-20 12:55:28.861 [WARNING] :: \src\sdksource\interface\viewtools\dztransformtool.cpp(202): Undo Stack hold already started in DzTransformTool::mousePress()!
I have submitted a ticket as well
Hiding the camera also hides its headlamp. In any event, see http://docs.daz3d.com/doku.php/public/software/dazstudio/6/change_log#6_25_2025_16207 - the active camera is not being drawn so it shouldn't get in the way.
The keyboard navigation issue was reported and is fixed in a future build http://docs.daz3d.com/doku.php/public/software/dazstudio/6/change_log#6_25_2025_19907
are you using display scaling?
Please ignore if this has already been reported. This is Windows 11 (fully up-to-date) NVidia drivers Studio 576.52 and Studio 576.80 and DS6 Alpha 6.25.2025.19807:
1) Launch DS6.
2) Make DS6 full screen (with or without the Windows autohide task bar).
3) Switch the interactive viewport to Iray mode.
4) Click on the Windows "minimise" button at the top left.
At those point Studio goes AWOL; it is possible to see a thumbnail of the window from the task bar but it does not "come back" if clicked. IRC it might have happened in the previous drop as well but I suspected the NVidia driver (in some ways I still do) because it had added a really annoying piece of screen clutter to the Windows display. It wasn't that; I worked out how to switch it off but the issue still repros.
The only way I have found of getting control back is to Task Manager Studio.
John Bowler
Same. I am but I don't think it's that. The issue went away after I installed the NVidia 576.80 driver **and rebooted**. I suspect the latter was the key; I only saw the problem once recently [today] with the 576.52 driver and I didn't try a reboot then, either of Windows or Studio. The pixelisation is way over my scaling (2x) and, while it doesn't go away in a single Studio instance, it certainly went away after a reboot.
All, yes **all** my cameras have the headlamp switched off. The "texture" view is still lacking in illumination. There is plenty (somewhat excessive) with "Universal" and a lot (a little too much) with Filament but it is, of course, perfect with Iray (since I carefully adjusted it to be so :-)
There are a plethora of view modes all of which seem to be slower than the original, crude and cartoonish, DS4 texture shading. Maybe just do a fast version of smooth shaded (texture shaded was always very much faster) and add a bit of computed colour from the way complicated texture maps? Interactive editing does not require or **benefit from** the darned lighting; I can fix that in Iray when I have everything in position! So just give be crude, undivided, surfaces that I can move round PDQ and call it "EDIT".
(c) John Bowler
Is the camera/view away from world-centre? I find things go wonky quite quickly (dark, and the camera rotate/orbit doesn't work as expected until another move, such as mouse-scroll zoom, kicks it). The issue has been reported but I have no idea what dependencies fixing it may have.