FWIW 2026 is Alpha not Beta.. You should expect it to be "buggier" than 2024. I'm running 6.25.2025.35308 with a 5070 TI and find a viewport render to be faster than 4.24 was with a 3090 TI. 2025 also loads a character/scene much much faster the 4.24. Granted I don't use viewport enders for anything other than quick texture or lighting checks. Straight renders in 2025 at 4000x6000 and up are man times faster than 4.24 and GPU temperatures about half the value of the 3090 TI.
I don't understand why the viewport in 2026 is so garbage (lagging much more even when using the same scenes) compared to the 4.24, I sadly have to use 2026 to render because I have a 50 graphic card, but God 2026 is so horrible, I know it's a BETA but damn..
I don't understand why the viewport in 2026 is so garbage (lagging much more even when using the same scenes) compared to the 4.24, I sadly have to use 2026 to render because I have a 50 graphic card, but God 2026 is so horrible, I know it's a BETA but damn..
Odd, I'm having the opposite experience on a 4090. Is this a 5090 thing maybe? Don't see why that would be the case though.
I don't understand why the viewport in 2026 is so garbage (lagging much more even when using the same scenes) compared to the 4.24, I sadly have to use 2026 to render because I have a 50 graphic card, but God 2026 is so horrible, I know it's a BETA but damn..
Odd, I'm having the opposite experience on a 4090. Is this a 5090 thing maybe? Don't see why that would be the case though.
I find that strange too, I have a 5090 Astral and I also experience significant slowdowns...
I don't understand why the viewport in 2026 is so garbage (lagging much more even when using the same scenes) compared to the 4.24, I sadly have to use 2026 to render because I have a 50 graphic card, but God 2026 is so horrible, I know it's a BETA but damn..
Odd, I'm having the opposite experience on a 4090. Is this a 5090 thing maybe? Don't see why that would be the case though.
I find that strange too, I have a 5090 Astral and I also experience significant slowdowns...
Same here - 5090 Astral on a Core 9 285k with 128 GB RAM; 4.24 - the viewport in any view is completely stutterless with HEAVY scenes loaded - 2026 latest with 2 characters jumps all over the place. I share the frustrations of every single 50-series owner - but why, why, why are people with 4090's even running the 2026 version?!!!!
I don't understand why the viewport in 2026 is so garbage (lagging much more even when using the same scenes) compared to the 4.24, I sadly have to use 2026 to render because I have a 50 graphic card, but God 2026 is so horrible, I know it's a BETA but damn..
Odd, I'm having the opposite experience on a 4090. Is this a 5090 thing maybe? Don't see why that would be the case though.
I find that strange too, I have a 5090 Astral and I also experience significant slowdowns...
Same here - 5090 Astral on a Core 9 285k with 128 GB RAM; 4.24 - the viewport in any view is completely stutterless with HEAVY scenes loaded - 2026 latest with 2 characters jumps all over the place. I share the frustrations of every single 50-series owner - but why, why, why are people with 4090's even running the 2026 version?!!!!
Because it's snappier? On 4090 at least, apparently. But in my case mostly for testing while I developed the 3d mouse plugin and ported my other plugins.
I don't understand why the viewport in 2026 is so garbage (lagging much more even when using the same scenes) compared to the 4.24, I sadly have to use 2026 to render because I have a 50 graphic card, but God 2026 is so horrible, I know it's a BETA but damn..
Odd, I'm having the opposite experience on a 4090. Is this a 5090 thing maybe? Don't see why that would be the case though.
I find that strange too, I have a 5090 Astral and I also experience significant slowdowns...
Same here - 5090 Astral on a Core 9 285k with 128 GB RAM; 4.24 - the viewport in any view is completely stutterless with HEAVY scenes loaded - 2026 latest with 2 characters jumps all over the place. I share the frustrations of every single 50-series owner - but why, why, why are people with 4090's even running the 2026 version?!!!!
Because it's snappier? On 4090 at least, apparently. But in my case mostly for testing while I developed the 3d mouse plugin and ported my other plugins.
So, the complete program overhaul works better on a 4090 than any of the 50-series it was actually made for? Interesting.. Worrying, but very interesting. Any other 30- or 40-series who can weigh in on this?
I don't understand why the viewport in 2026 is so garbage (lagging much more even when using the same scenes) compared to the 4.24, I sadly have to use 2026 to render because I have a 50 graphic card, but God 2026 is so horrible, I know it's a BETA but damn..
Odd, I'm having the opposite experience on a 4090. Is this a 5090 thing maybe? Don't see why that would be the case though.
I find that strange too, I have a 5090 Astral and I also experience significant slowdowns...
Same here - 5090 Astral on a Core 9 285k with 128 GB RAM; 4.24 - the viewport in any view is completely stutterless with HEAVY scenes loaded - 2026 latest with 2 characters jumps all over the place. I share the frustrations of every single 50-series owner - but why, why, why are people with 4090's even running the 2026 version?!!!!
Because it's snappier? On 4090 at least, apparently. But in my case mostly for testing while I developed the 3d mouse plugin and ported my other plugins.
So, the complete program overhaul works better on a 4090 than any of the 50-series it was actually made for? Interesting.. Worrying, but very interesting. Any other 30- or 40-series who can weigh in on this?
DS 2026/6 is not "made for" the newer cards, and daz would in fact have supported the cards in DS 4 if they could (the chnage log shows they added a version of Iray that had support, but it proved to be buggy during the internal/private testing and had to be rolled back). nVidia made chnages to the way they build the Iray code, and those changes cannot be supported in DS 4 so the updated Iray is DS 2026/6 only; but DS 2026/6 was being worked on anyway, for general reasons not for an unexpected issue with Iray.
Did some more testing. In a moderately complex scene with a G9 figure at subd 3 and a strand based hair, DS6 gives 40 fps while moving 3d mouse. Same thing in DS4 is like 18 fps (using the same 3d mouse plugin as well). However, once I remove the strand based hair, both of them are 40 fps. And I also notice that DS6 frametime graph is way more chaotic than DS4 so that means that fps from frame to frame must be way less consistent.
I then set the figure to subd 4 and no strand based hair. DS4 did 20 fps and DS6 still 36 fps. Added the strand based hair on top and DS4 was 15 while DS6 did 35 fps.
So only going from 20 to 15 fps in DS4 when adding strand based hair back in, which before resulted in going from 40 to 18 fps is a bit bewildering. But other than that I guess the new Qt6 OpenGL just handles lots of polys better, while having a weird ass seismograph for frametimes though.
Never mind frametime graph, it only happens when Aux viewport is also rendering the same thing. Still a bit weird it doesn't happen in DS4. I guess something in DS6 may cause the rendering of both viewports to alternate between each other or something weird, resulting in a messy frametime graph.
Simulating under 2026 is so much faster. The 60 frame simulation zipped by, until the surface exploded. That still takes forever to cancel. No idea why canceling operations can take forever in Daz, any version.
Thank you again, I am working on a standalone tool and QA is asking if it will support DS 2026. If there are changes then I will have to constantly update it. I wonder if it would be best to note the changes for the future and just release the tool for 4.2x and update it once 2026 is no longer Beta. Thanks Doc!
If it is a script, so far script engine in DS 6 hasn't really changed, so you could release a script for DS 6 ( I've done that, dual, DS 4 and DS 6 ), but for plugins, I'll wait until DS 6 SDK is frozen.
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 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...
first one would need to understand what it is
as a PA you also likely have a glimpse at the new SDK (not that it would be any use to me)
and therefore understand a bit more about it's purpose and functions
I only actually looked at this build because a Facebook friend with a 5### card couldn't use Filament on her machine
she says she doesn't have it in he dropdown
I still cannot help her there other than to say she can still use Filament in 4.24 without her Nvidia GPU
she was surprised when I showed a similar screenshot as she didn't have that
Are her drivers up to date? Filament requires at least OpenGL 4.1, which basically covers graphic cards released during the past 5 years. I have a 5090 myself.
she was surprised when I showed a similar screenshot as she didn't have that
Are her drivers up to date? Filament requires at least OpenGL 4.1, which basically covers graphic cards released during the past 5 years. I have a 5090 myself.
I suggested asking on the forum
I cannot diagnose someone elses PC since she dioes have Filament in 4.24 AFAIK I don't really know what's going on
I wasn't even using this beta hence just discovered the new drawstyles
deptn is very useful except it sadly ignores cutout opacity
Comments
FWIW 2026 is Alpha not Beta.. You should expect it to be "buggier" than 2024. I'm running 6.25.2025.35308 with a 5070 TI and find a viewport render to be faster than 4.24 was with a 3090 TI. 2025 also loads a character/scene much much faster the 4.24. Granted I don't use viewport enders for anything other than quick texture or lighting checks. Straight renders in 2025 at 4000x6000 and up are man times faster than 4.24 and GPU temperatures about half the value of the 3090 TI.
yonashald said:
It moved to beta a few builds ago.
I find that strange too, I have a 5090 Astral and I also experience significant slowdowns...
Same here - 5090 Astral on a Core 9 285k with 128 GB RAM; 4.24 - the viewport in any view is completely stutterless with HEAVY scenes loaded - 2026 latest with 2 characters jumps all over the place. I share the frustrations of every single 50-series owner - but why, why, why are people with 4090's even running the 2026 version?!!!!
I have a 4090 and it runs crisper on the beta than 4.24. If I had access to all my scripts and plugins, I'd only be running the beta.
So, the complete program overhaul works better on a 4090 than any of the 50-series it was actually made for? Interesting.. Worrying, but very interesting. Any other 30- or 40-series who can weigh in on this?
DS 2026/6 is not "made for" the newer cards, and daz would in fact have supported the cards in DS 4 if they could (the chnage log shows they added a version of Iray that had support, but it proved to be buggy during the internal/private testing and had to be rolled back). nVidia made chnages to the way they build the Iray code, and those changes cannot be supported in DS 4 so the updated Iray is DS 2026/6 only; but DS 2026/6 was being worked on anyway, for general reasons not for an unexpected issue with Iray.
Did some more testing. In a moderately complex scene with a G9 figure at subd 3 and a strand based hair, DS6 gives 40 fps while moving 3d mouse. Same thing in DS4 is like 18 fps (using the same 3d mouse plugin as well). However, once I remove the strand based hair, both of them are 40 fps. And I also notice that DS6 frametime graph is way more chaotic than DS4 so that means that fps from frame to frame must be way less consistent.
I then set the figure to subd 4 and no strand based hair. DS4 did 20 fps and DS6 still 36 fps. Added the strand based hair on top and DS4 was 15 while DS6 did 35 fps.
So only going from 20 to 15 fps in DS4 when adding strand based hair back in, which before resulted in going from 40 to 18 fps is a bit bewildering. But other than that I guess the new Qt6 OpenGL just handles lots of polys better, while having a weird ass seismograph for frametimes though.
Never mind frametime graph, it only happens when Aux viewport is also rendering the same thing. Still a bit weird it doesn't happen in DS4. I guess something in DS6 may cause the rendering of both viewports to alternate between each other or something weird, resulting in a messy frametime graph.
Simulating under 2026 is so much faster. The 60 frame simulation zipped by, until the surface exploded. That still takes forever to cancel. No idea why canceling operations can take forever in Daz, any version.
Now that Daz 6 is in beta, is there beta SDK available somewhere?
Indeed ( Check your DIM )
I can only see 4.5 SDK in DIM.
It's not available to the general public as yet. I suspect it will be once the features have been locked in.
It's a stand-alone windows application.
Does anyone know what the plan is for all those scripts? Will we need to repurchase them or will they be updated for exisiting owners?
That will be decided individually by the PAs.
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
I see it's been added but it doesn't tell me what it is
looks the worst
But where is the explanation of what they do? A link to the change log is not very helpful.
I've looked at universe a few times and then given up. No clue what it's purpose is.
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...
first one would need to understand what it is
as a PA you also likely have a glimpse at the new SDK (not that it would be any use to me)
and therefore understand a bit more about it's purpose and functions
I only actually looked at this build because a Facebook friend with a 5### card couldn't use Filament on her machine
she says she doesn't have it in he dropdown
I still cannot help her there other than to say she can still use Filament in 4.24 without her Nvidia GPU
I'm not sure why it isn't in her dropdown.
yes, I see it and can use it but I have a 2080Ti
she was surprised when I showed a similar screenshot as she didn't have that
Are her drivers up to date? Filament requires at least OpenGL 4.1, which basically covers graphic cards released during the past 5 years. I have a 5090 myself.
I suggested asking on the forum
I cannot diagnose someone elses PC since she dioes have Filament in 4.24 AFAIK I don't really know what's going on
I wasn't even using this beta hence just discovered the new drawstyles
deptn is very useful except it sadly ignores cutout opacity