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
Why not use nvidia-smi and judge by the wattage?
@vrba79
@3DIO
There are many ways of distributing Linux applications which essentially make them distro agnostic: Flatpaks, snaps, appimages and others. There are advantages and disadvantages for each of these methods but the downsides are mainly the larger download and installation size due to these packages containing all of the system files needed for them to run. It's not quite an accurate analogy but think of portable apps for Windows which contain the .dll, .ini, .json files et.al. that are needed for them to run; any update of Windows which changes those .dlls and others won't affect a portable app and the same is true for Linux distros. The only restriction is generally that the user must be using a Linux distro with a kernel at least as new as the distro used to create the distribution file.
There may well be one but I can't think of a reasonably modern (last 5 years or so) and somewhat mainstream Linux distro that won't run Blender natively for example. I don't think that's an issue.
We don't know if Nvidia's agreement with Daz is restricted to official Windows distributions only (there have been some well-publicised heated disagreements between Nvidia and Linux developers), we don't know if Daz is concerned about an explosion of support tickets even if they released it as an unsupported version, we don't know most things because Daz doesn't really communicate with its user base. All they've said about this is that there will be no native Linux version and, for now, I would take them at their word.
If you want Studio on Linux, and it will work on any reasonably recent distro of Linux, you can get the Windows executables for both the current 4.24.x release and the 6.x Beta running through WINE with no indepth knowledge or arcane coding tricks required. All you need to be able to do is follow instructions accurately. It takes about 15 minutes + however long it takes for DIM and Studio to download and install. Just be prepared to start learning again because you'll want more from your OS than just running Daz Studio!
@TimberWolf
Hi.
I've had similar a experience; plain vanilla WINE got DIM running well enough to install and run with only very minor annoyances related to window behavior. But without the GPU.
I haven't tried it recently, but are you saying that these days, even the GPU just works? That's stupendous news, if so...
Agreed. Just wait for the Steambox. When people discover that the "water is fine", I think it'll start a trend.
Also, I think Red Hat Enterprise Linux is already synonymous with Linux in the 3D world and the only oddball outlier I can think of that insists on Ubuntu, and a specific version and a specific GPU even is move.ai, And so most any RPM based distro can be coerced into working. And back in the day, I even got Maya running on Ubuntu without too much trouble.
@TheMysteryIsThePoint
Yep, GPUs and multi-GPUs work absolutely fine under Linux. Debian-based distros lose the ability to use the built-in denoiser for reasons I have yet to figure out, but it's related to Optix; the translation layer in WINE under Debian doesn't seem to be able to handle it properly. However, Fedora and Arch-based distros work perfectly, including the denoiser. Desktop compatibility varies from distro to distro but having spent the best part of a week installing, testing and uninstalling a wide variety of distros I would suggest using the KDE-Plasma desktop if it is available for whichever distro you prefer - I've found zero problems with it. However, Studio will work with most desktops and windows managers (Gnome, Cosmic and Cinnammon to name but a few) but you may find the odd UI glitch that wouldn't be present in KDE.
To get your GPU(s) working, you'll need a WINE version >= 10 and you'll also need to download a small additional package from Github after you've got it all up and running. To avoid filling the thread with a repeat of information, have a look through the last three or four pages - all the info and links you need are there. The Beta requires one additional tiny .dll to be downloaded and inserted into the WINE prefix as it is required by 6.x and is not part of the official WINE repository.
Give it a whirl - you'll be pleasantly surprised :)
@3DIO
If you have zero or limited experience of Linux I suggest you try out a few distros using a spare drive if you have one. It may take you a number of installations to find a distro that clicks with you and has the features you need, but there is one out there with your name on it. After you've picked one, or if you already know what distro you would like to use, pop back here with the details of the OS and desktop you've picked and I'll give you a step-by-step guide to getting it running.
It isn't possible to produce a generic guide that covers all possible combinations of distro and desktop unfortunately - the process can differ quite widely depending on what you want to install.
If you use Adobe products to any great extent you'll find that, with one or two exceptions due to their availability on Steam, none of them will install and work well under Linux (or even work at all) so do check what else you need from your OS as well.
@TimberWolf
I don't render in DAZ Studio at all, but it would be nice to run dForce. Think I'll give it a try based on your encouragement. Thanks!
@3DIO
Whilst there is nothing I know of that meets *all* of your requirements, I would recommend Nobara Linux with the KDE desktop. It's Fedora-based (so every Studio feature works), very easy to work with and is specifically geared towards content creation and gaming. Whilst you can always install anything that's missing or upgrade WINE, Nobara comes with the latest Nvidia drivers as part of the installation package and these can be a bit of a hassle in some distros. It does, however, come pre-loaded with other software and you're going to find every distro does that. Unless you decide to howl at the moon and install something like Gentoo, mainstream distros are always packaged with apps that reflect how their creators believe they will be used. Nobara comes with Steam, some streaming packages, that kind of thing but they can all be removed at a later point.
Earlier in this thread someone has written a guide to getting Daz Studio running on it. I highly recommend you don't follow it because, whilst it works, that method will probably cause them and you problems further down the line when you install other software but if you just wanted to try it out and see if it suits you, go for it, but I'd recommend then nuking the installation and starting again afterwards. We'll be using a WINE manager (Lutris) to sandbox a WINE setup so that it does not affect, and is not affected by, any additional software you want to install in the future. Best practice and all that good stuff. Seriously though, it is worth setting these things up properly in any version of Linux.
https://nobaraproject.org
https://wiki.nobaraproject.org/en/new-user-guide-general-guidelines *do have a read of this before you start as there are a couple of points worth noting.
I would suggest either the Official-NV or the KDE-NV downloads which come with basically everything ready to go. Have a read and decide which one suits you best. Or try both! Do note the disclaimer that states this distro is a 'hobby project' - Nobara is highly rated and very stable but the creators are making sure you understand that if you intend to use this OS commercially they are not liable for any losses you may incur due to issues with Nobara.
---
The only other thing I would suggest to you is to have a quick check to determine if any additional hardware beyond the usual fitted to your PC will still work. I'm talking about internal or external soundcards, wifi dongles, video capture cards etc - the categories of hardware most people don't have. Check compatibility with any printer or scanner you own as well. 99% will work natively with Fedora but it's worth making sure that you're not going to find yourself locked out of something you need before you start!
My experience is that the GPU doesn't just work. I installed Daz Studio on Commodore OS Vision and Iray works with CPU rendering but it can't see my RTX 4070S. I haven't got into the details of configuring Wine yet.
Commodore OS Vision ... first time I've heard of it! I had to do some research into this. Just to confirm, you're system is x86_64 PC with Nvidia RTX 4070S commonly available on the market, not the cool Retro Commodore 64, right? Gosh, seeing the other retro Commodore, the Commodore Ultimate 64, brought to life -- on a Xilinx FPGA -- reminded me of the old IBM PC from the early 80s.
Cheers!
Yes, it is an x86 64 bit PC with Nvidia RTX 4070S dual booted with Windows 11 Pro and Commodore OS Vision. The Commodore OS is Linux, I think it is based on Mint, with a lot of display tweaks, emulators and a load of free games for what it's creators think a modern Commodore OS might look like. I've also got The C64 made by Retro Games and both Amiga Forever and C64 Forever on Windows. I haven't looked at the Ultimate 64 but I think I have as much Commodore emulation as I need for now.
TimberWolf,
That's the morning-after hangover, right? Getting the Daz3D-Wine-Linux stack up and running is only the first steps. Learning about the Linux operating system is the next leg of the journey.
I've been asked what Linux skills and know-how a beginner should aim for. At the least: grasping the concepts of the UNIX shell (pretty much Bash these days) and its rudimentary commands; user accounts and file system organization and permissions (SUDO do's and do nots); and networks and firewalls.
It can be argued that Wine hides much of the underlying Linux complexity, but Daz relies on system components -- network and GPU -- that call for an understanding of Linux runtime libraries and device drivers. These modular pieces coordinate by means of configuration files that set requisite file paths and shell environment variables. Knowledge is a useful tool, especially when things don't play nice with one another.
Here are a couple of examples to highlight what I mean:
I remember the day, eons ago. when a visiting professor showed up with several boxes of 3.5 inch disk. It was Slackware Linux, pre-1.0, and when he laid out the installation disks the stack was as long as his forearm. He came prepared to spend the night at the computing lab to deploy Linux on a disused 386 PC. Whew! Since then, Linux has come a *very* long way.
Invariably, the more casual users adopt Linux, the more they're exposed to the tech and the homebrew-hacker culture around which Linux grew up. Not everyone needs to be a comp sci grad or know POSIX and such, but some basic level of know how and caveats are needed. Armed with that, folks moving from Windows would have a more pleasant experience working with Daz3D in Linux.
Cheers!
@3DIO
Just fire away and install it. I can't tell you how Nobara/Gnome will play with Studio because I haven't tried that combination. Gnome is Wayland-based now so it should be ok (and Gnome worked fine with other distros) but there's no way of really knowing until you try. I can guarantee that the KDE desktop has zero glitches or oddities, works well with multiple monitors, including 4K, and copes with mixed resolution setups. It performs just as well as on Windows - the choice is yours as the process of installing Studio is identical.
The pre-installed applications you don't want can be removed at some convenient point btw - there is nothing uninstallable which is more than can be said for Windows...
Anyway, all I'll assume is that you've got a functional installation with the supplied Nvidia drivers installed.
In addition, after installation you will need to download the following - just drop them into the default Download folder or wherever you prefer:
1 - The Windows executable for the Daz install manager - DIM.
2 - https://github.com/SveSop/nvidia-libs/releases/download/v1.0.1/nvidia-libs-v1.0.1.tar.xz
* Required for 4.24.x and 6.x Beta
3 - https://www.dll-files.com/icuuc.dll.html
* If you intend to install the 6.x Beta for 50xx support you will need the very last file on this page (0.61Mb) or, if you're dual booting with Win10/11, copy it from your /syswow64 directory onto your Linux drive.
Let me know what combo of distro and desktop you picked so I can grab the same version, and which version(s) of Studio you're installing, and we can get started. The OS installation is the hardest part of this!
@csaa
Happily, the days of shell commands being named after the creator's girlfriend/dog/hamster and having zero relevance to the actual function being performed are long over! I don't think Linux has even been more available to the casual user than now; stable kernels, Windows-esque UIs, YouTube channels full of very helpful and knowledgable people who actually know how to teach and not just show off their superior technical skills. If all you need is email, a browser and some office software, which I would guess covers a large percentage of PC users, you could install any modern Linux distro and never have to touch the console or understand how the OS is actually structured.
More and more applications are being released with native Linux support, hardware drivers without OEM support are built into the kernel - I could go on and on.
This is all great until you want to go off-piste a bit (like installing Daz Studio and getting it to actually work properly) or the utterly inevitable moment when the whole installation keels over for no discernible reason. All they did was run an update... It's at this point you really need some level of understanding as you describe or you're going to be spending a long evening reinstalling everything.
I think the main issue I've seen with Linux distros is people assuming that it's 'Free Windows' and works the same. My father renamed the desktop links I had set up for him on his laptop, just as you would in any version of Windows - right click, select rename, type the new name. He renamed the lot. Everything. All the Libre Office links, the Thunderbird link, the browser links. Perplexed as to why they had suddenly become white squares instead of nice icons and no longer worked, I got the phone call. I do understand this; it looks similar, it behaves similarly and yet desktop 'shortcuts' on Linux do not work remotely the same as in the MS offerings. And you cannot just rename them in some flavours of Linux - it's text editor time :)
ChatGPT and AI-based search results are the utter bane of Linux forums everywhere at the moment. 'I asked ChatGPT and it told me to do this, so with no understanding of what I was cutting and pasting, I dutifully obeyed.' You might get lucky. Probably not, though. This is perhaps the biggest problem that needs to be overcome - realigning expectations. Any version of Linux really isn't Windows in any way, shape or form but it's going to be hard for people not to bring their preconceptions with them when it all seems, initially anyway, so easy.
What I would say to anyone who is reading this thread and who doesn't fancy agentic AI being shoved into their faces by Microsoft, increasingly ridiculous minimum hardware requirements coupled with ads and data harvesting, and is thinking of switching to Linux - do it. But do your research and invest some time in learning and understanding what you are moving to. The post by csaa is a great pointer to where to start your search. It's not rocket science but it is very, very different.
OK. This info might have been useful earlier on! I'm going to guess that you'd like to at least have dForce running in Studio and this is somewhat outside my experience. I don't have any AMD hardware at home or my office but I've called a friend who has a 9060XT; I'm bringing the wine and we're going to see what we can conjure up later this evening. You'll see in the comments above that someone very experienced is having problems doing just this so I'm not hugely hopeful that this is going to be successful. Just installing Daz Studio will not be an issue but you might be left having to do everything in Blender, including cloth simulation. If you can hold on a day or so, I'll let you know what we could or couldn't do.
This will be an interesting exercise anyway because I'm sure there are plenty of people who have AMD hardware and use a Studio/Blender combination.
My Linux knowledge is way out of date, but why do you care about KDE vs GNOME?
@TimberWolf
I though Nobara dropped X11 support as of 41+, I used X11 as it played nicer with my Daz Install. Does this mean Daz works fine under wayland nowadays?
@3DIO
We failed to get the dForce kernels to compile in three Linux distros with a PC using an AMD CPU and GPU. We tried Linux Mint, Nobara and CachyOS, one from each mainstream line of Linux, all of which work very well with Nvidia hardware and Daz Studio. This means no dForce at all, not even on the CPU. Before we go any further is this a deal-breaker for you? It would be for me.
The last possibility is to try Ubuntu which is directly supported by AMD for the ROCM stack but I wouldn't hold out much hope to be honest. Just because we couldn't do it doesn't mean it's not possible of course, but unfortunately I don't have weeks and weeks to try to resolve it. You can get Studio working on an unsupported operating system OR using unsupported hardware. I'm not convinced you'll be able to do both simultaneously. When I said earlier that you could get Studio running on basically any modern Linux distro, the (unwritten) assumption was that all of it worked in Windows!
You can have Daz Studio with no dForce and no GPU rendering on Linux with your setup, unless someone else knows how to get the dForce kernels compiled with AMD hardware.
What do you want to do?
@BlueFingers
X11 is being progressively dropped by distros at this point. I haven't seen any problems with Studio and Wayland at all. Nobara/KDE is Wayland, CachyOS/KDE is Wayland, Fedora/Cosmic is Wayland - all work great. I haven't tested every combination, obviously, but I would be surprised if you ran into any major difficulties.
It doesn't support GPU passthrough only virtual GPU
Most probably wouldn't matter
DaVinci Resolve Studio nas a version for Linux
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
How To Install Davinci Resolve 20 On Linux Mint 22
Have you tried Bazzite? Mentioned frequently for gaming along with CachyOS these days. Would assume it can't be wrong for general 3D.