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
I was able to load a character, dress, shoes, background, and hair and simulate it. And the hair did a Frankenstein's Wife and moved from a 40s era glamour girl into a full upright fall towards the sky! Deleted it, went for another hair, loaded it, and made the mistake not to save. I went into the scene area to delete a hair ornament that was not needed now and 'poof' Daz crashed. I rebooted the MacMini M4, opened the Alpha, loaded the last saved scene file, fixed the hair, checked the number of vertices. Almost 7million. Saved after every move I made. But I was successful in my render finally.
I was pleased to find I could use Power Pose and Simulate in the Alpha.
Thank you. It is one of a series I did using the scene. The other two are in my Art Studio thread.
https://www.daz3d.com/forums/discussion/139311/my-wips-renders-and-animations#latest ;
GPU?
Loading certain props seem to hang on load. One is SY Whips and Lashes for Genesis 3 and 8, the other is lightBlue belt
The logs get to
2025-08-16 16:23:04.955 [INFO] :: Determining missing assets...
2025-08-16 16:23:04.966 [INFO] :: Setting textures...
and then stops and the prop never loads. Scenes with those props do not load either, but if I remove the offending prop the scene (or subscene in my testing) loads fine.
These did load previously, before I got the last Alpha update Daz Studio 6.25.2025.22607
Are you sure they aren't just taking a long time? A chain would probably have a lot of geometry and chains and whips might each have a lot of bones.
I thought about that but let it sit for a long time, and defintley longer longer than Daz 4.5 took to load, but I didn't let it sit for an hour or so :) and my scene loaded before in a reasonable time (before the update). I'll load the prop now and see if it ever finishes.
That is a good point though, both the whip and the belt have a lot of bones so it may be related.
Currently the log this time is stopped at
2025-08-16 17:23:43.331 [INFO] :: Begin asset load (open): /Props/SY Whips And Lashes Genesis 3 and Genesis 8/Props/SYWAL Short Whip.duf
and it has been over 40 minutes
I'm pretty sure it is hung :)
I have uninstalled Daz Alpha through DIM and removed the directory and registry remnants, re-installed. I did not remove %appdata% pieces
I have two 5090's. Through devmgmt.msc disabled one, didn't help, disabled both, didn't help (I really don't want to pull the beast out again and pull cables :) )
I have tested both 5090's successfully independently with a scene that will load
Thanks
That does sound pretty extreme, but not terribly informative. Does Task Manager show activity (e.g. CPU activity or RAM increasing) for DS? Does a different Viewport Drawstyle help?
I'll try whatever you want. The rest of the system was responding fine so It isn't like Daz was running away with anything. But good idea, I'll check to see if memory increases that will indicate some processing. I'm not sure how the viewport comes into play. It does default to filament and I left it there. I'll try with texture
Yeah, weird, it is just not doing anything memory wise. It actually went down to xxx,608 now, but not fluctuating
CPU fluctuates but around 6.x%
Obviously the best thing is to have other people obvserve the same behavior. I don't know if you have that product to test, but if others do, maybe it is just me.
The script, which is not offiicial but is a personal offering by the author using the official spec, requires dzProcess - DS 2025 does not yet have the required process in its SDK/scripting - see https://www.daz3d.com/forums/discussion/comment/9137811/#Comment_9137811
Thanks ! but I don't understand.... I was talking about Plugins ~ so such issue has something to do with dzProcess ?
I believe the lack of DzProcess stops it from opening correctly, hence the unexpected results.
Can I post to ask people with the product to test (tee hee, already done)? and if I link to the product would that be considereded advertising for the product, and is that ok in this thread?
I could reproduce the issue ~ The Prop is very simple with just 2.3K polycounts + Iray Uber shader. It can be instantly loaded in DS 4.24.
I have no idea by now why it couldn't be loaded in DS 2025 ~~
Edit: Well, I think the culprit should be the bone hierarchy of this Prop (totally 43 sub-nodes levels)... Since there've been quite a few changes in terms of DzNode and DzBone etc, in DS 2025, more or less there're some bugs I think ~~
I tried deleting 20 bones, then it worked ~~~
I have seen the same behavior with a figure I had stored in previous versions. It has a lot of custom morphs, but I have narrowed it down to being connected to the Nagaleon tail. I have a re-rigged version of that I use, which has around twice the bones as the original version. I notice the original version loads slowly (>1 minute load time), and my re-rigged one doesn't load in 2 hours. I may leave it overnight tonight to see if it loads at all.
I also saw it lock up after the texture message, using around 1 CPU worth of load, so it seems to be spinning a single thread. I think the texture thing might be a red herring: I loaded the figure with all textures removed (just a plain white iRay surface) and got the same behavior. Not convinced that final log message is actually meaningful. I am somewhat suspicious of the depth of the chain of bones causing some weird issue, but it really is just a guess.
What is the use of Node Color ? How to change the color of multiple Nodes ? Why does the default Node Color have to be Black ...? Better be transparent... then the user can change the color on demand.
And the behavior of changing Node Color is weird, it doesn't work as expected, for instance, if I click to change the color of one Node, the color of some of its children nodes (not all...) are also changed ~~
Well, it's very annoying indeed ... as by now I cannot open both of 4.2x and 6.x ~~ a simple AutoFit will fail in DS 4.24 in this case ~~
I get the same with that product. Please submit a bug report.
See https://www.daz3d.com/forums/discussion/comment/9137811/#Comment_9137811
See the following Change Log entries
http://docs.daz3d.com/doku.php/public/software/dazstudio/6/change_log#6_25_2025_21907
http://docs.daz3d.com/doku.php/public/software/dazstudio/6/change_log#6_25_2025_22007
http://docs.daz3d.com/doku.php/public/software/dazstudio/6/change_log#6_25_2025_22308
http://docs.daz3d.com/doku.php/public/software/dazstudio/6/change_log#6_25_2025_22411
Transparency is a separate property to colour, so it couldn't be a value let alone the default.
Pointing at specific parts of the code is premature, though of course if you think you have specific issues (in general, not just in relation to this) it would be helpful to raise them for review.
Then... a wiser choice for me is to wait for a Beta or more reliable version ~
Inappropriate word ~~ better keep it as same as the Background Color of the Scene pane.
The ticket has been filled.
Hi. Just downloaded S2025 and installed it like two, three weeks ag and it really did some damage. It wiped out at least thre quarters of my assets, rendered very slow, made my download folder in the installmanager folder disappear, and makes all of my renders come out black. I am using Windows 11 if that makes a difference. Question: if I can go back to S4.15, would that fix everything?
Installing DS 2025 would not have done that, nor would it remove (or usurp the the file associations of) your DS 4.x.x.x. Installing a new version of DS, or anything else, would not remove the Downloads folder (literally remove, or empty - the latter might be done by reinstalling everything for some reason with delete after isntallation checked).
Slow/non rendering may be that you need a later drive or simply that your GPU is not supported - 4.15.x.x is a really old version and the requirements/supported GPUs have changed greatly (you mention both slow and blank so I am not sure which it is - unless the slow are iray and blank 3Delight, which is no longer present).
Not seeing the content in DS may simply be a matter of not having the folders to which some of your content is installed selected as content diectories (but before mirroring the DS 4 set up make sure you don't have issues like nested content directories, one selected location inside another).
I'm not sure if this is because of the Alpha or not, but is there a way to stop it asking for the 'filtered save' option when saving a loaded file? Neither of the previous versions to this with me, so I assume it's an Alpha thing, but might be a setting I'm not seeing?
What I mean is I'm about to go through and 'remaster' a bunch of previous works, and so I'll be opening old files, tweaking things and then saving it, but once I've tweaked it and hit 'CTRL+S' it SHOULD usually just automatically replace the current save file, but annoyingly this now opens a window like I've pressed 'Save As' and asks me to choose a file name and all that stuff which is uaully fine, but I don't want to have to do this over and over hundreds of times in the next few days if I can avoid it...
I've looked through the usual settings and can't find anythign, and it's not to do with keyboard shortcuts as it still happens when I click 'save' manually through the file menu.
Is this a setting I'm missing that I can change, or is this an Alpha thing that I've just gotta slog it out with for now?
That's because the Author Name you specified in DS 2025 Alpha is different from what you saved in your old Scenes. Check it via : Edit > Preferences > General tab > Authorship Information... in both of DS 4.24 and DS 2025 ~~
Different behavior of showing DUF file names in DS 2025 Alpha:
In cms database, a DUF file has two data fields related to its File Name: filename and default_filename . They can be different. The former is the latest modified one which comes from the file name physically saved.
Now in DS 4.x, it always shows filename which is a correct way (screenshot 1). But in DS 2025 Alpha, it shows default_filename which is a wrong way (screenshot 2). Screenshot 3 shows the file names of the DUF file in cms database ~~
Edit: I know why now... because of that new feature of Relabel in Content Library... It changes default_filename rather than the physical file name. However, showing default_filename in Content Library makes no sense at all to me ~ It's really confusing people and making things messy. Frankly speaking, this Relabel feature is totally useless to me.
Besides, if Copy such a Relabelled file, then Paste it to another folder, the physical file name rather than the relabelled one is back. These behaviors are not consistent ~ BTW, sorting is also wrong...
Instead, if really needed, the better way is to show default_filename in the tip when hovering mouse over the file thumbnail ~ or make this Relabel one of the features of Tagging... That default_filename shouldn't be modified by the user~