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
I tried copying libstdc++.6.dylib before upgrade, and re-installing it after upgrading to Big Sur, but there is still a problem related to library caching.
I have retried on a Parallesl VM
Although libstdc++.6.dylib is still available, the system prevents DAZ Studio from loading it.
Me either but with a real install, that library is there but is not loading with Big Sur. I'm happy with the system is really super fast, I hope someone will find a workaround for it.
For anyone causally following this thread or getting some of the particular references, you might find this interesting...
https://www.techdirt.com/articles/20201208/13454345846/apples-failure-to-ensure-backwards-compatibility-big-sur-leaves-developers-quite-sour.shtml
DAZ isn't the only one struggling to catch up with this particular upgrade.
Means that also other companies did not do their homework.... That particular library was marked as "depricated" five(!) years ago. Keeping it that long is actually rather nice, compared with Apples usual policy. A function or package marked as depricated will be thrown out two releases later.
I sympathize with people who have problems with Big Sur. But have you thought of the huge changes Apple has in store over coming months?! "Apple Silicon" means a huge jump into computers using Apple's own chips/boards. Every software company will need to create new versions of their software to work with the new Apple computers. True. Apple will also release Rosetta, but it will likely only work for 1-2 years.
Yep. I bought a Windows (gaming) laptop the other day solely because I expect a lot of the non-Adobe CC programs I use outside of work will no longer be supported once the Apple Silicon rollout gets into full effect.
I'm starting to make the big move of doing Daz-related content over to it as well. Nice to finally have an Nvidia graphics card so I can see what the big fuss over Iray is, lmao
That is not really an issue for a developer. It is ticking an extra box in XCode. You can decide if you want Intel-only, AppleSilicon-only or combined. The combined setting is the defualt in the actual XCode. The rest is done automatically. As long as you are not directly hitting the hardware, or using 3rd party stuff, then moving from Intel to Apple Silicone is not rocket science. An average program running on Rosetta on M1 is about as fast as on an Intel i5. It is about twice as fast if run natively. Honestly,I was shocked how damn fast that thing really is, running a couple of our tools on the new Mac mini. This is not just a statement, it is a declaration of war to Intel.
One part of the problem is that supporting BigSur will break the old plug-ins for both platforms (Win+Mac), some for which the developer that is supposed to "push the button" is not amongst the living anymore, will cease to function for good.
PerttiA I'm sorry the plugin developer has died, but that is part of life. The computer world moves on. Software moves on. We get new versions, and often leave the old stuff behind. Working with computers becomes much easier when you accept those hard facts, and go with the flow.
Is any of that core functionality? It would be weird if Daz didn't have the code for anything part of the core functionality, except where they licensed it from an entity that woudn't depend on the health of a single person (like 3delight and Iray). On the other hand, Daz is a fairly small business, and small businesses don't always have the budgets for "optimal" solutions.
As the BigSur support breaks the old plug-ins for ALL users, for some that consider those plug-ins essential, they may as well be considered core functions.
Yes, plugins are an issue. That's why I have not yet upgraded my main Mac to DAZ 4.14. I am currently testing if the plugins I use still function, using a stripped down DAZ Studio on a virtual machine. Since Filament is not yet supported on Macs anyway, staying with 4.12 is not a big issue, I suppose.
Its a sad thing that some developers are no longer with us. But I am a bit shocked that DAZ does not have access to the sources. My company usually has to deposit source code we develop for our customer projects. Since it contains our intellectual property, we deposit that code with an escrow agent.
The plug ins don't belong to Daz, so they could not claim any right to them - and trying to maintain another person's code, on top of their own, would probably not be a practical option..
It's always a challenge when we get a new version of an Operating System. DAZ, like other software companies, often needs to wait till we have an official version of the OS. They need time for testing. I have at times, been frustrated with the pace of things. Sometimes I need to just sit back and relax.
I believe DAZStudio is written with QT, so I wouldn't be surpised if XCode isn't involved in the build pipeline at all. Most QT applications I've worked on were built via elaborate Makefiles or (shudder) cmake. I certainly don't envy the engineers tasked with updating DS for Big Sur, but I certainly appreciate their efforts.
I'm probably an oddball, but I setup my scenes on my macbook, lounging on my couch, and then transfer them over to my windows workstation to render overnight. That way I get to practice my hobby while still being near my family, whereas my workstation is isolated in my office away from the fam. And I definitely plan to upgrade to one of those macs rolling out in 2021. I guess what I'm saying is, godspeed Daz3D macOS dev(s), godspeed.
Well, not the most elegant way to solve it, but works with Crossover 20 and macOS Big Sur. I just installed and connected my library. Found many items I never saw before on my Mac (the same folders). Renders fast, too. Still having difficult to connect the Database, CMS not starting and trying to fix it.
I asked one of our Mac developers, and he told me that QT on a mac will only work when Xcode is installed. Nevertheless, you still can build things using makefiles or cmake... Xcode does not prevent developres from creating nonsense....
As with rendering "heavy" scenes, I had found a different solution (than buying a Windows machine with an expensive NVidia card). I am using a virtual graphics machine on the AWS elastic cloud. For $0.38 per hour (spot price, regular price is about $0.82) you can run quite a lot of renders until you end up at the price of a Titan card (the ones Amazon are using). If you are done, you shut down your virtual instance, and resume next time...
I am glad, that so many people using Apple computers like Big Sur and incoming Apple Silicon.
We use many of Apple computers at work and my role is to help users with them.
If it is only ticking an extra box in XCode to get it work on Apple Silicon,
then the future looks bright, I hope.
This used to be the case many versions ago, but since then macOS systems can install the needed utilities for QT (and many other tech stacks) without installing Xcode proper (via a utility set called xcode-select). This was a great move because Xcode has gotten gigantic, and it isn't entirely necessary unless you are building a native mac/ios app.
From checking the QT site, it looks like the QT developers are already making progress towards getting arm64 (apple silicon) compilation working for their toolchain :-D (https://bugreports.qt.io/browse/QTBUG-85279 for the curious)
RE: render farm, thats actually a great idea that I really need to look into more.
Are you guys just using the CPU to render? That is the whole reason I left Apple. Apple does not support NVIDA and Daz is built around the iray structure. Even the new Octane requires a NVIDIA card and as long as NVIDIA is a big part of DAZ they will not support other GPUs... Like Metal or AMD.
I CPU render, but Octane has a public beta supporting Metal, which allows for AMD-based rendering. They haven't said anything about Apple Silicon as far as I'm aware, but if they're supporting Metal, the transition sholdn't be too difficult. On the other hand, I have no idea if Apple will either have competitive GPUs when they roll out the next, more powerful Macs with more cores, nor if they'll have any options for 3rd party GPUs from AMD.
The OTOY twitter account announced in mid-november that full support for AS is in the works (if I recall correctly).
The current version of Octane that works on the Mac only supports iMac Pro's & Mac Pro's as it only supports a small number of AMD GPUs
I don't know all this programming lingo. I use MAC and just updated to Big Sur and Daz no longer works. I've spent hundreds of dollars on this software and now its completely useless. Can someone help me using terms I will understand? I feel so hopeless now
You may be able to roll back to your previous mac version, if possible, or in the short term (pending an update to DS) you could try using Windows via Bootcamp.
I admit to being a bit nostalgic when I hear about Big Sur and the new Macs. But I'm glad to avoid the problems owners of the new Macs are experiencing.
I think I might try Windows Via Bootcamp. I just hope it will work. I literally cannot believe I've been rendering for almost 10 hours a day for the last two months to being at a complete standstill all because of an update. They optimized the software for all of the other yearly updates, why not this one?? I cannot believe how unreliable this has become. I've spent so much money on this. This will be a total loss if I can't get it working again soon.
Check your downloads you may find that you still have Studio 4.11.0383 around. I have been using Studio 4.11.0383 with Big Sur.