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
"Find missing files" button only works for the case in which the missing files are texture maps from the folder(s) in : runtime\textures...
I have no idea if UI scaling is planned, but I would not be surprised at its absence now in any event - UI elements have changed thanks to the Qt update, so just nailing them down at default is probably the first task in that respect.
Yes - report here first, a ticket later if it isn't resolved in thread would be my suggestion.
Changes to the Viewport are one of the features.
While plug-ins definitely need updating to work at al scripts are not necessarily immune, I would be wary about using script products in this version.
I know this is an Alpha, so I'm not surprised that the Papagayo lip synch script doesn't work nor will it most likely unless it's updated. What *did* surprise me is that I'm able to load my .wav file and hear it while I animate. Awesome. So, six of one, half a dozen of the other. Overall, the ability to hear the audio is more important, but I won't say "no" to an automatic lip sync tool.
Further, it *looks* like I'm able to output a .mov file, but the file seems too small and can't open or convert at all, so unless I'm missing something, I still need to output frames. Too bad, now that I can import audio and hear it while I animate, being able to output a single file with both audio and video again would be super sweet.
This could be a GPU issue, several people with Intel GPUs seem to be having issues, but for selection go to the Tool Settings pane and check the Node Selection Mode.
Ah... thanks. I just saw the thread : https://www.daz3d.com/forums/discussion/727631/daz-studio-2025-6-25-2025-x-evergreen#latest ;
These could be GPU related, I suspect. Certainly WASD navigation is working for me - but you are not the only one for whom it isn't.
I had a crash exiting Preferences - I noticed that there is some activity (spinner next to mouse cursor, UI refreshes) as it updates the content panes. I didn't get a crash if I waited until that was done. Still, if you get a crash report please upload it (here or to a ticket) to prove I was not imagining the issue (Daz couldn't reporduce it).
I'm perhaps unusual in having an M2 Max Macbook with a ton of RAM and also a Lenovo ThinkPad P1 with Nvidia RTX 4070, also with a ton of RAM. The Alpha crashed within seconds of being installed on the mac: trying to close a pane to reconfigure the default screen layout. Disappointing. By contrast, the Windows version appears more stable than the regular non-alpha. I've loaded a pile of scenes, with no issues, reconfigured the pane layout to my liking etc. It seems very robust, and a fair bit quicker. By contrast, the regular Windows version appears to be actually SLOWER than my macbook, despite supporting iRay. Which is a bit unexpected. And unlike my mac, it cannot render large scenes at all. Perhaps that's because the mac has 'universal' memory, up to 64Gb, whereas the RTX is limited to 8Gb.
So as a Mac (M3 iMac/Sequoia) user:
Some bugs / issues I've met so far :
1) Progress bar is alwasy shown with "Processing image: xxx" no matter I click New or load a Scene file. (ss1) The progress bar even doesn't update any progress when switching to Iray Preview
2) Layout cannot be correctly saved... with no preview as well (ss2) And DS 2025 always loaded a wrong layout after I re-launched it... even if I loaded the layout I ever saved for DS 4.23 PB...
3) Per Pixel Shading cannot be turned on... in Preferences > Interface. It's always Off...
4) Low performance (laggy) in Viewport when tweaking perspective / camera view.
5) After opening a scene file, some lag can be seen when Viewport is redrawn with Texture Shaded drawstyle... for two times, I could only see all objects are black. I had to switch the drawstyle back and forth in between Texture Shaded and Filament, then the Viewport was updated correctly with Texture Shaded.
6) I tried with some scripts... some script product didn't work any more, e.g. Content Wizard. I got the error messages in DS log, as attached.
Several Mac users posted that they got a crash the first time they opened DS2025, but it worked fine afterwards.
And yes, when rendering with the CPU you're less limited regarding the size of the scene you can render.
I was having some issues until I updated my graphics card driver. If you don't have the latest version installed you might try that and see if it fixes your issues. :)
I haven't tried saving, but the session layput seemed to save and restore OK.
What GPU is driving the UI? If you have an Intel GPU on the CPU is that being used? Some people are reporting lag, some people are finding it snappy - at least soem of the laggers have Intel GPUs handing the UI (even if they have an nVidia GPU).
Scripts may well requiree updating, deepnding on what they do and how they are written.
Well looking at this thread it seems that it's not going to come back
I just tried this with my 5090 and it was smooth going. I haven't played much yet though. Bad timing today, super busy with other stuff.
RTX A6000 + AMD 3990x, and I never have Intel GPU. Comparing to DS 4.23 PB, the lag can be seen when orbiting View, with just one G9 in the scene ~~
Okay.... still, I'd rather test a Beta...
What does "Adaptive subdivision/displacement" mean?
DS2025's crash notification leaves something to be desired.
In this case I am not certain but as I recall it has, in other things (including 3delight) meant effectively SubD on the fly as needed rather than having to set a division level for the whole model. That is, in the not altogether likely event that I am remembering correctly, why 3Delight can use displacement for fine detail on modles with large polygons without requiring an impossible level of division for the whole model.
Yes, this has been reproted (by me, at least) - clicking More will still allow you to save the crash report, though.
While I have a Window 11 with an RTX-40 series card, I still have two Win 10, GTX 1080 and 1080Ti machines with D|S on them. I read the following and Googled what it referred to. Am I correct it is better to not install Daz Studio 2025 on the Windows 10 computers at all? (This is not an issue, I have been thinking of mothballing them anyway. Only the 1080 machine still allows me to fix the categorization of products.)
NVIDIA Iray 2024.1:
Another reason I would be happy to not install it, they are running out of room on the C: drive for more programs that have to be stored there. I have all content that can be moved off onto other drives.
Deprecatewd means they are supported for now but probably not soon. So you could install and use this version (though the memory may be tight) but a future update may no longer support the 10x0 cards in Iray.
Where are the settings for adaptive subdivision?
Adaptive displacement seems to work great (though I'm finding it hard to expose the parameters on models with existing displacement setups), but I cannot figure out how or where to configure adaptive sub-D.
If you add a displacement map to a surface it turns on an extra option
A slider called "Displacement Adaptive Quality". The pre-defined limits are 0-10,000
I made a plane primative, added a displacment map, set the SubD Displ level to 12 then set the new slider to 750 to make sure I could see any differeence between o and 750 and now my Studio install is just resizing it's app window and not letting me do anything yet.
I didn't see any difference at zero, will report back once Studiop returns to full screen and lets me have control again.
So far it's used 2GB of system ram and 4.3GB VRAM. doesn't seem to be increasing over that so far.
edit: now it's not responding. 12 levels of SubD and 750 of the new setting may have been too much :)
I'll kill it and try gain
I have a small tool that I use for myself which spawns an external program using DzProcess. That is not working in 2025 because DzProcess is gone. Is it possible to see any kind of documentation for scripting yet where I could look for an alternative? Or is it possible this will be added back eventually to the scripting api?
EDIT: just found it myself in the changelog actually:
QProcessAPI has changed significantly since the Daz Script wrapper for it, which is based on the Qt 3 API, was implementedLooks like we get better displacement at lower SubD levels with it.
This is a patch of tileable human skin in 32bit greyscale
I used the same map for both Diffuse and displacement
Both of these are at subD level 1
The first image is Adapt level 1, the 2nd is Adapt level 10
It looks really good to me, I could have done better on the test images, but It was fast work.
I think that the Sub-D level you set in the surfaces editor doesn't get used when you've got the adaptive parameter active.
The adaptive parameter seems to be number of samples per-pixel, so values over 4 or so are going to be pretty diminishing returns for most work. Also, I have yet to get adaptive working on a figure. None of the default materials will expose the adaptive parameter when displacement is added.
I'm having a hard time figuring out what the relationship is between the *material* level settings for adaptive displacement (which uses subD) and the *object itself*, which seems to be independant from the displacement subD settings.
Okay, super-happy camper here. I'm able to add my audio file to my scene and hear it (for lip syncing), then output a .mov file; the .mov file generated is a container file linked to the rendered frames in the D|S temp folder.
If I take the .mov file and drop it in iMovie, it outputs a complete mp4 file, with sound. No more manually linking the frames, then adding the audio after, then generating the mp4.
I still have to start converting things to Filament and Filatoon, but I am a very happy camper. Three minutes to generate a final, 1080p mp4 movie clip:
https://sterdan.com/wp-content/uploads/2025/04/04-Rinn-Test.mp4
Now, if they'd "unretire" Mimic or supply something similar, I'd be 100%... but I'm pretty darn happy with 95%.
No issues nor crashes while testing all the rendering. Best. Tuesday. Ever.
Why on earth did you remove preview lighting mode? That is going to generate so much support hate for you guys, why change something so profound and leave no alternative "use legacy preview lighting" or something?
e: "Use Headlamp" is not a good substitute, i.e. if the camera is hidden it doesn't light preview; what if I don't want headlamp style lighting in preview?