Daz Studio 2025 ALPHA - version 6.25.2025.32308! (Updated November 20, 2025)

Richard Haseltine · July 21

jbowler said:

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

Isn't that the issue reported a bit up-thread which, as I recall, affects other drawstyles too.

jbowler · July 21

Richard Haseltine said:

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.

No, I'm aware of that bug too and it has been extensively reported. These days I put the scene at world centre and the camera at the required distance. I don't use sports, or purient, photog focal lengths either; I typically aim for 80mm (35mm equivalent).

The issue might have already existed because turning "on" preview lights under the "Windows" menu would invariably zap the scene in a camera view. I don't do that (well, I've learned to turn off preview lights when it happens). What is happening now and is completely reproducible is that a scene with a camera with **no** headlight (none of my cameras have headlights, all my lights are in the scene) no longer renders in the "textured" camera view if the camera itself is not "visible in viewport".

It really is that simple. Simple. Simply a bug.

The same annoying insect bites in "Universal" view, whatever that is, but not in "filament" or "Iray".

1121314108 · July 21

Richard Haseltine said:

1121314108 said:

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.

are you using display scaling?

yes,windows 175% scaling,but I also tried 100% scaling,nothing changes.

Ainm · July 21

Richard Haseltine said:

Ainm said:

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.

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

Ah, excellent! Alpha, while still needing some work, is streets ahead in usability and responsiveness for me. This bug is the only thing stopping me from using it alongside 4 in my workflow. Will be a very happy camper when that update releases.

evilded777 · July 21

So what is the story with scripting?

I rely on many, many scripts and UI improvements via scripts. I can't go from 0 to render without them. Am I going to have to, as someone else suggested, do everything in 4 and then use 5 to render? Simple things like Look at Camera scripts don't even work properly. Is everything going to have to be updated by vendors?

DoctorJellybean · July 21

evilded777 said:

So what is the story with scripting?

I rely on many, many scripts and UI improvements via scripts. I can't go from 0 to render without them. Am I going to have to, as someone else suggested, do everything in 4 and then use 5 to render? Simple things like Look at Camera scripts don't even work properly. Is everything going to have to be updated by vendors?

It will be up to the vendors to check their scripts for compatability. As you noted, Look at Camera is one of them. From my own experiments, there are scripts which work as is.

Leana · July 21

evilded777 said:

So what is the story with scripting?

There were changes to both the scripting engine and SDK, so some scripts still work "as is" but others need an update in DS2025 depending on what they do and which features they use.

evilded777 · July 21

DoctorJellybean said:

evilded777 said:

So what is the story with scripting?

I rely on many, many scripts and UI improvements via scripts. I can't go from 0 to render without them. Am I going to have to, as someone else suggested, do everything in 4 and then use 5 to render? Simple things like Look at Camera scripts don't even work properly. Is everything going to have to be updated by vendors?

It will be up to the vendors to check their scripts for compatability. As you noted, Look at Camera is one of them. From my own experiments, there are scripts which work as is.

It will be up to the vendors is really not the answer I wanted to hear (god forbid we have to buy updated tools for this). I understand this is an alpha and there are dramatic changes under the hood but destroying workflows that have taken years to develop...that's harsh. Is there anyone with better scripting knowledge than I who can give a glimpse into how hard this is going to be for vendors to update?

Totte · July 21

evilded777 said:

DoctorJellybean said:

evilded777 said:

So what is the story with scripting?

I rely on many, many scripts and UI improvements via scripts. I can't go from 0 to render without them. Am I going to have to, as someone else suggested, do everything in 4 and then use 5 to render? Simple things like Look at Camera scripts don't even work properly. Is everything going to have to be updated by vendors?

It will be up to the vendors to check their scripts for compatability. As you noted, Look at Camera is one of them. From my own experiments, there are scripts which work as is.

It will be up to the vendors is really not the answer I wanted to hear (god forbid we have to buy updated tools for this). I understand this is an alpha and there are dramatic changes under the hood but destroying workflows that have taken years to develop...that's harsh. Is there anyone with better scripting knowledge than I who can give a glimpse into how hard this is going to be for vendors to update?

Simple scripts that do something simple might work without changes. Smaller scripts with GUI, a handful of hundred of lines of code, depending on age (what DS version they were written for), it might take from a few hours to a day. Larger scripts or script systems, tens of ks of line, can take several weeks to move over, specially of things you heavily rely on no longer exists or is deeply changed.

The most time consuming part after the actual coding to solve everything that just gives errors, is testing, as you never know if something you reply on working a certain way, suddenly doesn't because Qt has changed the plumbings.

willem_cornelis_46c075d549 · July 21

alpha-version-6-25-2025-19807 is a real mess for me, it has such a memory leak that after 5 minutes Daz studio blocks completely.

Can I get a link to the previous version?

Leana · July 21

Previous versions are not available for download once a new one is released

Xandyr78 · July 22

...am I reading this roadmap/announcement correctly? The Geometry Editor is being moved under the Premier Exclusive list of features? I'm a Premier Subscriber, and even I find this...a bit problematic, honestly. Perhaps I'm misunderstanding the announcement?

I'm also saddened to see the 3DL retirement. I still use 3DL in some capacities. Is there any way to get a download of 4.24 that I could install beside my 4.25 installation for when I need it or its elements?

barbult · July 22

4.24 is the latest General Release. You can download it and install it with DIM. There is no 4.25 version.

Stretch65 · July 22

Is it DAZ's intention to make sure that all scripts that run under Studio v4.24, will run correctly under Studio 2025? It's just that I've written an awful lot of scripts and would hate to rewrite them all.

Leana · July 22

Xandyr78 said:

...am I reading this roadmap/announcement correctly? The Geometry Editor is being moved under the Premier Exclusive list of features? I'm a Premier Subscriber, and even I find this...a bit problematic, honestly. Perhaps I'm misunderstanding the announcement?

The announcement was about Geometry sculptor, which is already a Premier feature.

Leana · July 22

Stretch65 said:

Is it DAZ's intention to make sure that all scripts that run under Studio v4.24, will run correctly under Studio 2025?

There were charges to both the script engine and SDK, so while some scripts will work fine "as is", other scripts will require adjustments.

Stretch65 · July 22

Leana said:

Stretch65 said:

Is it DAZ's intention to make sure that all scripts that run under Studio v4.24, will run correctly under Studio 2025?

There were charges to both the script engine and SDK, so while some scripts will work fine "as is", other scripts will require adjustments.

There are certain scripts from 3rd party authors that I have come to rely on. If those authors have retired or left the store, and their scripts no longer work, where does that leave me? Can't they have 2 script engines? One for legacy scripts, and one for new scripts? I'm kind of freaking out here because I've spent months tailoring my content to work with certain scripts.

namffuak · July 22

Stretch65 said:

Leana said:

Stretch65 said:

Is it DAZ's intention to make sure that all scripts that run under Studio v4.24, will run correctly under Studio 2025?

There were charges to both the script engine and SDK, so while some scripts will work fine "as is", other scripts will require adjustments.

There are certain scripts from 3rd party authors that I have come to rely on. If those authors have retired or left the store, and their scripts no longer work, where does that leave me? Can't they have 2 script engines? One for legacy scripts, and one for new scripts? I'm kind of freaking out here because I've spent months tailoring my content to work with certain scripts.

Studio 4 will still run; the scripts will work there. The third party scripts are mostly encrypted (extension .dse) and this is a one-way encryption process so these cannot be converted to the new scripting engine that is part of Qt 6.So it becomes a question of whether the original authors are still around AND think that re-working old scripts will be worthwhile.

Leana · July 22

Stretch65 said:

There are certain scripts from 3rd party authors that I have come to rely on. If those authors have retired or left the store, and their scripts no longer work, where does that leave me?

With scripts which work in DS4, which is still available.

Can't they have 2 script engines? One for legacy scripts, and one for new scripts?

The script engine is linked to the version of Qt used AFAIK, so I don't think that would be possible.

And as namffuak mentioned, scripts are encrypted so only their creators can edit them unfortunately.

Totte · July 22

Stretch65 said:

Is it DAZ's intention to make sure that all scripts that run under Studio v4.24, will run correctly under Studio 2025? It's just that I've written an awful lot of scripts and would hate to rewrite them all.

Qt 6 script engine is changed a lot, new ECMA standard, from 5 to 7+, whicvh means some thing that were not considered an error in ECMA 5, now is. It also , as I wrote before, what DS version the script was originally written for. The APIs have been updated over the years of DS 4, and a lot of APIs have been marked as deprecated for almost a decade now, and now they will be gone.

Dude3DLab · July 22

I've founda bug that is very annoying indeed, so basically to replicate it just have the autosave feature activated, and let it run with daz3d minimized if the autosave activates It completitly stops DAZ3D and don't let me maximize it again, making me have to close daz on task manager

DoctorJellybean · July 22

Dude3DLab said:

I've founda bug that is very annoying indeed, so basically to replicate it just have the autosave feature activated, and let it run with daz3d minimized if the autosave activates It completitly stops DAZ3D and don't let me maximize it again, making me have to close daz on task manager

We will need some more information please, e.g. were you rendering when you minimized, a static load scene, how long was the timer set for?

Stretch65 · July 22

Leana said:

Stretch65 said:

There are certain scripts from 3rd party authors that I have come to rely on. If those authors have retired or left the store, and their scripts no longer work, where does that leave me?

With scripts which work in DS4, which is still available.

Can't they have 2 script engines? One for legacy scripts, and one for new scripts?

The script engine is linked to the version of Qt used AFAIK, so I don't think that would be possible.

And as namffuak mentioned, scripts are encrypted so only their creators can edit them unfortunately.

I was wondering about DAZ's policy towards encrypted scripts. I understand why authors encrypt them, i.e. to protect their intellectual propery, but if any author ceases to support a script for whatever reason, couldn't the DAZ Store keep an un-encrypted version which is made available to users? Is that such an unreasonable policy? It would mean users who still need the script's functionality, can at least view the code and perhaps update it.

johndoe_36eb90b0 · July 22

DoctorJellybean said:

Dude3DLab said:

I've founda bug that is very annoying indeed, so basically to replicate it just have the autosave feature activated, and let it run with daz3d minimized if the autosave activates It completitly stops DAZ3D and don't let me maximize it again, making me have to close daz on task manager

We will need some more information please, e.g. were you rendering when you minimized, a static load scene, how long was the timer set for?

I don't think that's a separate bug or related to autosave in any way -- it's the problem with Win+D or Win+M hanging Daz Studio on restore which I reported upthread and Richard confirmed.

Richard Haseltine · July 22

Stretch65 said:

Leana said:

Stretch65 said:

There are certain scripts from 3rd party authors that I have come to rely on. If those authors have retired or left the store, and their scripts no longer work, where does that leave me?

With scripts which work in DS4, which is still available.

Can't they have 2 script engines? One for legacy scripts, and one for new scripts?

The script engine is linked to the version of Qt used AFAIK, so I don't think that would be possible.

And as namffuak mentioned, scripts are encrypted so only their creators can edit them unfortunately.

I was wondering about DAZ's policy towards encrypted scripts. I understand why authors encrypt them, i.e. to protect their intellectual propery, but if any author ceases to support a script for whatever reason, couldn't the DAZ Store keep an un-encrypted version which is made available to users? Is that such an unreasonable policy? It would mean users who still need the script's functionality, can at least view the code and perhaps update it.

Yes, it would be unreasonable for Daz to take over another person's intellectual property without permission.

Richard Haseltine · July 22

Xandyr78 said:

...am I reading this roadmap/announcement correctly? The Geometry Editor is being moved under the Premier Exclusive list of features? I'm a Premier Subscriber, and even I find this...a bit problematic, honestly. Perhaps I'm misunderstanding the announcement?

I'm also saddened to see the 3DL retirement. I still use 3DL in some capacities. Is there any way to get a download of 4.24 that I could install beside my 4.25 installation for when I need it or its elements?

4.25? This thread is on DS 2025, and nothing has been said about the version number of DS 4 that will remove 3Delight - which is not yet the current version, so yes you can just back up your isntallers for it and its plug-ins right now. See https://www.daz3d.com/forums/discussion/737346/just-got-a-notice-about-3delight-being-retired#latest

DS 2025 was never going to be able to include 3Delight as the version in DS 4 is very old (due to a chnage after that point in the shader language used) and so lacks a version that would be compatible with the updated DS application.

Imago · July 22

Any chance to see the timeline scrubbing working, the keyframes copy-pasting fixed and the graph panning increased in the Alpha?

It has been already stripped of the only reliable render engine, please at least make the timeline fully functional.

liam_moore1977 · July 22

Been playing with this for a few days now and like most others, the viewport performance is glitchy and slow especially in iray preview mode. Messed around with a lot of settings and nothing seemed to help. Tried the nvidia game ready and studio drivers, but it's the same on both. I imagine this stuff will be fixed pretty quickly with optimizations and enabling and tweaking iray 2024 features.

The one area I really hope gets fixed soon is streaming from iray server. I have a render pc in another room with a 4090, a 5090 and a 4070ti super that I send my jobs off to from my workstation in my office. Keeps things cool in my office and allows me to work in Daz while I'm rendering images. But when I do animations, I need to use streaming mode from the bridge tab in render settings since this is the only way to render animations in iray server, but no go in daz 2025. I hope I don't have to wait too long for this to get addressed though because straming through daz 2025 is the only way I can use my 5090 for animations. Right now I've gotta do it through 4.24 and only the 4090 and 4070ti super can be used. I just wish iray 2024 would be added to 4.24. Honestly this would solve everything for me.

gelstat · July 22

Hi,

With my rtx3090 and SD 576.80, when using for the first time iray preview not work.

The launch runs in a loop without changing the texture of the preload (usually gray and white like 4.xx). The color remained the same as the colors in texture shader mode. Daz Studio froze for a moment, scrolling the bar at the bottom right until Daz started working again, but still with the colors in texture shader mode.
However, if you change the material of an element in the scene, in this case a clothing, the Iray preview mode starts to load (changing the preload colors to gray and white) and Iray preview starts to work.
And it still works when Daz Studio is restarted.

That's it for my second test.

Richard Haseltine · July 22

liam_moore1977 said:

Been playing with this for a few days now and like most others, the viewport performance is glitchy and slow especially in iray preview mode. Messed around with a lot of settings and nothing seemed to help. Tried the nvidia game ready and studio drivers, but it's the same on both. I imagine this stuff will be fixed pretty quickly with optimizations and enabling and tweaking iray 2024 features.

The one area I really hope gets fixed soon is streaming from iray server. I have a render pc in another room with a 4090, a 5090 and a 4070ti super that I send my jobs off to from my workstation in my office. Keeps things cool in my office and allows me to work in Daz while I'm rendering images. But when I do animations, I need to use streaming mode from the bridge tab in render settings since this is the only way to render animations in iray server, but no go in daz 2025. I hope I don't have to wait too long for this to get addressed though because straming through daz 2025 is the only way I can use my 5090 for animations. Right now I've gotta do it through 4.24 and only the 4090 and 4070ti super can be used. I just wish iray 2024 would be added to 4.24. Honestly this would solve everything for me.

As explaned in the past, Iray 2024 cannot be made avaialble in DS 4.x.x.x as it's binary interface is incomapatible (and chnaging that is making a new version of DS, with all that that entails). There was an initial release of Iray 2024 that could be integrated, but serious bugs were found and it had to be removed. The bug-fixed version was then binary incompatible, and remains so.

http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log_4_24_0_3#4_23_1_1
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log_4_24_0_3#4_23_1_7

Iray Server is developed by nVidia, all Daz Studio does is connect to it and send it data. Those aspects have not been updated recently - see

Notifications

Daz Studio 2025 ALPHA - version 6.25.2025.32308! (Updated November 20, 2025)

Comments

Adding to Cart…