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
A docker container with all required wine and cuda libs would provide a setup largely distribution independent. I requested a Linux version officially once and the base answer was "not planning to", so to make Daz Studio in wine a lasting solution one has to abstract the baseline to manageable levels.
Tried it a couple more- rolled back to Ubuntu 24.04 as is supported by the CUDA toolkit thinking the libraries between 24.04 and 25.04 were different, no dice there either.
This wound up being the issue. I didn't have the NVML libs installed correctly and missed the part about the omitted script.
On my end, under Fedora 42 KDE, the first biggest hiccup was getting dForce working because my 3070 wasn't being recognized (despite being recognized in the Render Settings portion of DS)
After searching for OpenCL for WINE, I got that sorted.
One thing I couldn't yet solve is the missing capital "I" letters on the UI. (I believe one instance of Studio I had under Lutris - or a different bottle maybe - didn't have that issue.
The one thing that is more annoying though, which I just realized a couple nights ago was the Map Transfer doesn't seem to work: If the materials are 3Delight, there seem to be errors with the texture format.
And if the materials are converted to iray (using RiversoftArt's script for example) the map transfer runs within a few seconds but doesn't really do/output anything.
The case sensitivity on some Linux file systems can be annoying too, but at least that doesn't really break things.
Ancillary question.
Has anyone been able to get Comic Life 3 to work on Linux? I can get it to work at about 85%. The problem is bold and italic don't work, and the background of the dropdown menus is invisible.
Back to NVML... Had some kind of kernel panic or serious error and I haven't been able to finagle the installation back since. After the libs are installed alongside NVML I show a CUDA (numbers) adapter with the correct GPU information, but it won't render when isolated to only use that adapter.
Switched to Mint/Cinnamon from Ubuntu 25.04 - no change.
I stuck with Bottles rather than plain vanilla Wine and after months of usage I found one likely fix to the slow loading times.
In my Bottles (51.24) setting I have two choices for the Wine compatibility layer, called Runner: sys-wine-10.0 and soda-9.0.1. All along I've used Soda, and the I/O performance leaves a lot to be desired. The CMS phase, when Daz3D starts the persistent storage and goes online to communicate with Daz server, is slow; once I load a DUF scene file, the process of reading and getting the initial render (Filatment or Cartoon Shaded) is also glacial.
By switching the Runner from Soda to Sys-Wine, this initialization steps run much faster. Updating the settings was simple; however, the switch appears to reset the Daz3D settings as, once again, I had to enter my credentials for my Daz account; the DIM directories also reset to their default. Now, evertime I load a DUF scene I've used before, I see Daz3D rebuilding its metadata, as if populating its data structures anew. The switch from Soda to Sys-Wine comes with a cost, but with the run time speed up it appears to be worth it.
I'm still evaluating the outcome of the change.
--- Update ---
That part about "Daz3D rebuilding its metadata" wan't exactly as I expected. I needed to manually kick off this step.
How did I know this was necessary? One big indicator is that the Smart Content pane displays all products grayed out, even though DIM reports separately that these have been installed. Conceptually there's a disconnect in how DIM sees the database contents and how Daz3D does; hence the need to re-sync the Daz3D content library metadata.
(This is a simplified view of things. If, as in my case, Bottles deployed Windows guest in one branch of the Linux file system -- my home directory -- and the content library files are saved to another sub directory, then the Daz3D Content Directory Manager settings need to be updated beforehand. Only then will the following metadata refresh work.)
To properly rebuild the metadata in Daz3D:
The metadata re-sync took less than two minutes for me. For good measure, i restarted Daz3D and now it sees every asset that I've installed via DIM.
Cheers!
Out of curiosity, have any of you managed to get the latest release of Bryce running on Linux?
And if so, which distro and software did you use?
Anyone else having issues after Kernel 6.16.3 with DAZ Studio and iray?
the previous couple ones (6.15.9 and 6.15.10) weren't causing issues with Studio but something with the newer Kernel or some other package that came along for the ride completely broke Iray Rendering for me.
I can do previews, I have my 3070 listed in the hardware tabs (both in the render settings and the simulation settings) but if I try to render, Studio refuses to use my GPU and attempts to render on the CPU side (meaning it never renders anything) and in the System Monitor the GPU utlization hardly goes above a single digit percentage.
Rebooting into previously working Kernels didn't work at all as the behaviour is the same.
I even tried installing DS on my other SSD with CachyOS in it which has the latest driver 580.xx and the behaviour is similar.
This is on Fedora 42 btw.
I've tried the latest release of the nvlibs (0.85?) but no luck.
Has anyone experienced something similar?
Fedora 42 is really making me miss Windows 10 right now.
I'm on Arch Linux and it's working for me.
I have both nvlibs 0.8.5 & NVML installed
Operating System: Arch Linux
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 24 × 13th Gen Intel® Core™ i7-13700K
Memory: 64 GiB of RAM (62.5 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3090 Ti
NVIDIA-SMI 580.82.09 Driver Version: 580.82.09 CUDA Version: 13.0
wine-10.14 (Staging)
I don't think GPU utilization issues are related to the kernel on Nvidia as the driver is separate from the kernel (unlike AMD)
I just recently installed it on Linux Mint and although DAZ Studio works great, I can't get it to see my gpu even after using Sven Sop's latest (https://github.com/SveSop/nvidia-libs) but it doesn't seem to work.. at least not for me. I still don't see my gpu in the render settings. I see a generic gpu that doesn't work. I double checked that I'm using the Nvidia driver.. maybe I'm using one that is too new?
I have similar problem. I've installed DAZ in Flatpak Bottles, and it kind of works, but it does not detect my GPU (I have RTX 4070 Super). Render settings only shows the CPU, which allows to render somewhat but kind of defeats the whole point. How did any of you manage to make it see the CUDA? What should I look into?
Freddy, ash.rabbi:
I have two computers and I use two Ubuntu drivatives: a Linux Mint desktop PC with an RTX 2070 super Nvidia card, and pop!_OS/System76 on an i3 laptop w/ Intel integrated graphics.
(1) When I set up my desktop for Daz, I was also intended to write CUDA code. So I followed the Nvidia instructions for installing the whole CUDA suite. This was almost a year ago, and along the way the installation process must have built the Nvidia driver from source. If you haven't compiled Linux drivers from scratch, the task can be quite involved as instructions will ask you to also update Linux system software, particularly kernel-related components the driver interacts with. Complicated but not impossible; people have been doing it for decades, and the Nvidia scripts automate the process as much is reasonable.
After setting up the Nvidia drivers on Linux Mint, I went on to set up Bottles, a Wine derivative. With that in place, deploying Windows apps such as Daz Studio, DIM, even Clip Studio Paint, went smoothly. More or less. Heh. iRay rendering was as fast as when that PC of mine ran Windows 10.
(2) Why pop!_OS from System76, a repackaged Ubuntu distro? I saw a live demo of pop!_OS and after trying it out on my i3 laptop, I was convinced that System76 had developed a UI layer that felt way ahead of Linux Mint. Apart from bespoke UI and apps, pop!_OS also bundles Nvidia drivers by default.
To quote CUDA Programming: Workflows for getting Nvidia drivers working on Linux (05/01/2025):
Some day I plan to replace Linux Mint with pop!_os my PC with the Nvidia card and rebuild my software stack accordingly.
Hope this helps.
Cheers!
csaa,
Thanks, that's a very helpful pointer. I am a bit of an old tool, so I'll probably go on using Xubuntu, but Pop!_OS sounds interesting. Maybe it has repositories that have fresher or more robust Nvidia drivers and CUDA than mainstream *buntu? Worth checking out, at any rate.
Other than that, I've downloaded the nvidia-libs 0.85 release from Sveinar Søpler's Github https://github.com/SveSop/nvidia-libs and installed it into the bottle that holds Daz. It appears to have done a bit of progress, at the very least now I have some dud CUDA listed in my rendering devices. It still doesn't work, and if I turn off the CPU rendering it doesn't render anything, but still it's something. I asked ChatGPT, and it suggested that it's because I have nvidia-driver-580, which is too fresh, and Søpler's nvidia-libs only support up to nvidia-driver-550. Is this true? And if it is, what can I do to upgrade it to support 580?
I finally got CUDA to work in DAZ under Bottles. For those who are in the same situation as me, you need to:
1. Compile Sveinar Søpler's nvidia-libs from source and install them in the bottle (you don't really need the x32 version, as DAZ doesn't use it)
2. Select new experimental version of DXVK NVAPI in the bottle's settings
3. In DLL overrides add nvcuda native, then builtin
After this everything should work.
I finally got CUDA to work in DAZ under Bottles. For those who are in the same situation as me, you need to:
1. Compile Sveinar Søpler's nvidia-libs from source and install them in the bottle (you don't really need the x32 version, as DAZ doesn't use it)
2. Select new experimental version of DXVK NVAPI in the bottle's settings
3. In DLL overrides add nvcuda native, then builtin
After this everything should work.
Heads-up for any AMD users, having the ROCm OpenCL runtime (
rocm-opencl-runtimeon Arch and similar, not sure about other distros) installed seems to cause Daz to hang at startup. Drove me nuts trying to figure out what the cause was until I tried starting from the terminal and keeping an eye on the output. If you want dForce on an AMD GPU, the mesa openCL runtime (opencl-mesa) seems to work. Obviously this is just for dForce - you're not gonna get Iray running on an AMD GPU no matter what CUDA alternative you're running.Additionally, wine (or at least, wine-staging) versions beyond 10.14 seem to cause severe flickering issues in the viewport while in Filament mode - not great if you're generally working with Filatoon. If you're encountering the same issue I'd suggest downgrading to wine-staging 10.14 and seeing if that helps.
From what I can see there's no GPU passthrough, so it's probably not gonna be a great experience.
Someone tried DAZ Studio under Zorin OS?
Are users who've installed Daz Studio on Linux OS Distros, sending install/usage/fault feedback to the Daz Studio Devs?
Needs to be much more support from software/hardware developers for Linux Distros and not just for Windows/Mac. One of the reasons holding me back from installing Linux is compatibility and ease of use of installing software.
Daz does not claim to suport Linux so theer is no point in reporting Linux-specific issues.
Well this thread is 10 years old.
So it's been a subject of conversation here for at least that long if not longer.
I'd love to see a flatpak on an official Daz repo, but at this point I'm not very hopeful anymore.
The sandboxed flatpaks can be configured to let Studio have full access to the GPU using the nvidia container toolkit and some other flatpak extensions.
I'm not real savy on the process because I've never done it, so I can only make assumptions about the time, licensing costs and time commitments.
If Daz/TAFI would do it and put a fair asking price on it I wouldn't be against paying for a linux version. They could even separate the subscription model to have linux and windows versions.Then the linux version would pay for it's own development costs.
The problem is getting past the Windows fan boys, and those that know all about Linux but have never used it, and those who haven't looked at it or used it since Cretaceous period
The moment DAZ Studio and Nvidea GPUs work flawless under Linux, is the moment Windows will become obsolete.
Blender could already replace zbrush, Gimp and Affinity can replace photoshop.
So, what else is needed, that requires a Windows desktop?
At the risk of giving away my age, my professional life pretty much tracked the rise of desktop computing, then the Internet, followed by mobile and the cloud. Looking back, these trends traced the evolution of the x86_64-Windows PC duopoly, then x86_64 in data centers, and ARM on mobile devices. (More or less, as far as the major computing platforms are concerned.) Understandably, most consumers may not be aware that Linux has pulled ahead of Windows OS. Today crucial parts of the Internet are pretty much built on it; sticking strickly to the OS kernel, Linux lies at the core of Android. Working behind the scenes, Linux hasn't been the face of computing that many consumers interact with.
In no way am I reviving the flame wars of the 90s and early 2000s. Windows is the predominant OS, thanks to tech and market dynamics. But going forward we're entering an era when computing will also be shaped by geopolitical rivarly. I'm talking about China, it's rise as a hardware and software powerhouse, and it's drive towards technological independence.
Reading the tea leaves, my guess is that China will break off from the proprietary x86_64 and Arm chips; instead it will build its own hardware architecture around open source RISC-V or the like. And the OS it fosters won't be Windows or Android or Mac; instead it will be another Linux variant. To muscle it's own consumer systems countrywide -- trending a billion and over users, by industry estimates -- it won't rely on free market, but rather on central government directive. So Linux afictionados, look to the Far East. Odds are, the future lies there.
(Personally, I'm pinning my hopes on RedOX, a newbie, another UNIX-like OS but written with Rust.)
And what does this all mean to Daz3D? Hard to say for certain. Will it eventually evolve into a cloud application, leveraging some sort of Web Assembly stack that accesses the local GPU? If so then it may become OS agnostic, from the consumer's POV, running in the web browser. But if it stays tied to desktop OS, then any rise in use of Linux -- propelled by China -- may motivate Daz3D to establish a stronger footprint there.
As of today, I'm content with the way things are. I ditched Windows more than a year ago for Ubuntu Linux variants. Thanks to generous folks in this thread, I've got Daz3D running in Bottles/Wine. I'm not agitating for anything and happy to see the future unfold in its own way.
Cheers!
Note that something is happening with Affinity - details to be announced on the 30th, but the iPad version is already free in the App store. It seems all too likely that they are going the Modo/Vue route, though it could be a more benign outcome.
Thank you for the heads up Richard.
I use Affinity Photo, and occasionally Designer.
I just visited their forums and see that they are in read-only mode and have moved all conversations to discord.
The store is gone and the main page just has a banner saying...
Creative Freedom Is Coming
Sign up to be the first to know.
True creative freedom is just around the corner.
October 30.
Can I ask, Where's some good step by step tutorials on installing DAZ Studio into Linux Mint?
n.aspros123,
I followed this video tutorial for using Bottles/Wine to get DIM and Daz3D running in Linux Mint. The video is more than a year old and I haven't gone through that process ever since. So hopefully this helps.
Cheers!