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
It doesn't support GPU passthrough only virtual GPU
Thanks for the heads up, Robert, but just to be clear, I can't use the GPU anyway, so would that make any difference in my case?
I'm forced to render on the CPU even on Windows.
The idea now is to install a minimal Debian/GNOME environment to act as my OS. I would install everything I use to that OS and it would serve as my only OS. The only exception being Daz Studio, which I could run from within that OS using GNOME BOXES running Windows 10. So while there's no GPU passthrough, would that even matter in my case, and wouldn't doing it that way also allow me to get around the problem TimberWolf pointed out regards the dForce compilation thing?
Daz Studio would be running in a Windows 10 environment just as it's meant to, and sure, no GPU, but we don't have that on AMD anyway, and at least GNOME BOXES allows dragging and dropping of files between the host OS and the hosted OS, so I was hoping it would just feel like it was running natively on the same OS even though Daz Studio would be running on Windows 10 inside of GNOME BOXES, inside of my main OS.
Most probably wouldn't matter
I hope you're right, cause I'm sorted if that happens to be the case. I suspect I'm going to have some fun gettng DaVinci Resolve Studio to work on that setup, but I've read that others got it working in a Debian/GNOME environment after some trial and error. What I don't understand is why there isn't a minimal download of Fedora, or I would have added GNOME to that and done it that way cause apparently DaVinci Resolve Studio prefers a Fedora base.
DaVinci Resolve Studio nas a version for Linux
Apart from Daz Studio, literally every program I use now has a native Linux installer. The trouble with DaVinci Resolve Studio is just a dependency and configuration thing, so depending on your setup, you sometimes have to dig around and see how others have gotten it installed.
That aside, I'm pleased to say I just found a whole page of minimalistic Fedora downloads. Why on earth this page is not visible from the main menu on the website I have no idea, but wow, this lot could change everything since it looks as if I could install a minimal Fedora, add GNOME and GNOME BOXES to it, and with a bit of luck it will be a case of Ta-Daa!!!
I reckon even DaVinci Resolve Studio would be easy enough to set up in that environment. Perhaps that's why they added the dependency install to Nobara.
For anyone like me who is wanting a minimal install, maybe take a look at this page (which is not shown on the menu of the website):
Downloads for FEDORA MINIMAL and Other Miscellaneous FEDORA ISOs
TimberWolf, 3DIO:
I may have something useful to contribute on that matter. Up until two weeks ago, I've been running Daz3D in Wine-Bottles on Ubuntu (Linux Mint 22) for over a year. Then I decided to replace my aging NVDIA 2070s with an AMD RX 7700 XT. After the swap, I got Daz Studio to render without iRay, but no dForce. Just this weekend, luckily, following a big Linux Mint update, I was able to get Daz Studio to recompile the dForce kernels using the OpenCL drivers for AMD.
How did it all come together and work? Here's what I've managed to figure out.
The diagram below explains the various software and hardware components that enables Daz3D in Wine (source). It may look like a lot of plumbing, but the key takeaway here is that MESA enables OpenGL rendering and OpenCL dForce simulations.
Next, referring to the second screenshot above:
[1] I use Wine (wth sys-wine runner) in Bottles installed and jailed via Flatpak.
[2] GPU Cap Viewer is a free Windows app that inspects and runs tests on the GPU. It's a great diagnostic tool to examine the rendering and compute software stack visible to Windows ... which in turn is made visible by Wine-Bottles ... allowed by Flatpak (in my case) ... and runs natively Linux. As you can see GPU App Viewer "talks" OpenGL with the AMD GPU to render scenes. It does so by means of the MESA software stack, not ROCm. Same for compute jobs (such as dForce) by means of, rusticl, a MESA OpenCL runtime library.
[3] In Daz Studio, the Simulations Settings tab confirms the availability of the AMD GPU. It identifies the MESA OpenCL system: rusticli.
[4] dForce is running, simulating gravity on the dress the G8.1F figure is wearing.
If you persevere and try to get OpenCL working to enable dForce, a reasonable goal would be getting Wine to leverage the MESA software stack. As I understand it, various Linux distros pre-bundle MESA according to varying degrees. For example, in my Linux Mint, Flatpak bundled rusticl as an extra component of Freedesktop.
/var/lib/flatpak/runtime/org.freedesktop.Platform.GL.default/x86_64/24.08/4c37b3e42ec09de553a93fe22fa3079ef784beda91aea794563284a25f3f77e2/files/lib/libRusticlOpenCL.so.1 -> libRusticlOpenCL.so.1.0.0
I never had to manually build and install MESA from source code. Later, when I installed Wine-Bottles via Flatpak, and Daz3D afterwards, Daz Studio picked up the OpenGL and OpenCL stacks automatically.
Hope this helps.
Cheers!
I got 18.6 running on Ubuntu 22.04 with absolutely no modifications. It just worked.
@TheMysteryIsThePoint
Aha! And that solved it in Fedora 43 as well with MESA 25. As I said earlier I don't have any day-to-day access to AMD hardware and so made the (incorrect) assumption that the ROCm stack was required for Gallium/MESA. It isn't. Rusticl just worked. In fact, the rocm-meta packages just added to the confusion. The default for Fedora is 6.4.something and Studio just reported no OpenCL devices available at all. OK, we thought, the 9060XT is reasonably recent and perhaps unsupported with that release, so we added the Rawhide repo and upgraded to 7.1.something. Studio then identified the GPU as an OpenCL device correctly and we thought we'd cracked it. Nope!
Well, you've probably made @3DIO 's day. Great bit of detective work and makes life for AMD users with a Studio -> Blender workflow a lot easier. Trying to get Blender's cloth simulation to play nicely with Daz assets is not something I'd wish on anybody!
TimberWolf,
Yep, never doubt TheMysteryIsThePoint. Miracle maker!
With MESA-rusticl set up properly, AMD GPU owners can run dForce then export the Daz Studio scene as an obj to Blender. From there it takes just a bit of work to get the clothing object merged into the scene.
Incidentally, deploying both MESA and ROCm in Linux doesn't cause too much problems. I believe the Linux display subsystem ignores ROCm and continues to use MESA. Thus isolated, and with the right shell environment variables configured, ROCm can be used for writing code and for runtime use by local LLMs (managed with Ollama, for example).
Cheers!
@csaa
Apologies, I got my posters jumbled there. Your explanation of the graphics stack cleared up my confusion as to why ROCm was eliciting precisely nothing useful from Studio. It's ermmm not used! Armed with this info it took myself and the last vestiges of a friend's goodwill about 10 minutes to get her 9060XT recognised and working as an OpenCL device.
I'm a Diffeormorpic fan myself as it will export the simulation data and you end up with the scene precisely as it was in Studio. It's a fantastic piece of software.
So, the state of play for Daz Studio on Linux is currently very positive I'd say. I haven't gone back further than Studio 4.21 but anything from there onwards works in virtually every modern Linux distro with full GPU rendering if you have a compatible Nvidia GPU. Debian distros lose denoising - not a big deal for most people. AMD owners can export finished simulations and scenes via Diffeo or any other method they prefer to Blender or any GPU-agnostic renderer.
I doubt Daz could be persuaded to Flatpak their software but that would be my solution to open it up to more people who want to dip their toe into Linux.
Flatpack would definitely be the way to go as it eliminates their to many distros argument
I'm just the layman type when it comes to Linux. Having an AMD system, I'd help out as best I can if I knew what I was doing. Unfortunately, my knowledge of Linux extends to knowing what a distro is and how in general a Linux system is put together. Stuff like compiling, and a whole bunch of the other stuff I see in csaa's post, that level of stuff just goes right over my head.
I agree, it's a shame that Daz don't have a Flatpak. I'm surprised though, that given the knowledge csaa, TimberWolf and no doubt countless other Linux-heads in the thread, that you don't pool your knowledge and create a distro based upon what you know to be working.
The way I see it is this: As long as there's a single, common-between-us minimalistic distro that contains the only the prerequisits required by us creative types, then people like us would take it up happily. At the end of the day, Blender, GIMP and stuff like that all have a native Linux releases anyway, and stuff like Daz Studio and DaVinci Resolve being free are considered pretty much essential to most of us as well.
So what about a minimalist distro that allows selection and installation of (at OS installation point) the following:
- Dependencies (to include most appropriate drivers) for Daz Studio on AMD
- Dependencies (to include most appropriate drivers) for Daz Studio on Nvidia
- Dependencies (to include most appropriate drivers) for DaVinci Resolve on AMD
- Dependencies (to include most appropriate drivers) for DaVinci Resolve on Nvidia
- GIMP
- Inkscape
- Blender
- Choice of web browser
So that basically, you run the installer and the first thing it asks you is whether you use AMD or Nvidia, and depending upon the selection you make, it installs the most appropriate drivers and the correct Daz Studio and DaVinci Resolve dependencies based on that selection. Then it ask you which of those first three packages you want to install. Finally, it asks for your choice of web browser. It then sets about installing and configuring stuff in the way you Linux-heads are discussing here, and the really beautiful thing is, that when you select the type of graphics card you have, the installer doesn't just install the relevant driver for their card, it also automatically installes the Daz Studio and DaVinci Resolve dependencies based upon the graphics card brand the user selected.
The result (hopefully), is that both Daz Studio and DaVinci Resolve would then install and run without fail.
And just to be clear, I don't undertand how much work would be involved in doing somthing like that. For all I know, it could be an insane amount of work or it could be fairly straight forward for someone in the know. But unless we have such a distro, then due to the nature of Linux, I don't see how it is ever going to get universally solved unless that Flatpak thing works, and even then, I'm guessing you would have to depend on Daz to do that for you, whereas as a minimalist custom, bespoke distro such as I've describe here, would be in the hands of the users, namely the Linux-Heads on here!
I just cannot help but think that with the knowledge you have between you, that pulling-off a minimalist, bespoke distro like that would be the answer to all our dreams. The stuff csaa just pointed out sounds amazing. I mean, lol, I cannot even get AMD accelration for dForce in Windows, so what he's achieved there is beyond what is even possible for us on Windows as far as I'm aware!
All of that aside, I managed to free-up my disabled drive. I actually have two physical 240GB drives in this system, but the second was always intentionally disabled, used only to store my ISOs. But what I've done is shuffle the most important off to USB sticks, wipe the drive and can now use it purely for installing Linux on, using the BIOS to diable the Windows or Linux drive at will. I got fed-up of having to re-install Windows between Linux distro tests, so this is much better, should have done it years ago!
So what I've been doing: I couldn't help but notice that further down the page on that link I gave the other day, there is something called "Fedora Everything". It should really be called "Fedora Custom" cause that's exactly what it is, and it's exactly the sort of thing I was looking for. And, unlike the Debian variant, this one actually recognises my WIFI dongle and I was able to install a minimal Fedora base with a minimal GNOME desktop. Works perfect so far, but (and this really blows my mind), there is no firewall by default. I thought the Debian and Ubuntu-based distros were bad enough in so far as they do have a firewall, but it's disabled by default.
This one, though, this Fedora/GNOME minimal setup, there is no firewall at all, so I'm currently trying to find out which is considered the defaull firewall to use for that configuration, one that actually has a GUI element to control it. Crazy stuff for sure, and I suppose there's a very good reason for it, but man, you would think that they would at least have one on there to be able to swtich it on!