Daz Studio 2026 Beta - version 6.25.2026.13921! (Updated May 20, 2026)

Richard Haseltine · April 27

barbult said:

DoctorJellybean said:

WendyLuvsCatz said:

I tried reading through if this had been answered

what is Universal Drawstyle?

a compromise between Textured and Filament or something new?

I noticed Depth been added too

https://docs.daz3d.com/public/software/dazstudio/6/change_log#6_25_2025_15923

But where is the explanation of what they do? A link to the change log is not very helpful.

It allows you to mix drwastyles, so you can override individual objects to have them in differnt styles - for example, one might be smooth shaded and another wire shaded so that you could readily see when the two were begining to intersect 9and so have the lines of the wire shaded disappear inside the other). I believe it is "universal" because it can use any standard style (not Iray or Filament, which are totally different engines).

DoctorJellybean · April 27

WendyLuvsCatz said:

I tried reading through if this had been answered

what is Universal Drawstyle?

a compromise between Textured and Filament or something new?

I noticed Depth been added too

As Richard posted.

Universal Draw Style allows you to specify one scene wide draw style (in draw settings) and then override that draw style on individual nodes and materials ("DrawStyle Override" override property on these respective element).
Depth is used to make an image recording the depth of the scene, which can be useful for some post processing.

WendyLuvsCatz · April 27

DoctorJellybean said:

WendyLuvsCatz said:

I tried reading through if this had been answered

what is Universal Drawstyle?

a compromise between Textured and Filament or something new?

I noticed Depth been added too

As Richard posted.

Universal Draw Style allows you to specify one scene wide draw style (in draw settings) and then override that draw style on individual nodes and materials ("DrawStyle Override" override property on these respective element).
Depth is used to make an image recording the depth of the scene, which can be useful for some post processing.

I know what depth is, I used it with the iray render on facebook for a 3D image

johndoe_36eb90b0 · April 27

I concur with all the posts saying that 5090 is awfully slow in Daz Studio 2026 viewport.

kntwnrrlnd_e7a0939b26 · April 29

Bug report:

Version: 2026.9715 (2026 beta version)

OS: Windows 11

Issue: When using the deformer spline adjusting tool it fails to function at all.

Severity: High. Tool is unusable.

Steps to reproduce:

Create any type of object (ex a cube).

Create a deformer on the object to modify the shape.

Attempt to alter the spline by pressing 'Edit Spline...'.

Observe that the edit window is very slow to show, seemingly using up 100% of one CPU core for an extended period of time, and the entire application freezes up for a bit.

Once the edit window is visible attempt to select any square (or 'knot' as they seem to be called here). Observe that only the rightmost knot can be selected.

The same goes for creating new knots. These will be created correctly but cannot be selected so any alteration will always be made to the last knot.

Workarounds: None found

kntwnrrlnd_e7a0939b26 · April 29

Spline issue window:

DoctorJellybean · April 29

kntwnrrlnd_e7a0939b26 said:

Bug report:

Version: 2026.9715 (2026 beta version)

OS: Windows 11

Issue: When using the deformer spline adjusting tool it fails to function at all.

Severity: High. Tool is unusable.

Steps to reproduce:

Create any type of object (ex a cube).

Create a deformer on the object to modify the shape.

Attempt to alter the spline by pressing 'Edit Spline...'.

Observe that the edit window is very slow to show, seemingly using up 100% of one CPU core for an extended period of time, and the entire application freezes up for a bit.

Once the edit window is visible attempt to select any square (or 'knot' as they seem to be called here). Observe that only the rightmost knot can be selected.

The same goes for creating new knots. These will be created correctly but cannot be selected so any alteration will always be made to the last knot.

Workarounds: None found

Bug reports should be submitted here:

https://bugs.daz3d.com/hc/en-us/requests/new

kntwnrrlnd_e7a0939b26 · April 29

Thanks but I get:

"oops

The page you were looking for doesn't exist

You may have mistyped the address or the page may have moved"

When I attempt to use that link.

There exists no way of selecting the beta version for general techical support. The only version I can select is the 4.X versions.

Also see Richard Haseltines post: "Yes - report here first, a ticket later if it isn't resolved in thread would be my suggestion." - though I suppose that may be wrong/outdated.

I could, I suppose, submit a general technical support request (suing N/A as version) but that doesn't seem to quite fall in line with a bug report on a beta release. This would be more in line with getting support on a full release.

If there is another working page/process I can use would be grateful though.

DoctorJellybean · April 29

kntwnrrlnd_e7a0939b26 said:

Thanks but I get:

"oops

The page you were looking for doesn't exist

You may have mistyped the address or the page may have moved"

When I attempt to use that link.

There exists no way of selecting the beta version for general techical support. The only version I can select is the 4.X versions.

Also see Richard Haseltines post: "Yes - report here first, a ticket later if it isn't resolved in thread would be my suggestion." - though I suppose that may be wrong/outdated.

I could, I suppose, submit a general technical support request (suing N/A as version) but that doesn't seem to quite fall in line with a bug report on a beta release. This would be more in line with getting support on a full release.

If there is another working page/process I can use would be grateful though.

Link fixed.

kntwnrrlnd_e7a0939b26 · April 29

Thanks, I thought you might mean that page but as I indicated the support page has no version to select for 2026 beta tickets.

Can anyone kindly clarify the process here if bug reports should go into technical support as a 'Not Applicable' version and that earlier discussions on reporting on 2026 Alpha/Beta in this thread are no longer valid?

(I merely ask to avoid sending bug tracking tickets/report to the wrong place as this can cause hassle for the devs and/or the tickets to go missing)

DoctorJellybean · April 29

kntwnrrlnd_e7a0939b26 said:

Thanks, I thought you might mean that page but as I indicated the support page has no version to select for 2026 beta tickets.

Can anyone kindly clarify the process here if bug reports should go into technical support as a 'Not Applicable' version and that earlier discussions on reporting on 2026 Alpha/Beta in this thread are no longer valid?

(I merely ask to avoid sending bug tracking tickets/report to the wrong place as this can cause hassle for the devs and/or the tickets to go missing)

Enter DS 2026 in the Application Version Number(optional) box and actual bug report, it'll be done internally.

kntwnrrlnd_e7a0939b26 · April 29

Thanks a bunch. I'll try it out.

TBorNot · May 1

Daz Studion 2026 is throwing out warning messages about not being suppoorted soon on MacOS.

DoctorJellybean · May 1

TBorNot said:

Daz Studion 2026 is throwing out warning messages about not being suppoorted soon on MacOS.

They are aware of that.

inquire · May 1

Yes, because Daz has never developed a version of DS That can run natively on an apple silicon chip. DS only runs in emulation. The next version of the macOS will probably not include that emulation. Apple reasons that it has given developers long enough to convert their software to something that will run on the new Apple chips. It has been years, and years.

Richard Haseltine · May 2

inquire said:

Yes, because Daz has never developed a version of DS That can run natively on an apple silicon chip. DS only runs in emulation. The next version of the macOS will probably not include that emulation. Apple reasons that it has given developers long enough to convert their software to something that will run on the new Apple chips. It has been years, and years.

AsfarasI know the version of the Qt framework used in DS 4 could not be compiled for Apple Silicon, so DS 6 was necessary - and indeed the Evergreen thread indicates that an Apple Silicon version is planned, though not yet available. They still have well over a year before there will be an issue, as I understand it from the previous posts.

attilaszkablin · May 2

Any info about when the windows display UI scaling settings messing up the whole DAZ Studio UI (making it blurry, hard to read) will be fixed?
This is not an issue in DAZ 4

DoctorJellybean · May 2

attilaszkablin said:

Any info about when the windows display UI scaling settings messing up the whole DAZ Studio UI (making it blurry, hard to read) will be fixed?
This is not an issue in DAZ 4

Please provide your system and monitor specs.

duvy2 · May 2

Hey all, I hope it comes to the right topic, I never used the non-alpha versions, since I have rtx 50s gpu. I found a strange behaviour of the timeline: I'm setting up keyframes and defining the characters posing. At some point when I apply a pose, somehow it influences backwards the existing keyframes, moving my characters historically into a bad positions. I tried to: select everything in the scene, create a key frame of them in the beginning, and at some certain point (type: node recursive), I hoped it might help, but just encountered the issue again. Am I missing something? Why a future selected frame influencing a previous one? It's just messing up my works for hours backwards.

Richard Haseltine · May 2

duvy2 said:

Hey all, I hope it comes to the right topic, I never used the non-alpha versions, since I have rtx 50s gpu. I found a strange behaviour of the timeline: I'm setting up keyframes and defining the characters posing. At some point when I apply a pose, somehow it influences backwards the existing keyframes, moving my characters historically into a bad positions. I tried to: select everything in the scene, create a key frame of them in the beginning, and at some certain point (type: node recursive), I hoped it might help, but just encountered the issue again. Am I missing something? Why a future selected frame influencing a previous one? It's just messing up my works for hours backwards.

By default DS will try to drawa a smooth curve through each key frame, so changing a pose in frame n can affect previous frames that don't have a key for that particular property. Setting a key for the proeprty should fix it in the keyed frame, but won't necessarily protect downstrream or upstream frames thata re not keyed. If you don't want to have smooth interpolation (if you are just usiing the frames as snapshots) then consider chnaging the default interpolation type - I am not sure if this script works in DS 6 or not, but I don't think it does anything high-risk so there is a good chance it will. Setting the default timeline interpolation to linear - Daz 3D Forums

Falco · May 4

Are HD morphs fully implemented/functional in the beta, both authoring and using?

Richard Haseltine · May 4

Falco said:

Are HD morphs fully implemented/functional in the beta, both authoring and using?

The import tool is limited to PAs, we don't have it and I don't know if it is updated. HD moprhs certainly work in DS 6

hapciupalit · May 4

Any idea when the viewport will improve on this version? I've been checking each version since June/July last year. And the viewport is still really, really laggy, even with a small scene that includes a small room and one or two characters and I can assure you this is not a PC problem. I have a i9 14900K, 128GB RAM, 2x5090. Daz 4.24 is very smooth, but since I can't render in it, I have to use this Beta version, but it still not usable.

Falco · May 4

Yea a lot of us are in this situation unfortunately. There are some reports the 5090 has it worse than others, as people have reported better performance with a 4090. It really sucks to spend all this money on an upgraded GPU only to get worse performance than if we hadn't upgraded.

hapciupalit said:

Any idea when the viewport will improve on this version? I've been checking each version since June/July last year. And the viewport is still really, really laggy, even with a small scene that includes a small room and one or two characters and I can assure you this is not a PC problem. I have a i9 14900K, 128GB RAM, 2x5090. Daz 4.24 is very smooth, but since I can't render in it, I have to use this Beta version, but it still not usable.

jd641 · May 4

I just tried the latest 2026 beta, I'm not sure if its DAZ that needs to add support or 3Dconnexion but my SpaceMouse isn't working at all and I can't tolerate using Studio without it. Is there something I need to configure?

barbult · May 4

jd641 said:

I just tried the latest 2026 beta, I'm not sure if its DAZ that needs to add support or 3Dconnexion but my SpaceMouse isn't working at all and I can't tolerate using Studio without it. Is there something I need to configure?

Check this out https://www.daz3d.com/forums/discussion/759601/bj-3dconnexion-3d-mouse-plugin-for-daz-studio-2026

eman · May 4

I still can't see anything in the opengl viewport and I get these warnings:

2026-05-04 23:07:30.830 [WARNING] :: Failed to link shader program: Error: Fail to build reflection info.

2026-05-04 23:07:30.831 [WARNING] :: Failed to build graphics pipeline: Creation Failed
2026-05-04 23:07:39.725 [WARNING] :: Failed to link shader program: Error: Fail to build reflection info.

2026-05-04 23:07:39.725 [WARNING] :: Failed to build graphics pipeline: Creation Failed

amd ryzen with radeon graphics

hapciupalit · May 5

Falco said:

Yea a lot of us are in this situation unfortunately. There are some reports the 5090 has it worse than others, as people have reported better performance with a 4090. It really sucks to spend all this money on an upgraded GPU only to get worse performance than if we hadn't upgraded.

hapciupalit said:

Any idea when the viewport will improve on this version? I've been checking each version since June/July last year. And the viewport is still really, really laggy, even with a small scene that includes a small room and one or two characters and I can assure you this is not a PC problem. I have a i9 14900K, 128GB RAM, 2x5090. Daz 4.24 is very smooth, but since I can't render in it, I have to use this Beta version, but it still not usable.

Yeah... I have upgraded my rig before I knew Daz didn't support it well. What I end up doing now is work in Daz 4.24 prepare the scene and then check it in Daz 2026. But it's a bit annoying to keep reloading the scene just to test the iray. The rendering so far seems to be working really well, it's just the viiewport that is a complete mess.

r4fmed · May 5

Is "Display optimization" option not available in Daz 2026? It is in Preferences>Interface in Daz 4.24. But it's missing in new Daz Studio 2026.

Richard Haseltine · May 5

r4fmed said:

Is "Display optimization" option not available in Daz 2026? It is in Preferences>Interface in Daz 4.24. But it's missing in new Daz Studio 2026.

The viewport code has been extensively reworked, I believe, so the setting may well be irrelevant now.

Notifications

Daz Studio 2026 Beta - version 6.25.2026.13921! (Updated May 20, 2026)

Comments

"oops

The page you were looking for doesn't exist

"oops

The page you were looking for doesn't exist

Adding to Cart…