Daz Studio 2026 Beta - version 6.25.2026.12107! (Updated May 04, 2026)

comradenikola92 · May 6

johndoe_36eb90b0 said:

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

Same. It's been like this since launch and they've done nothing about it. They blame drivers and other things, but it takes a simple runtime profiling to pinpoint where the 50x0s create problems compared to the same run on a 40x0 card.

But it's mostly a moot point because you can just use 2026 as a rendering frontend for queueing because, as it stands now, it's still useless for anything else. It'll be years before all the plugins and stuff updates to it.

Tugpsx · May 6

I must say the built in AI function is awesome. Very knowledgeable on scripting too, that was a good surprise. Asked about animation and it had good suggestions and procedures with accurate directions. Job well done.

DoctorJellybean · May 6

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.

Could you, or anyone else with viewport issues, please provide a a basic scene using Daz Originals content where possible which shows this behaviour. You should also list the products used, so that I can test your scene on my system.

Ron Knights · May 6

It's funny because I'm still working with an ancient nVidia 1660 Super with 6GB VRAM.

The display looks fine. But I don't load anything really intense or complicated.

And, yes, my GPU has been or will be deprecated (spelling?!)

halvardeq · May 6

I definitely understand that software development is hard, and coding to as varied a hardware ecosystem as the PC doesn't help, but we're a year out of the 5000-series launch and the DAZ viewport issue appears to have remained static, or even gotten worse. It simply adds too much inefficiency to pose on one PC and render on the other.

It's reached the point where we'll have to discontinue our DAZ Premiere subscription and migrate workflows into another tool.

We're hopeful the tool will have improved sufficiently to budget for it next FY.

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.

gamingmods897 · May 7

Is anyone also facing issue , I recently build my PC using 5060 Ti 16GB from GTX 1650 for DAZStudio rendering but even though I am using Latest DAZ Studio 2026 beta , I am not getting that much of speed which I have expected from it its Taking around 10-15 minutes to render a character with some lightning background, could someone suggest me hot to fix it.

hapciupalit · May 7

DoctorJellybean said:

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.

Could you, or anyone else with viewport issues, please provide a a basic scene using Daz Originals content where possible which shows this behaviour. You should also list the products used, so that I can test your scene on my system.

Usually any room that has a bit more props and have one or two characters. But when the environment is bigger and you have already one character is already a mess. For example just put a character inside this environment and you can check to see how it goes.
https://www.daz3d.com/new-york-brownstones?srsltid=AfmBOopBnudvWjmoPhrjcGwtG02PXjWBjvybuuP5H-kdqgdgWD3Y5DoU
This one is a bit big. In my case I can barely move in the scene.

Padone · May 7

Just my two cents here. I'm noticing most people complains for the alpha/beta not working properly, as if it should. I mean reporting bugs is fine as this is what a beta is for. On the contrary complaining about bugs makes little sense, as again this is what a beta is for. Then one can understand that support for new cards or processors is desirable, but nobody is forced to go for new hardware. I mean personally I upgrade the hardware when the software I'm using requires it, rather than the other way around, this also makes the overall pipeline better for production, as usually older harware is more tested and stable.

hapciupalit · May 7

I agree. This is beta version, so bugs are expected. They have reworked the software entierly for this 2026 version which makes sense for bugs to happen. But the viewport is lagging in the same way for almost a year now. They keep adding new features to this version, which are great, but the basics are not working.
In my case I was asking if they are working on improving the viewport, rather than complaining. Just so I can have a rough estimate when I'll be able to use it

Richard Haseltine · May 7

gamingmods897 said:

Is anyone also facing issue , I recently build my PC using 5060 Ti 16GB from GTX 1650 for DAZStudio rendering but even though I am using Latest DAZ Studio 2026 beta , I am not getting that much of speed which I have expected from it its Taking around 10-15 minutes to render a character with some lightning background, could someone suggest me hot to fix it.

What are your picks in the Hardware tab of Render Settings? What driver are you using? If you go to the log (Help>Troubleshooting>View Log File) are theer any errors during rendering, and what does it give for device usage in the final summary?

DoctorJellybean · May 7

Richard Haseltine said:

gamingmods897 said:

Is anyone also facing issue , I recently build my PC using 5060 Ti 16GB from GTX 1650 for DAZStudio rendering but even though I am using Latest DAZ Studio 2026 beta , I am not getting that much of speed which I have expected from it its Taking around 10-15 minutes to render a character with some lightning background, could someone suggest me hot to fix it.

What are your picks in the Hardware tab of Render Settings? What driver are you using? If you go to the log (Help>Troubleshooting>View Log File) are theer any errors during rendering, and what does it give for device usage in the final summary?

Also, it might be worthwhile to check Render Settings - Hardware tab, and uncheck CPU in both Modes.

Richard Haseltine · May 7

DoctorJellybean said:

Richard Haseltine said:

gamingmods897 said:

Is anyone also facing issue , I recently build my PC using 5060 Ti 16GB from GTX 1650 for DAZStudio rendering but even though I am using Latest DAZ Studio 2026 beta , I am not getting that much of speed which I have expected from it its Taking around 10-15 minutes to render a character with some lightning background, could someone suggest me hot to fix it.

What are your picks in the Hardware tab of Render Settings? What driver are you using? If you go to the log (Help>Troubleshooting>View Log File) are theer any errors during rendering, and what does it give for device usage in the final summary?

Also, it might be worthwhile to check Render Settings - Hardware tab, and uncheck CPU in both Modes.

Yes, it is counterintuitive but sometimes having the CPU add its mite can actually degrade performance (I guess because it is trying to do two things, manage the render and do some of the work).

Chakradude · May 7

Totte said:

I could see a use for someone making a product much like the Old 3Delight LPR Render ( or what it is called ), where you render a bunch of layers and masks and generate a Photoshop file where you easily could merge those different layers using the masks to do some advanced render postprocessing...

I think I had a product from dreamlite that did something like that (back when I could afford photoshop)

pivasmanya · May 9

Three months ago, I wanted to write another message about how painful and unpleasant it was to work in Viewport version 26. For some reason, I didn't send it then. I guess I thought it would take a while for the developers to fix the most basic system of any 3D graphics program.

Please fix your camera and controls. It's been so long, so many updates, and yet the direct control mode, when you need to quickly move the camera around the scene, hasn't been fixed. The camera twitches, sometimes jams, or moves jerkily. Everything works perfectly in 24. Why is it so hard to transfer these settings to 26? This problem isn't just mine. It's a common one. Please!

But no. The developers probably don't work at DAZ themselves. Or they're just so lucky they don't have these problems.
(And don't even bother telling me about "returning the camera to the center of the world, moving it here and there, etc.; that's all just crazy.)

bluejaunte · May 9

Probably a good idea if we start putting some numbers out. Download MSI Afterburner and activate the overlay. Show fps and probably the frametime graph so we can see what's actually happening.

jmucchiello · May 9

pivasmanya said:

Three months ago, I wanted to write another message about how painful and unpleasant it was to work in Viewport version 26. For some reason, I didn't send it then. I guess I thought it would take a while for the developers to fix the most basic system of any 3D graphics program.

Please fix your camera and controls. It's been so long, so many updates, and yet the direct control mode, when you need to quickly move the camera around the scene, hasn't been fixed. The camera twitches, sometimes jams, or moves jerkily. Everything works perfectly in 24. Why is it so hard to transfer these settings to 26? This problem isn't just mine. It's a common one. Please!

But no. The developers probably don't work at DAZ themselves. Or they're just so lucky they don't have these problems.
(And don't even bother telling me about "returning the camera to the center of the world, moving it here and there, etc.; that's all just crazy.)

The only issue I've had with the beta viewport is it sometimes goes completely black after making changes to geometry or position. It flashes black for 2-3 seconds. But, I've never seen any "camera twitches."

halvardeq · May 10

Padone said:

Just my two cents here. I'm noticing most people complains for the alpha/beta not working properly, as if it should. I mean reporting bugs is fine as this is what a beta is for. On the contrary complaining about bugs makes little sense, as again this is what a beta is for. Then one can understand that support for new cards or processors is desirable, but nobody is forced to go for new hardware. I mean personally I upgrade the hardware when the software I'm using requires it, rather than the other way around, this also makes the overall pipeline better for production, as usually older harware is more tested and stable.

I understand your perfectly reasonable position all things being equal. I also recognize that this was a bit of a perfect storm: DAZ didn't remove 32-bit CUDA from iRay and the 5000 series, nVidia did.

I'd posit the reason that all things *aren't* equal in this case is that the entire state of the art for nVidia GPUs has been impacted for over a year. If simply switching to AMD were an option, that would be great, but iRay is targeted at a sole GPU manufacturer natively unless one invests in a third party render pipeline like Octane. The 4000 generation is no longer even manufactured.

This isn't a minor inconvience, it's a showstopper for daily production use for anyone with a computer purchased in 2025 or later. For a year.

Ron Knights · May 10

Maybe it's just me, but I won't put much effort into a Beta version of any software.

Yeah, I'll load something and maybe Render an image.

But that's about it. It's a Beta.

WendyLuvsCatz · May 10

Ron Knights said:

Maybe it's just me, but I won't put much effort into a Beta version of any software.

Yeah, I'll load something and maybe Render an image.

But that's about it. It's a Beta.

some users, (better off than you or me) have new 5### cards and little choice

wsterdan · May 10

WendyLuvsCatz said:

Ron Knights said:

Maybe it's just me, but I won't put much effort into a Beta version of any software.

Yeah, I'll load something and maybe Render an image.

But that's about it. It's a Beta.

some users, (better off than you or me) have new 5### cards and little choice

Or they have Macs and want to use Filament or Filatoon...

Ron Knights · May 10

I hear you. I have a lowly nVidia 1660 Super with 6GB VRAM. It's been (being?) deprecated.

I will soon be left in the dust.

But I've learned the hard way not to stress out too much about things I can't change.

I still feel the excitement of the experience, until I run into problems due to the BETA state.

jmucchiello · May 10

The beta works better for me than 4.24 using a 4090. I don't need the beta to use my card. But for general usefulness of the GUI, it's already an improvement. If my plugins and scripts were supported, I'd have no reason to use 4.24 any more.

RustyBln · 7:50AM

I have the same viewport problems as many others here with the beta version. Navigating a bigger scene is almost impossible since it's so laggy. I'm using a 5090 on a 13600K and the CPU is disabled in the render settings. In fact It's so bad that I'm using DAZ 2026 only for rendering jobs. For all other stuff I'm still using my 4090 PC and DAZ 4.24 where I don't have any of these problems.

DoctorJellybean · 7:55AM

RustyBln said:

I have the same viewport problems as many others here with the beta version. Navigating a bigger scene is almost impossible since it's so laggy. I'm using a 5090 on a 13600K and the CPU is disabled in the render settings. In fact It's so bad that I'm using DAZ 2026 only for rendering jobs. For all other stuff I'm still using my 4090 PC and DAZ 4.24 where I don't have any of these problems.

It is being investigated.

mosjeschwartzman · 10:00AM

I'm experiencing something I haven't seen in this thread, as far as I can recall. In all honesty: I didn't revisit all 73 pages to check...

Here's what I'm experiencing: DAZ 2026 turns into a "ghost" app after hibernating the Windows laptop (when explicitly turning it into hibernation or by closing the lid which I set to make the laptop to hibernate). What do I mean with "ghost"? The app disapears from the taskbar, but I can't restart it from its shortcut. Checking the Task Manager shows the app is still running, but it consumes virtually no resources. Like it has crashed and cleared but not completely. As if a "lock" is still persisting.

The logfile doesn't show much usefull, I think, but I'm pasting the entries here anyway:

026-05-10 10:59:01.207 [INFO] :: Unlocking viewport redraw...
2026-05-10 10:59:01.209 [INFO] :: Viewport redraw unlocked.
2026-05-10 18:20:54.494 [WARNING] :: monitorData: Unable to obtain handle for monitor '\\.\DISPLAY1', defaulting to 96 DPI.
2026-05-10 18:20:54.547 [WARNING] :: monitorData: Unable to obtain handle for monitor '\\.\DISPLAY1', defaulting to 96 DPI.
2026-05-10 18:20:54.569 [WARNING] :: monitorData: Unable to obtain handle for monitor '\\.\DISPLAY1', defaulting to 96 DPI.
2026-05-10 18:20:54.585 [WARNING] :: monitorData: Unable to obtain handle for monitor '\\.\DISPLAY1', defaulting to 96 DPI.
2026-05-10 18:20:54.606 [WARNING] :: monitorData: Unable to obtain handle for monitor '\\.\DISPLAY1', defaulting to 96 DPI.
2026-05-10 18:20:54.622 [WARNING] :: monitorData: Unable to obtain handle for monitor '\\.\DISPLAY1', defaulting to 96 DPI.
2026-05-10 18:20:54.652 [WARNING] :: monitorData: Unable to obtain handle for monitor '\\.\DISPLAY1', defaulting to 96 DPI.
2026-05-10 18:20:54.669 [WARNING] :: monitorData: Unable to obtain handle for monitor '\\.\DISPLAY1', defaulting to 96 DPI.
2026-05-10 18:20:54.690 [WARNING] :: monitorData: Unable to obtain handle for monitor '\\.\DISPLAY1', defaulting to 96 DPI.
2026-05-11 11:43:01.480 +++++++++++++++ Daz Studio 6.25.2026.12107 starting +++++++++++++++++

After 11:00 yesterday I closed the lid of the laptop and around 18:20 I continued with something different. If I remember correctly I opened the laptop to look something up on Google; in any case, I wasn't using DAZ then. When done I closed the lid again. Later that evening I have watched an episode on Netflix. This morning at 11:40-ish I wanted continue in DAZ, finding it gone. Only after I killed the DAZ 2026 instance using the Task Manager I could start the app again.

I'm not having this behaviour 100% of the time. Somtimes the app will continue run over one or even more hibernations. But when it doesn't I need to kill the app explicitly.

Laptop is a Lenovo Legion 15akp10 - AMD AI 7 350, GTX 5070, 32 GB RAM

DoctorJellybean · 10:50AM

Does it happen with 4.x as well?

mosjeschwartzman · 2:50PM

DoctorJellybean said:

Does it happen with 4.x as well?

Good point, I didn't test that since I was using DAZ 2026 solely because of the GTX 5070. I'm testing it now; will report back.

Before the Legion, I had a Thinkpad P16 Gen 2 (Intel Core i9-13950HX vPro, 64 GB RAM and RTX ADA 4000) from my work and on that one neither version had this issue.

yonashald · 4:42PM

DoctorJellybean said:

RustyBln said:

I have the same viewport problems as many others here with the beta version. Navigating a bigger scene is almost impossible since it's so laggy. I'm using a 5090 on a 13600K and the CPU is disabled in the render settings. In fact It's so bad that I'm using DAZ 2026 only for rendering jobs. For all other stuff I'm still using my 4090 PC and DAZ 4.24 where I don't have any of these problems.

It is being investigated.

Investigated? I mean this has been known for so long at this point.... Everyone with a Geforce 50, has been saying for forever that 2026 viewport runs like a sack of potatos compared to 4.24, I'm sorry but it feels like Daz devs are really dragging their feet... I'm seriously suprised about how long this is taking to fix, I honestly expected more form the devs...

Richard Haseltine · 6:49PM

yonashald said:

DoctorJellybean said:

RustyBln said:

I have the same viewport problems as many others here with the beta version. Navigating a bigger scene is almost impossible since it's so laggy. I'm using a 5090 on a 13600K and the CPU is disabled in the render settings. In fact It's so bad that I'm using DAZ 2026 only for rendering jobs. For all other stuff I'm still using my 4090 PC and DAZ 4.24 where I don't have any of these problems.

It is being investigated.

Investigated? I mean this has been known for so long at this point.... Everyone with a Geforce 50, has been saying for forever that 2026 viewport runs like a sack of potatos compared to 4.24, I'm sorry but it feels like Daz devs are really dragging their feet... I'm seriously suprised about how long this is taking to fix, I honestly expected more form the devs...

I have a 5090 and the Viewport has seemed OK near to the centre, but weird things start to happen when the camera/view moves a few metres away from the centre (using the mouse wheel to zoom in/out a tad fixes it for a while). I haven't had a general navigation slow down, haven't really tried animation playback.

Notifications

Daz Studio 2026 Beta - version 6.25.2026.12107! (Updated May 04, 2026)

Comments

Adding to Cart…