Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
But I gather only the ones that the scriptwriters update to the new version?
Plug-ins absolutely require updates. Scripts may or may not work, it depends on exactly what they do and how they do it.
If it has a package for each bit architecture and operating system that it supports it is almost certainly a plug-in, if it has only cross-platform content packages then it is almost certainly not a plug-in.
Hi. Yes, just seems like a real step backwards. A bit similar to when Poser decided to gimp all their plugins (although not as bad as that). Just a shame that rather than just improving on Daz Studio 4, they essentially decide to break it for many users.
They didn't have much choice. Qt 4 is no longer supported, therefore the switch to Qt 6.
The only way they could do this is by NOT supporting NVIDIA 50xx Series RTX video cards. DS4, and by extension the scripting for DS4, is based on a cross-platform library called QT, version 4. The drivers for 50xx series cards are only compatible with QT version 6. (An entire generation of QT, version 5, was skipped.) The shame here is not getting ahead of the change in time. There was a DS5 project. It never finished. That's why DS went from DS4 to DS6. But not releasing DS6 was not an option.
The distinction between DS 5 and DS 6 is the Qt version used, so DS 5 became DS 6 rather than being an abandoned project (and DS 4 has had updates with what were essentially DS 5/6 features that didn't require the move to a new version of Qt). It wasn't just support for the new nVidia chips (up until the beginning of last year there was meant to be an Iray version that would have been integratable in DS 4, but it proved to have fatal issues and the update that fixed those did have the higher requirements) but rather that Qt 4 was, as Doctor Jellybean says, no longer supported and was a block on other things Daz wanted/needed (including Apple Silicon support, I believe).
I was just pointing out it took them so long to make DS 5 they had to change the QT version in the middle of developing. I don't know why it took them so long. I'm sure they didn't want to stay on the 15 years old QT4 as long as they did. But that doesn't change my comment about the part that cause the most pain for support of scripts and plugins is that they didn't get in front of the tech stack changes. It isn't an indictment, more of a post mortem.
Qt is an application development framework which helps you develop cross-platform application. It includes many tools and utilities, and among them a scripting engine.
The scripting engine used by Qt4 has been replaced by a new one in Qt6 which is based on a more recent standard, and there have been other evolutions in the framework (especially in parts which handle the UI).
If a script didn't use things that changed, then it will usually work as is in DS6. But a lot of them relied on features which have changed so the code needs to be updated.
Me my very self, I'm just disappointed that we're more than three months into Daz Studio 6 and they haven't patched out any of the kinks yet (I don't count Beta so don't even bother bringing that up).
The less of a workout the betas get the more kinks will not be found until the general release.
Maintaining compatibility with scripts and plug-ins would be a major part of why they didn't update.
They knew they'd have to bite that bullet eventually. Putting off just resulted in what we have now.
It didn't help that the release of DS6 was a complete surprise to the PAs. Most of them were still posting "I'll work on that when they finalize the API" and then suddenly there was the big DS6 release. Shouldn't the API have finalized before that?
SDK, not API. And no, DS 6 was inistially released as an alpha where you would not expect the SDK and API to be final. The PAs did know about DS 6 in advance, but that doesn't alter the fact that plug-in (and to a considerable extent script) developers needed to wait until the SDK was ready, which needed to wait until a wider range of users had used DS 6.
Hair splitting. I didn't say they didn't know DS 6 was under development. I meant the actual release day was a surprise. PAs were still saying they couldn't start plugins and DS 6 splashed across the Daz home page without prior warning. Most software releases get articles telling to be prepared on such and such future date.