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
True, about multiple configurations,etc.The issues in the previous release (timeline related) and this latest release (dForce hair related) don't seem to be limited to a specific machine or configuration, though. I haven't seen anyone posting evidence of "It works fine for me." Both timeline and dForce are major areas of DS functionality. That is why I question whether any significant regression testing is happening, to identify things have been broken. Sometimes during development it is necessary to break something existing to start implementing something new. If it is intentional, they should tell us, so we don't have to waste time installing things that will impact ongoing work, or waste time reporting what they already know is broken.
I'm sorry your work was impacted and time wasted. Thank goodness you kept a backup of the previous version. I do the same thing every time a new version is released, so I can always revert.
Thanks, but like you I'm keeping back-ups of each Alpha so the only time lost was uninstalling and reinstalling, measured in minutes. The first thing I tested on installation was the animation I'm working on and once I saw that wasn't going to work, it was out with the new and in with the old.
For what it's worth, for what I'm using it for the Alpha's been working very well wtih very, very few crashes, but it's just Filatoon animation, I'm not stress-testing it the way others are. I'm even doing multiple lip syncs with muliple characters with multiple audio tracks and exporting multiple .mov files from a single DAZ Studio file, so I'm mostly having a ball.
Well, it's not kernels. I just simulated clothing, shut alpha down and then tried loading AM tiger.
Node selection.
On the POSITIVE side, I bought 5060 Ti yesterday and am now running 4.xxx dforce simulation.
The Cuda, they core!
Are you on a Mac and need DS6 Alpha to use Filatoon?
I see now the keyframes can be selected and moved in the timeline, nice to see some fixes.
Quick question: Is normal to see very little options in the IRay render settings pane? Did I miss something?
No less but even more ~~ What did you see ?
Frankly speaking, I really don't like the way of showing Colors in Scene pane:
Better be sort of these:
I checked with some of my Qt developer friends, sth. like the above could be done ~~
Yup.
Ya, the latest update froze when loading most of my subsets (Customized characters only). No idea why. No log showing anything.
Problem 1: Render Settings, Environment Map
Cannot select "exr" or "hdr" files
Only available options: dsi, jpeg, jpg, png
Problem 2: libdsp_dzimageio plugin won't load
My configuration: Daz Studio 2025 ALPHA – Version 6.25.2025.25616! (Updated September 16, 2025) on Mac Mini M4
No issue on my side with Win11. That seems to be an issue specifically to Mac.
Problem 2 would be the cause of Problem 1 - imageio is Image Input/Output
This is an alpha version, UI styling is one of the things that has not yet been addressed - this is mentioned in the Evegreen thead.
More infromation is needed - including how long you waited before declaring the application frozen (I have generally found character Character presets slow to load, shape and materials are much more efficient on my system, but this doesn't seem to be an issue for others - if this is Character presets it is possible that your alpha is behaving like my any version and your DS 4 like other people's any release; iff so then any additional info you can find might actually enable to figure out the cause).
Please post a screen shot of your Render Settings.
So I tested this:
AM Tiger in ALPHA froze the program and did not load even as 20 minutes passed.
In base release, it loaded in a few seconds.
The set 13 alpha won't load any of my scenes, period. Complete unusable as of right now. Been looking to see if I could roll it back but have yet to find a way.
load app, try to load duf and the application freezes. No log, no nothing. It just stops responding and eventually windows prompts me to close it.
What does the log say?
Metadata issue split to https://www.daz3d.com/forums/discussion/743331/certain-outfits-breaking-metadata
One thing I've noticed in all of the alpha versions is that any HDRI over 8k immediately crashed the Alpha version, while 4.24 doesn't have any issues with them. It hasn't been a big deal for me and I assumed it would get fixed eventually, but with the newest Alpha version, I'm now noticing that instead of immediately crashing, loading an HDRI over 8k now does the sit and spin forever thing until you force Daz to close, similar to what others have been reporting for their scenes. I'm wondering if for those who are getting this issue, are you using an HDRI that is over 8k?
I couldn't reproduce the issue with the latest Alpha by using 8K and 16K HDRIs, no matter by loading a Render Settings Preset or direclty browsing to load... Rendering with them also works fine.
What's your OS ?
Windows 11. https://polyhaven.com/a/horn-koppe_spring is an example. The 16k version of it works fine in 4.24 but in Alpha it's always immediately crashed when loading, and now it just sits and spins forever. The 8k version works just fine. It does it for others too but this is just an example.
I'm also with Win11. I could load it with no issue by now. Maybe you can restart you Windows then retry ?
Now it returned to normal somehow. But before I had only the format (image size), folder, kind of render and headlamp settings. It was like having the "viewport" engine selected and I'm absolutely sure IRay was selected, otherwise the Spot Render whould give me the "select an active engone" message.
Ah, yes, about the Spot render: If I start a spot render selecting an area within the aspect frame, it works fine but if I end a bit over the area (like exagerating the selection) the render hangs. in 4.21 the spot render starts correctly and render only the area inside the Aspect frame as normal behaviour even if I go on the secondary monitor during the selection.
Ah, got it ~
But for the Spot Render, I couldn't reproduce the issue either... Maybe other folks can also give it a test.
Not a bug really, but an observation. I have been using the alpha as my every day Daz on an M4 Macbook Air for a few weeks now. The speed of loading of G9 has allowed me to finally make that switch to using G9 characters, Plus having faster iray and finally being able to use filament in addition to pretty good stability (Daz 4 on Mac has not been the most stable thing) has been enough that I only open the regular Daz 4 release when I need a script I'm missing (though many scripts crash Daz 4 on Mac anyway). Two days ago I upgraded my MacOS to Tahoe. Yesterday I updated Daz to the latest alpha. I used to be able to start a scene rendering and then go an watch youtube with no issues. Now I have noticed youtube stutters very badly when Daz is rendering. I don't know if it is something different in the latest Daz alpha or in Tahoe's load management. When I have some time I need to experimment and see how Daz 4 behaves or switch back to the previous alpha (which is backed up). Just wondering if any of the Mac users have seen a difference since updating.
Most of my scenes now cause DAZ Alpha to hang on load since the newest update.Previous version was working great.
Windows 11, Nvidia 5090, latest Nvidia Game Ready drivers.
Is there any way to roll back to previous Alpha version? I can't get any work done now.
Only if you kept a backup of the previous downloads file, as there's no way to download previous versions again.
If you have a backup: