Where can I get SDK to develop tool for DAZ Studio
SasquatchIsCool
Posts: 251
We are trying to work on programming a MOCAP app for DAZ 3d but where could a programmer go about getting the SDK and files needed to develop an app for DAZ?
Post edited by Chohole on
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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
There's this in the store: https://www.daz3d.com/daz-studio-4-5-sdk
But what if you are working on 4.15 and above? Would it work? And thanks that is cool.
AFAIK that's still the SDK used with recent versions of DS, it probably was updated. I'm not a plugin developer though...
There's a subforum for SDK developers, maybe you'll find more info there: https://www.daz3d.com/forums/categories/daz-sdk-developer-discussion
Yes, if you check the change log http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log you will see that, although the SDK has been updated, 4.5 is still the minimum version. Note, however, thatw e know that the update for Big Sur compatibility on Mac is going to break the plug-in SDK on both platforms, currently expected in the middle of this year.
So none of our plugins are going to work? I don't like that Richard.
No, but Mac users with Big Sur don't like being unable to run DS at all so there's a tricky balance. we may hope that there will be a version available using the old SDK for those plug-ins which can't or won't be updated, and that most will be updated.
Yes if they could get the old SDK to ALSO work along side, or as separate edition - wait a minute, IF they put the New SDK to D/S5, then we could keep D/S4.anything running along side D/S5, right?
I do realize that yes Mac users with Big Sur need to have DS too ... I've always rather wished and sometimes said that it would be nice to be able to run TWO editions of D/S on the same computer. I still miss the edition that did the most beautiful job of fitting clothing TO the figure [sort of a shrinkwrap deal] - but no, that had to "be fixed" in the updates because ... and we never had an option provided - maybe it's not possible - to select for a shrink wrap fit. I used it for making clothing because we could. Can't use Hexagon for a shrinkwrap ;-) Maybe they could put shrink wrap fit back into D/S5 as well. And I sure hope they keep D/S free. Thank you :-)
That would be a way to do it, yes - I've absolutely no idea whether they will, however.
Well, you can run beta and general release alongside each other.
True. I don't often load a beta but this might be a good one to try. I have purchased some plugins which I would hate to lose.
@Catherine3678ab For plugins that are still "active" in some sense, migrating from Qt4.x to 5 in most cases will be trivial and fixes will quickly follow. The problem is the older ones, but perhaps an offsetting benefit is that we should get an updated SDK v5 in the bargain that will spark a lot of innovation.
There are some complications when it comes to getting old plugins updated [like they're from lost accounts] however yes, innovations could certainly be more beneficial, like moving from the horse and buggy days to super sonic jets! Think I might be able to hold off updating D/S until I can get a new computer hopefully next year. Looks like nVidia and others are also making changes so I've gathered from other posts, waiting 'til next year when matters have settled down could be good all around.
How do you know this?
If you're asking with respect to Qt, it's because I've done it many times. Ubuntu, for example, has not even included Qt 4.x since 20.04, I think. If you want 4.x, you have to add an unsupported PPA (which most people are rightfully not going to want to do) or compile the open source everywhere version, which didn't even compile for me with gcc 9.3.0.
If you're asking about the SDK, I of course can't know for certain, but the reason I've always heard is that it hasn't been upgraded because it'll break binary compatibility. Well, binary compatibility will be broken anyway, so why wouldn't Daz upgrade it now? And let's be blunt; what Daz calls an "SDK" is just a set of header files, libraries you can get from other places or are part of the install, and some sample code, not all of which works. I see know reason why Daz would not. Do you?
DAZ does not have the right to update plugins that are not theirs, and when the creator of the plugin has passed away, it will not be updated (Gen X).
Of course. This is indeed what I meant by "For plugins that are still 'active' in some sense" The plugin developers who are still alive have an incentive to perform the probably trivial update. For example, I develop Sagan's GUI on Ubuntu, only building on Win32 to test actual functionality. Ubuntu doesn't even supply a PPA for Qt4 anymore, but I had the GUI part running Qt5 again over my lunch hour, and this typing with a Jersey Mike's sub in one hand :) Some will get left behind, but if the SDK is updated, I think the new cool stuff we get will outweigh what we lose. Of course, this from a person who doesn't really depend on any such plugins and can afford to have a cavalier attitude about it. I can totally empathize with the people who do.
The DS SDK provides pretty deep access to the code 9after all, if you look at the install footprint or help>About Installed Plug Ins a lot of basic finctionallity comes from plug ins). There is far from a guarantee that the cumulative changes since 4.5, or any additional changes incorporated since they are having to break compatibility anyway, will allow a simple recompile without adjustments. It is not necessarily equivalent to reompiling an unchanged code base for a new version of Qt.
You raise a good point that I should have considered, too: DS5 will certainly be more than just 4.15 for Qt5 :)
I really, REALLY hope that the SDK is timely and well documented, this time. Certain things give me hope that it'll be different this time.