Daz Studio 2025 ALPHA - version 6.25.2025.35308! (Updated December 19, 2025)

qq_81ee1a28 · January 10

Anyone knows when Plugin support for 6.x will be implemented?

Richard Haseltine · January 10

qq_81ee1a28 said:

Anyone knows when Plugin support for 6.x will be implemented?

The chnage log shows that an SDK is being worked on. Once that is done and stable developers will be able to make DS 2026 plug-ins, and update older plug-ins. Whether that will happen for any given plug-in will be up to the PA who wrote it, if theya re still alive and active (some are not), and so will whether the result is a free update, a paid upgrade, or a fuill new version. Older plug-ins in themselves will not work.

Richard Haseltine · January 10

TromNek said:

If you specify

--workers ALL

It will startup workers for all 9 protocols that the latest version supports.

I think that goes back to: Iray RTX 2021.0.4 , build 344800.12856 , 16 Mar 2022, nt-x86-64

So DS 4 can launch newer Iray that way or DS 2025 can launch older version of Iray? If it is the former it is iunteresting and useful (though better posted to another thread, not one on the DS 2025 alpha).

Falco · January 10

Richard Haseltine said:

TromNek said:

If you specify

--workers ALL

It will startup workers for all 9 protocols that the latest version supports.

I think that goes back to: Iray RTX 2021.0.4 , build 344800.12856 , 16 Mar 2022, nt-x86-64

So DS 4 can launch newer Iray that way or DS 2025 can launch older version of Iray? If it is the former it is iunteresting and useful (though better posted to another thread, not one on the DS 2025 alpha).

I don't believe so, because the transfer from DS4 will use whatever Iray version Daz is sending, and there is still the issue of card compatibilty with that version of Iray. So if the card on your Iray Server supported multiple versions of Iray, or you had multiple GPUs like a 3090 and a 5090 in the same machine, or multiple computers with different cards hooked into the server, it could render multiple jobs using different versions I think. But because the 50 series cards don't work with previous versions of Iray, if you send a job encoded in a previous version, the server can handle it, but the GPU the server is using won't be able to work with it.

I just tried sending a DS4 job to Iray server and it accepted it fine, but when I tried to start the render using my 5090, it errored out with the message below:

[Sat, 10 Jan 2026 12:41:04] 3 WORKER_6 | [test1] [Renderer] Error: Rendering failed with error code -3: Invalid parameters (\c NULL pointer).

The only real benefit of this info is that you can upgrade to the newest version of Iray Server without having to worry about compatibility, it will use whatever version of Iray the job is encoded in, even if its older. But you still have to match the GPU used to the Iray version of the job.

Richard Haseltine · January 10

Falco said:

Richard Haseltine said:

TromNek said:

If you specify

--workers ALL

It will startup workers for all 9 protocols that the latest version supports.

I think that goes back to: Iray RTX 2021.0.4 , build 344800.12856 , 16 Mar 2022, nt-x86-64

So DS 4 can launch newer Iray that way or DS 2025 can launch older version of Iray? If it is the former it is iunteresting and useful (though better posted to another thread, not one on the DS 2025 alpha).

I don't believe so, because the transfer from DS4 will use whatever Iray version Daz is sending, and there is still the issue of card compatibilty with that version of Iray. So if the card on your Iray Server supported multiple versions of Iray, or you had multiple GPUs like a 3090 and a 5090 in the same machine, or multiple computers with different cards hooked into the server, it could render multiple jobs using different versions I think. But because the 50 series cards don't work with previous versions of Iray, if you send a job encoded in a previous version, the server can handle it, but the GPU the server is using won't be able to work with it.

I just tried sending a DS4 job to Iray server and it accepted it fine, but when I tried to start the render using my 5090, it errored out with the message below:

[Sat, 10 Jan 2026 12:41:04] 3 WORKER_6 | [test1] [Renderer] Error: Rendering failed with error code -3: Invalid parameters (\c NULL pointer).

The only real benefit of this info is that you can upgrade to the newest version of Iray Server without having to worry about compatibility, it will use whatever version of Iray the job is encoded in, even if its older. But you still have to match the GPU used to the Iray version of the job.

That was what I was expecting.

TromNek · January 11

Richard Haseltine said:

Falco said:

I just tried sending a DS4 job to Iray server and it accepted it fine, but when I tried to start the render using my 5090, it errored out with the message below:

[Sat, 10 Jan 2026 12:41:04] 3 WORKER_6 | [test1] [Renderer] Error: Rendering failed with error code -3: Invalid parameters (\c NULL pointer).

The only real benefit of this info is that you can upgrade to the newest version of Iray Server without having to worry about compatibility, it will use whatever version of Iray the job is encoded in, even if its older. But you still have to match the GPU used to the Iray version of the job.

That was what I was expecting.

Very unfortunate. Thanks for checking (I don't have a 50xx card to test with)

I just looked at an older version of of the (protocol) workers in Iray Server. It looks like they don't re-compile the older workers when they release a new version. So what you tested now makes sense to me. In that, a worker is compiled to support all the Nvidia cards that are avaliable at the time of an Iray Server build. So an older iray worker does may not be compatible with a new Nvidia card released after that release.

I'll start a new forum thread to discuss Iray Server stuff.

Many thanks !

johndoe_36eb90b0 · January 13

Richard, when it comes to accessibility Daz Studio is totally broken.

Try this -- put display (not font) scaling in Windows to 125%.

Try right clicking on a node in the scene and reaching select children from submenu.

Depending on where you click and where the menu opens you either can or can't reach it because the menu closes when you move the mouse to enter submenu where select children option is.

I understand this is alpha and it's a big rewrite to move to QT 6 but these kind of issues should be part of UX testing and accessibility should be baked in from the start, not an afterthought.

As it is, Daz Sudio doesn't respect font scaling, and apparently has issues with display scaling as well.

Not everyone has 20/20 vision you know.

Rod Wise Driggo · January 16

For everyone experiencing interface trouble (tiny fonts etc.) on Mac I can recommend Better Display https://github.com/waydabber/BetterDisplay
Allows easy change of display preferences and disabling of HiDPI. Did make using the current build fine for me.

Pickle Renderer · January 18

Maybe noted by others but my mouse cursor disappears quite frequently. I haven't found a "trick" to make it return either (or a solid repro). It's just the cursor icon itself as I can see from mouse-over effects it's still moving around. If there's a trick to getting it back that would be cool. Otherwise I quite like the alpha so far.

schouwenburg · January 18

A bug I often encounter in all the alpha's. A reasonable complex scene .say 5 figures + enviroment. Delete lets say half of the scene because you want to reuse part of it. No problem until now. Place something new in the scene and then us the mouse to move objects or zoom. Many times it will crash immediately. If you save the 'reused' scene and then reload everything is fine.

NewVision · January 20

Due to it's now 2026, will the DAZ Studio 2025 Alpha be renamed and go to beta stadium?

DoctorJellybean · January 20

NewVision said:

Due to it's now 2026, will the DAZ Studio 2025 Alpha be renamed and go to beta stadium?

It will most likely be DAZ Studio 2026. As for beta status, no indications have been given yet.

Richard Haseltine · January 20

Change log numbers already seem to use 2026 in the last few, Private Build, entries https://docs.daz3d.com/public/software/dazstudio/6/change_log

devin066 · January 21

With Daz Studio 2025 6.25, my Iray view is not rendering properly. It is just rendering the base colors and not doing a full render with textures, etc on a Nvidia 5070 TI, latest drivers, win 11. Everything therefore just renders as very white.

Richard Haseltine · January 21

Pure white or very white? In the latter case it might just be the Tone Mapping (horribly over-exposed)

Pickle Renderer · January 21

Probably not going out on a limb here when I say that maybe there are some significant changes to the object model such that certain scripts will no longer work? The very simple ones I write still work, but some products seem to have broken. Alternatively... if I discover such things with the alpha I should report an issue?

Leana · January 21

Pickle Renderer said:

Probably not going out on a limb here when I say that maybe there are some significant changes to the object model such that certain scripts will no longer work? The very simple ones I write still work, but some products seem to have broken.

There were changes to both the script engine and the SDK, so yes some scripts don't work as is.

devin066 · January 21

Richard Haseltine said:

Pure white or very white? In the latter case it might just be the Tone Mapping (horribly over-exposed)

I checked many things such as tone mapping and all are normal. I think its just rendering base colors because non-white objects are rendering in their respective color. Its like when you change render types in the view and it flickers a little before it gets to the iray render. Mine is just getting stuck on the base color render and decides to stop there, its done enough for the day. Could coincide with my update to 6.25 on 12/23 though it was okay to begin with, then it would stall in white mode but minutes later maybe render, now its stuck just not rendering the viewport. Note the yellow jacket in the attached.

Richard Haseltine · January 21

Have you checked the log file (Help>Troubleshooting>View Log File) for errors?

devin066 · January 21

Good idea, but looks normal:

2026-01-21 10:57:39.863 [INFO] :: Locking viewport redraw...
2026-01-21 10:57:39.863 [INFO] :: Viewport redraw locked.
2026-01-21 10:57:39.866 [VERBOSE] :: Native format content directories: 3
2026-01-21 10:57:39.866 [VERBOSE] :: Poser format content directories: 3
2026-01-21 10:57:39.866 [VERBOSE] :: Other import format content directories: 0
2026-01-21 10:57:39.866 [INFO] :: Begin asset load (merge): /data/DAZ 3D/Genesis 8/Female/Morphs/Mousso/Lilianna/Lilianna Lashes MAT.duf
2026-01-21 10:57:39.869 [INFO] :: Determining missing assets...
2026-01-21 10:57:39.876 [INFO] :: Setting textures...
2026-01-21 10:57:39.876 [INFO] :: Creating materials...
2026-01-21 10:57:39.878 [INFO] :: Applying animations...
2026-01-21 10:57:39.885 [INFO] :: Setting up follow targets...
2026-01-21 10:57:39.885 [INFO] :: Finished asset load (merge):  - /data/DAZ 3D/Genesis 8/Female/Morphs/Mousso/Lilianna/Lilianna Lashes MAT.duf
2026-01-21 10:57:39.886 [INFO] :: Unlocking viewport redraw...
2026-01-21 10:57:39.886 [INFO] :: Viewport redraw unlocked.
2026-01-21 10:57:39.888 [INFO] :: Finished Loading Character Addons
2026-01-21 10:57:39.894 [INFO] :: Finished asset load (open):  - /People/Genesis 8 Female/Characters/Lilianna.duf
2026-01-21 10:57:40.280 [INFO] :: Unlocking viewport redraw...
2026-01-21 10:57:40.280 [INFO] :: Viewport redraw unlocked.

DoctorJellybean · January 21

devin066 said:

Richard Haseltine said:

Pure white or very white? In the latter case it might just be the Tone Mapping (horribly over-exposed)

I checked many things such as tone mapping and all are normal. I think its just rendering base colors because non-white objects are rendering in their respective color. Its like when you change render types in the view and it flickers a little before it gets to the iray render. Mine is just getting stuck on the base color render and decides to stop there, its done enough for the day. Could coincide with my update to 6.25 on 12/23 though it was okay to begin with, then it would stall in white mode but minutes later maybe render, now its stuck just not rendering the viewport. Note the yellow jacket in the attached.

Do you start in Iray Preview mode, or switch to it once you've loaded the assets? In case I've missed it, what are your system specs and driver version?

devin066 · January 21

I've started Daz with Iray mode by default, loaded Gen 8, and get white figure. I've also switched in and out of iray mode to filament, texture shaded, etc. When I go back to Iray, its white. Daz Studio 2025 (6.25) Public Build loaded about 12/23/25. NVIDIA Studio Driver 591.74 which I installed recently to try and fix, but issue spans this and the previous driver, but was working fine maybe before 6.25 install. Ryzen 7, 32GB, NVIDIA 5070 TI 16 GB, Windows 11 Home, 24H2 26100.7623.

devin066 · January 22

Success! Rolling back 2 driver versions from 591.74 to 591.44 seems to work. Also did a factory reset of Daz at the same time, but it was probably the driver...

glencoesmith · January 23

Anyone else having an issue where their spacemouse isn't working, aside from zooming in and out?

TromNek · January 23

glencoesmith said:

Anyone else having an issue where their spacemouse isn't working, aside from zooming in and out?\

Same for me, just zoom in and out.

Older 4.24.xxx is working.

I don't really use my spacemouse (SpaceMouse Wireless) with Daz. I couldn't get my settings comfortable.

Would you be willing to share your configuation file for Daz Studio with me ?

Robert Freise · January 23

Never got spacemouse to work

Poisoned Mind · January 27

Daz Studio is not user friendly anymore! Feel sorry for the newbies and the veterans alike.

maureen4486 · January 27

Squishy said:

Richard Haseltine said:

Squishy said:

Yeah this is actually also headlamp lighting, because the render options also force it by default. This isn't the same as the preview lighting available in current and all previous versions (which seems to be just gone). The difference is you have no contrast with headlamp lighting so it makes it much harder to perceive volume and shape.

There isn't a "preview light". When Preview Lights is on the non-PBR drawstyles attempt to do that, preview the lights (actual light nodes, not emissives or environment). When Preview Lights is off it uses a non-rendering headlamp-stylelight. The command is still in the Window menu, and it does work if there are light nodes (but I don't get a dark scene if I turn Preview Lights on in a scene with no lights in Texture Shaded mode).

Yeah that's what I dislike. This is a big change from earlier versions, in that you currently don't need any light nodes and can work in preview with just material based lighting. Now to duplicate this, I have to manually add a distant light - sure, fine, not a big deal - but I have to toggle it on and off with every render or when using Iray preview. Really baffling user hostile change.

I know it's been quite some time since this discussion about Preview Lights took place, but it made me curious, so I decided to do some tests. I took a series of screen captures in both Daz 4.24 and Daz 2025, and here are the results. Again, these are screen captures., not renders.

The top set were done in Daz 4.24:
Left: Preview Light OFF, no scene lights, no camera
Center: Preview Light ON, scene light on, no camera
Right: Preview Light ON, no scene lights, no camera

The bottom set were done in Daz 2025:
Left: Preview Light OFF, no scene lights, no camera
Center: Preview Light ON, scene light on (had to be made much brighter), no camera,
Right: Preview Light ON, no scene lights, no camera

As you can see, there are differences in how the figure looks, especially between the two left images, in which preview lights are off. However, the overall behavior is the same, although 2025 needed the spotlight to be drastically brighter than what it was in 4.24. As one would expect, if there are no lights in the scene, then Preview Lights isn't going to work. You can't preview what does not exist.

I did notice some differences in the lighting behavior when looking at a scene without lights though a camera. One of the most important things is that, in 4.24, it doesn't matter if the camera is visible or not. As long as the headlamp is on, you'll be able to see your scene through the camera when Preview Lights is on, although the light from the headlamp light isn't actually shown. The scene looks the same whether Preview Lights is on or off. In 2025, however, if the camera is not visible, then, when Preview Lights is on, the scene is black if there are no other lights. So while looking though a camera is when the behavior in 2025 changes significantly from previous versions.

I noticed that Squishy, who started the talk about Preview Lights, mentioned something about material based lights. I'm not sure what she meant by that. Was she talking about emissives? If so, I don't think Preview Lights ever worked with the light from emissives. It doesn't recognize that light being emitted from an object is light. The same is true for environment lights.

While working on a scene, I have always kept Preview Lights off unless I needed to check something like shadows. Then I could see anything and everything in the scene, lights or no lights. When you use only environment lights and/or emissives, you actually have to do it that way. Daz 2025 has not changed that.

That having been said, the truth is that, because of several reasons, I'd just stick with Daz 4.24 and have nothing to do with Daz 2025, if I could. Unfortunately, I don't have that option. My new computer has a NVIDIA RTX 5070 Ti graphics card. When I got it, I didn't know about iray not playing nice with the 5000 series cards and didn't find out until I realized that Daz 4.24 was completely ignoring the card, using only the CPU, which massively slows down renders. So I guess I'll be doing all the work in 4.24 and then bringing scenes over into 2025 for rendering, that is unless certain issues get resolved by the time 2025 is ready for general release, whenever that will be. Maybe in 2027?

Pickle Renderer · January 27

So everything seems to be a lot snappier and faster, e.g. for example, putting a dot in puppeteer then restoring that pose somewhere else on the timeline. It's very fast now. So is loading a scene, starting a new scene,etc.

Would it be possible for a developer to do a blog on what they changed to internals in order to make this happen? It was a problem with Daz for years and I'm genuinely interested in how it was solved.

Richard Haseltine · January 27

Poisoned Mind said:

Daz Studio is not user friendly anymore! Feel sorry for the newbies and the veterans alike.

That is not useful feedback - in what ways is it user unfriendly, how is that different from before?

Notifications

Daz Studio 2025 ALPHA - version 6.25.2025.35308! (Updated December 19, 2025)

Comments

Adding to Cart…