Daz Studio and Linux

barry_white77 · January 6

Nathanomir/Kitsumo, thanks for the input. Google ai search suggested Ubuntu with an KDE desktop and x11 is the best approach. I have been playing with MX xfce and really like it, however as a noob to Linux I would like an easy(ish) transition from w10. It is apparent with Linux there is a certain amount of trying out to see what works/feels right for any given user and hardware combo. As with many others, Daz is the only program I have need to use Windows for. Annoying.

brainmuffin · January 6

Kitsumo said:

Nyzerion said:

I'm kinda new here and I wanted to switch to linux because I'm sick and tired of windows, is the software stable enough and with all features to consider switching ?

Nope. Never will be. No reason not to try. Come on in. We don't bite.

The software is stable, but we users aren't...

Nyzerion · January 6

Kitsumo said:

Nyzerion said:

I'm kinda new here and I wanted to switch to linux because I'm sick and tired of windows, is the software stable enough and with all features to consider switching ?

Nope. Never will be. No reason not to try. Come on in. We don't bite.

I'm doing a game atm on daz3d and I freaking love linux from what I tried already but if I can't use daz it's gonna be painful

PixelPie · January 6

greywolf said:

GafftheHorse said:

It's unfortunate, but Linux Daz users don't hang out here, and don't come here except when they are having problems.

I think this thread is about to get some more activity. Windows 11's process scheduler absolutely blows chunks -- when I'm doing a render, the machine becomes 100% unusable otherwise to the point where I have to wait for the render to finish, because the mouse doesn't move and it doesn't register my ESC to cancel a render. Windows 10 was slow but I could still use a web browser (and a couple xterms (cygwin)) while a render was running with no true difficulty. Given that Windows 12 -- whenever it gets here -- will 100% mandate a microsoft login and not honour any local accounts (and all that entails), I'm not thrilled about the prospect on staying on Windows, but in order to get away from Windows, I need to run Daz3d somewhere else (and I've already bought hardware so I don't want to pay for a Mac that behaves in the same insidious data-mining way that Windows does).

I'd LIKE to run this on WINE/NetBSD but saw mention of OpenCL / Vulkan drivers which never seem to get ports to anything except Linux (<seethe>). So, Linux it is. I'm hanging around to see how nicely I can get this to play once I have some time to fiddle about with it.

Given there WILL BE a large chunk of the tech population that will walk away from Windows, I do wish (while fully realising that there are three chances of it happening: slim, fat, and none) that there would be some consideration of building a Linux native version of Daz (also fully realising that it would have to be built to work on Debian-based and Dead-Rat-based systems; I'd be happy about a Debian one)...

I am with you here, have purchased a set up for linux as windows 11 has too many deal breakers built in for me ("phones home", TPM, heavy telemetry, resource hog.. too long to list). I spend more time fiddling with windows issues than enjoying art creation. I wouldn't be surprised if they start an OS subscription model . So in 2026 I am switching. I also learned of a linux app called "bottles" that has piqued my interest... and there appears to be success running DAZ under it.. here is what AI chat said:

"Bottles is an open-source application designed to make it easier to run Windows software on Linux by creating isolated environments (called "bottles") for each app, managing dependencies, and handling configurations. It acts as a user-friendly frontend and manager for Wine, simplifying the process of setting up and running Windows programs without needing to manually tweak Wine prefixes or runners; it's very much like Wine—Bottles relies on Wine (or compatible runners like Proton) under the hood to provide the compatibility layer that translates Windows API calls to Linux ones, but it adds layers of organization, dependency management, and containerization to keep things cleaner and more isolated from your main system."

I wonder if anyone has successfully run Bryce through any of these on linux

brainmuffin · January 6

I've had quite the success going back to Lutris to do the installs. Even have the simulation running, as long as the NVidia drivers behave. Using latest Linux Mint.

Robert Freise · January 6

Has anyone tried this Proxmox

https://www.proxmox.com/en/products/proxmox-virtual-environment/overview

Nyzerion · January 6

Tonight gonna be the night I'm gonna give a go but gonna be pretty hard since I have 0 experience on linux apart from setting up sudo password on my steam deck

n.aspros123 · January 8

Richard Haseltine said:

n.aspros123 said:

Are users who've installed Daz Studio on Linux OS Distros, sending install/usage/fault feedback to the Daz Studio Devs?

Daz does not claim to suport Linux so theer is no point in reporting Linux-specific issues.

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.

The Daz Devs should really consider coding Daz and its plugins for native Linux compatibility while AI Microslop is pushing more PC users to Linux. Nvidia are being a pain with not allowing Linux Devs access to their drivers base and important coding, so they can create drivers for Linux.

brainmuffin · January 8

Nyzerion said:

Tonight gonna be the night I'm gonna give a go but gonna be pretty hard since I have 0 experience on linux apart from setting up sudo password on my steam deck

This is quite close to the process I used:

Silent Winter · January 9

Anyone tried Studio with Heroic Game Launcher?

I've been on Linux Mint for several months, dual-booting and only going back to Win-10 for Studio. Recently I found Heroic Game Launcher as a simple way to make Windows games work on Linux (it connects with gog/Steam/Epic account or just the offline installers, or just adds an already installed game from the Windows partition). It uses Wine+Proton from Steam. It works on a lot more than just games though.

Anyhoo, for a gamble, I just tried adding my Studio install from my Windows partition. It loads up fine (doesn't have my layout or directories done so I guess the config file or whatever didn't come over). Once I added one of my content directories, it loaded content just fine (first one took a while too long but after that it seems okay - it's loading from an HDD though, not an SSD, which I'll migrate to later). It also renders, but only from CPU at the moment (it recognises the GPU in settings, just won't use it if I set it to GPU rendering).

TheMysteryIsThePoint · January 9

n.aspros123 said:

Richard Haseltine said:

n.aspros123 said:

Are users who've installed Daz Studio on Linux OS Distros, sending install/usage/fault feedback to the Daz Studio Devs?

Daz does not claim to suport Linux so theer is no point in reporting Linux-specific issues.

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.

The Daz Devs should really consider coding Daz and its plugins for native Linux compatibility while AI Microslop is pushing more PC users to Linux. Nvidia are being a pain with not allowing Linux Devs access to their drivers base and important coding, so they can create drivers for Linux.

In response to Linus quite literally giving them The Finger, NVidia open sourced their driver. It's available under the MIT license.

Since you didn't know that, you should make sure you're running it and not the nouveau driver, i.e. "lsmod | grep nouveau" should return nothing and "lsmod | grep nvidia" should return a few things.

If you have a 50 series card, you must use the MIT license version (the NVidia driver package will give you the choice), otherwise you can install the proprietary version.

Robert Freise · January 9

Once again DAZ really should do a Linux version especially given the fact that Nvidia supports Iray in Linux

NVIDIA Iray has robust support for Linux, offering a C++ API for integration into applications and running server/distributed rendering on Linux, requiring compatible NVIDIA drivers (like R510 U6 or newer for certain features) and supporting modern Linux kernels (4.15+ for open modules) for efficient GPU utilization. The solution provides a comprehensive SDK and server for design visualization on Windows and Linux, allowing for both standalone and networked rendering setups.

csaa · January 12

The December 2025 Steam hardware and software survey came out - https://store.steampowered.com/hwsurvey/Steam-Hardware-Software-Survey-Welcome-to-Steam - Given that video gamers and 3D enthusiasts easily overlap, there's a good chance the data is representative of the overall Daz3D user base as well.

According to the survey, Windows in its various versions still tops the reported OS, but it did decline while OSX and Linux gained respectively. The tabulation also shows NVIDIA, collectively, as the GPU leader. Interestingly, English is the predominant language (of the installed OS?), but given how many people speak more than one language in addition to English, I'm inclined to take that with a grain of salt. The second predominant language -- Simplified Chinese, the sort widely used in mainland China.

Separately, here's a report on the November 2025 Steam survey.

Cheers!

Wallytheartist · January 16

It's interesting that I find there are users working on this type of Linux integration. Testing wine seems good so far. I'm surprised it works with NPU-type graphics. Will be testing the render engine and creation of a new regine engine for research purposes into another development, and fixing up the path issues with the Daz to Blender. The first fix requires many changes and new scripts to make it work alongside extracting it directly into the Blender folder. Will try to update anyone working in a similar context.

TimberWolf · January 17

Getting Studio 4.x to work in Debian or Fedora based distros is very straightforward. I'm not sure about Arch because I've never used it, but the kind of person who picks Arch could probably code the solution to any problems they face themselves!

I suspect the main reason people are having issues with GPU rendering in Studio on Linux is the Nvidia libs requirement of a WINE version >=10. Most distros come with older versions which are stable and proven but incompatible with that library. You can either install a system-wide WINE version from the wine hq repositories (not really recommended) or add WINE 10.x or 11.x to Lutris or Bottles using Proton-QT. I'm also wondering if folks are installing the Nvidia libraries in the correct place (i.e. inside the WINE prefix) - most of the guides I've seen gloss over or ignore this. It's obvious to anyone who understands what's going on but someone just dipping a toe into the water to see if it's for them could easily make a mistake. Linux in general is not that forgiving of mistakes during the setup process. Once it's up and running, though, it's far more stable than Windows in my opinion.

If all of the above is a mystery and you would like a step-by-step guide to doing it, let me know. It genuinely isn't difficult but producing an illustrated PDF would take up a day so if there's not much interest I can easily find something else to do! If you like the look of Debian distros, I'd recommend Pop! - it just works out of the box and Windows users can hit the ground running albeit still needing a Wine upgrade; if you're a Fedora person, Nobara also just works and it comes shipped with WINE 11. Both of these automate the installation of the correct Nvidia drivers which is one less thing to go wrong - it's not quite as simple as in Windows. However, any distro you like the look of will most likely work.

I still can't get 2025 to work in Linux, sadly, so if all you have is a 5xxx you're staying with Windows or learning Blender if you really want to shift to Linux.

Silent Winter · January 17

TimberWolf said:

If all of the above is a mystery and you would like a step-by-step guide to doing it, let me know. It genuinely isn't difficult but producing an illustrated PDF would take up a day so if there's not much interest I can easily find something else to do!

I'd definitely be interested in this. I might be able to muddle through it myself with what you've said, but the putting of the nvidia files into the Wine prefix would have me going "Where exactly?"

TimberWolf · January 21

@Silent Winter

I've started on this for Mint/Ubuntu (Debian), Nobara (Fedora) and CachyOS (Arch). The problem is knowing what level to pitch it at so it's a work-in-progress at the moment.

In the meantime, could you open up a terminal and type:

wine --version

Let me know what it says. If it says wine is not installed, that makes life easier. If it reports wine 9.0 or earlier you'll need to uninstall it and how you do that will depend on how you installed it in the first place. The aim is to get Wine 11.0 on your system and I don't think the Wine HQ repositories will play that nicely with any existing installation so if there is one it probably needs to be removed.

--

A wine prefix is a root directory which contains all of the Windows files WINE needs, as well as your Windows application. It is sandboxed so it doesn't interfere with any other Wine applications but that also means that Studio can't see outside it unless you specifically allow it to. If you symlink the Nvidia Cuda libraries outside the sandbox (WINE prefix) then, depending on the distro, they might not be visible to Studio although I think you might get away with it in Mint using system Wine and system Lutris. Still good practice to chuck them in with the program they are meant for.

In the meantime, if you want to grab the Daz executable package from your store account (it's much quicker than using DIM) and the Cuda libraries from Github and have them ready, it'll take you about 10 mins to go from nothing to everything working in Mint. Attached is 4.24.0.3 running in Mint 22.3.

Silent Winter · January 22

My Wine version is showing: wine-9.0 (Ubuntu 9.0~repack-4build3).

Uninstalling and installing a later version is easy enough (Edit: I did so and now have Wine-11.0 showing). The confusing part for me is that I run the applications (mostly games but a couple of others, including DS) through Heroic Game Launcher, which is using 'GE-Proton-Latest' (with 'GE-Proton10-28 showing as the latest version).

I'll give what you've said above a go and see how I get on. Thanks :)

---

Well, the updating of Wine was easy. The install of CUDA ran into errors. At first it was a driver conflict. I was able to remove the old driver and run the install, but then it failed and the log just says "Install of 590.48.01 failed, quitting". The latest 'normal' NVidia driver I'm running is 580 (assuiming that's what it is).

TimberWolf · January 22

Assuming that your drivers are the Nvidia Open drivers (the Cuda libs won't work with the closed proprietary ones) then all you need to do is follow these two videos. Just following these guides without updating WINE will cause Studio to fail to find your GPU(s) but you've fixed that and I think that's what's caused problems for people earlier in this thread. The 580 drivers will work.

The creator of these videos uses DIM but I highly recommend using the downloadable executable to install Studio and the CMS in one operation into a wine prefix using Lutris. You can then change the target executable in that prefix to point to Daz Studio rather than the installer and check that the runner is Wine 11 - it may have defaulted to the GE Wine 8 runner which is fine for the installer but not for Studio.

korb · January 24

Joltrast said:

korb said:

Well, it took me considerably more than "a few days" - more like a few months. I had a hot project that I needed to wrap up before I could risk screwing things up. Anyways...I have validated this approach, and it works!

I'll summarize here for anyone that wants to try to replicate this configuration.

First off, my configuration:

OS: Linux Mint 21 Cinnamon

CPU: Intel Core i9

RAM: 128GB

Storage: 7TB nVME M.2 drives

GPU: nVidia GeForce RTX 4080 w/ 16GB VRAM

nVidia driver version: 550.120
</snip>

I understood about half of that. I'll have to read it again!
Thank you for taking the time to write it all out. It really is appreciated to a returning Linux user who has only really "dabbled" for the last 15+ years on and off! Having to relearn it all again!

I have DIM, Daz and my assets installed. I think I'm using just regular WINE, but I'll have to check exactly what I've got (WINE do not show up in the application list, but it's definitely there!) The only thing left on my "to do" list that I can see is getting my GPU to show up in render settings. Othen than that, it's working. A little teperamental, but honestly Windows can have it's moments with Daz too, so I don't think either OS is better than the other! LOL

EDIT: Not sure how to run WINEPREFIX to create a case sensitive directory, but it sounds like that's necessary for both DAZ and Nvidia to play nicely?

$ wine --version
wine-10.7 (Staging)

$ zpool list
Command 'zpool' not found, but can be installed with:
sudo apt install zfsutils-linux # version 2.2.2-0ubuntu9.1, or
sudo apt install zfs-fuse # version 0.7.0-25

Sorry, I've not scanned through this thread in quite a while. I'm glad you found my document helpful. I've been using Unix since the mid-1980s, though I consider myself a Linux intermediate user, at best.

Anyway, I had hoped I would find something like what I wrote when I first decided to try to get Daz working on Linux, since I bailed on Windoze 10+ years ago. Not finding anything of the like, I figured it was my duty to the community to share my own (albeit limited) experience.

The Mint team made a disappointing decision when they went from 21 to 22 in that they removed the ZFS support from the installer. Not from the OS - I have a machine that I upgraded from 21 to 22 and ZFS still works fine. But they said there was "little interest" or something like that. That's disappointing to me as I've been using ZFS for almost 20 years, and it is by far the best filesystem I have used.

Anyway, if you still have questions about what I wrote, I'll do my best to respond, though I cannot guarantee that what worked for me will work for everyone. My document should just be viewed as a starting point - there is no substitute for trial an error to make things work the way you need them to.

korb · January 24

Robert Freise said:

Has anyone tried this Proxmox

https://www.proxmox.com/en/products/proxmox-virtual-environment/overview

For running Daz, you mean? It's a hypervisor, like VMWare ESXi, or Oracle VirtualBox. So yeah, I guess technically you could run Daz in Proxmox after creating a virtual machine, installing Windoze on it, and then Daz...but why?

I have servers that are VMs running under VMWare ESXi, but since Broadcom bought VMWare and set out to destroy the product, I've been looking at moving to proxmox but haven't yet had the time to play with it.

FWIW.

Nathanomir · January 25

I goofed around and accidentally found a fix for the "DAZ Studio does not run on elevated permissions" error in Linux.

Change the runner.

Mine in Lutris was set to default. Changing it to the current Wine Staging runner solved it.

So simple. So obvious, it's easy to overlook.

BlueFingers · January 25

Hi folks it's been a long time,

I am running Daz Studio 4.22 on Tuxedo OS (an Ubuntu derivative KDE Plasma) via Bottles (Flatpak). Under no circumstances will I return to Windows so I better make this work.

While Daz Studio launches, the RTX 3080 is missing from Render Settings > Advanced (only CPU is visible). Additionally, the viewport is frequently jumbled with echos of the desktop unless I kill the KDE compositor. I have spent significant time troubleshooting the sandbox environment. Here is the current state:

Technical Errors:

Sandbox Isolation: The nvidia-libs bridge seems to fail because the Flatpak cannot see host libraries.
Symlink Issues: Manual symlinking of nvcuda.dll to internal Flatpak paths has not resolved the CUDA detection.
Terminal Logs:
- X Error of failed request: BadMatch (invalid parameter attributes) Major opcode: 156 (NV-GLX)
- INFO:root:Config file ... not found, skipping load (Bottles is ignoring bottle.yml).
- 0024:err:ole:marshal_object Failed to create an IRpcStubBuffer

System Diagnostic Output:

--- SYSTEM REPORT ---
No LSB modules are available.
Description: TUXEDO OS
6.14.0-119037-tuxedo
--- GPU & DRIVER ---
name, driver_version, memory.total [MiB]
NVIDIA GeForce RTX 3080 Laptop GPU, 580.95.05, 16384 MiB
--- FLATPAK NVIDIA RUNTIME ---
nvidia-580-95-05 org.freedesktop.Platform.GL.nvidia-580-95-05 1.4 system
nvidia-580-95-05 org.freedesktop.Platform.GL32.nvidia-580-95-05 1.4 system
Nvidia VAAPI driver org.freedesktop.Platform.VAAPI.nvidia 25.08 system
--- CUDA CHECK ---
lrwxrwxrwx 1 root root 20 okt 1 08:57 /usr/lib/x86_64-linux-gnu/libcuda.so.1 -> libcuda.so.580.95.05

Questions for you guys:

Driver Regression? Has anyone seen the BadMatch Opcode 156 specifically with the 580.95 driver?
Flatpak vs. CUDA: Is there a known trick to make the Iray worker process "see" the nvcuda.dll bridge when Bottles is failing to load its own configuration files?
Viewport Fix: Is there a way to stabilize the OpenGL viewport on KDE without the Alt+Shift+F12 workaround?

I am wondering whether I should abandon the Flatpak/Bottles approach entirely for a native Wine setup to get CUDA support back.

TimberWolf · January 25

@BlueFingers

I have never, ever got Studio working with GPU detection in Bottles. Doesn't mean it can't be done of course but I banged my head against that brick wall long enough and switched to Lutris. As long as you've got Wine >=10 in your prefix and the nvidia-libs inside the prefix and correctly symlinked it should just work. Proton-QT will allow you to add pretty much any runner you want in Lutris as it does in Bottles.

To your questions:

1. It's a vague driver incompatibility error. You should be able to grab the 590-open drivers if you still run into it in Lutris but I suspect you won't.

2. Lutris :)

3. Lutris - make sure DXVK is enabled (I think it is by default) and the OpenGL calls will be converted to Vulkan. End of problems.

If that doesn't work for you then system WINE definitely will. I found Bottles, CUDA and Daz Studio just don't get on with each other...

BlueFingers · January 25

Thanks!! I was going crazy trying to get bottles to work, I am going to try out Lutris!

PhthaloBlue · January 25

TimberWolf said:

If all of the above is a mystery and you would like a step-by-step guide to doing it, let me know. It genuinely isn't difficult but producing an illustrated PDF would take up a day so if there's not much interest I can easily find something else to do.

I would definitely be interested in a step-by-step guide, as well.

TimberWolf · January 26

@BlueFingers

The only thing to note is that that the Nvidia denoiser does not work in Mint 22 and, by extension, I'm not sure if it will be working with your distro either. It wouldn't be a deal-breaker for me - you can run Intel's Open-Denoise on the finished image or use the noise degrain filter - but for some people it might be. It's an issue with Optix and I never managed to track it down although I didn't try too hard. I use Nobara, which is Fedora-based with KDE Plasma and it just works.

@PhthaloBlue

Are you interested in any particular Linux distro or would a Linux Mint one work for you? The reason I ask is that there are some distros that need a very specific and quite different way of installing all the requirements. Staying with a mainstream distro such as Mint or an Ubuntu variant is the way to go for people new to Linux in my opinion, rather than going off-piste with something obscure. Ubuntu plus offspring and Mint are close enough in terms of the process that I could probably combine the two into one guide.

korb · January 26

korb said:

korb said:

...and I will reply to myself one more time - I can have the best of both worlds, according to this reddit post:

https://www.reddit.com/r/linux_gaming/comments/uswuv6/how_to_set_folder_as_caseinsenstive_with_btrfs/

About ten replies in I found this gem:

Use ZFS. It lets you create case insensitive filesystems from pools by doing zfs create casesensitivity=insensitive $pool/$fs.

So I'll try my new 4.22 installation on a new WINE C drive and also put the entire installation in a zfs filesystem with case insensitivity enabled. It may take me a few days to find the time to work on this, but if/when I do and can confirm, I will reply to this and let you all know how I fared.

Well, it took me considerably more than "a few days" - more like a few months. I had a hot project that I needed to wrap up before I could risk screwing things up. Anyways...I have validated this approach, and it works!

I'll summarize here for anyone that wants to try to replicate this configuration.

First off, my configuration:

OS: Linux Mint 21 Cinnamon

CPU: Intel Core i9

RAM: 128GB

Storage: 7TB nVME M.2 drives

GPU: nVidia GeForce RTX 4080 w/ 16GB VRAM

nVidia driver version: 550.120

Probably the only important part of that is the OS & GPU/driver info, but I wanted to be up front. I suspect this will work on newer systems than mine (about a 2-year-old build) as well as older. Note that this post assumes you have already configured ZFS on your system. Not all distros include (or even support) ZFS, but anything that forked from Ubuntu should have it (like Mint).

One caveat up front: I did not do a clean install of Mint, so I cannot tell you exactly which packages I installed to get this working. I will share what I feel is pertinent, but you will need to know enough about Linux to discover and install any missing packages as you move ahead on this. Installing & configuring Linux is beyond the scope of this post.

NOTE: There are many commands run at the Linux command line in this post. Lines that start with "#" are run as root (or sudo root). Lines that start with "$" are run as a non-privileged user - in my case, as "korb".

Setting Up Your New WINEPREFIX and Installing DAZ 3D Studio

Since NTFS is a case-insensitive filesystem (that is, files name "abcd", "Abcd", and ABCD" are all the same file), we need to create our WINE instance in a similar filesystem. While NTFS filesystems can be used on Linux, ZFS is a far more advanced and capable filesystem, and in fact, does support creating a filesystem with case-insensitivity enabled.

# zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT bpool 1.88G 443M 1.44G - - 7% 23% 1.00x ONLINE - rpool 5.44T 1.80T 3.63T - - 4% 33% 1.00x ONLINE - # zfs create -o casesensitivity=insensitive -o mountpoint=/daz rpool/daz2025 # df -h /daz Filesystem Size Used Avail Use% Mounted on rpool/daz2025 3.6T 128K 3.6T 1% /daz

Once the filesystem is created, we can validate that it works as expected. First, demonstrate a filesystem that is not case-insensitive:

$ echo "This is a test of ZFS case insensitivity." > /tmp/README.txt $ cat /tmp/README.txt /tmp/readme.txt /tmp/Readme.txt This is a test of ZFS case insensitivity. cat: /tmp/readme.txt: No such file or directory cat: /tmp/Readme.txt: No such file or directory

In our new case-insensitive filesystem, however, it works as desired:

$ echo "This is a test of ZFS case insensitivity." > /daz/README.txt $ cat /daz/README.txt /daz/readme.txt /daz/Readme.txt This is a test of ZFS case insensitivity. This is a test of ZFS case insensitivity. This is a test of ZFS case insensitivity.

Now that we have our target filesystem, we need to create a WINE installation within this new filesystem where we will subsequently install Daz Studio. This installation is on Linux Mint 21 using wine 10.0-rc3 (Staging).

$ which wine /usr/bin/wine $ wine --version wine-10.0-rc3 (Staging)

To get the wine installation placed in our new ZFS filesystem, we have to supply a WINEPREFIX that will reside within that filesystem. I will just create an entirely new WINEPREFIX within my new /daz filesystem: /daz/.wine

Get the latest nvidia-libs from github: https://github.com/SveSop/nvidia-libs/releases

Unpack the nvlibs into /opt. I do this as my non-privileged user by using sudo to grant myself the needed permission, though you could unpack it using sudo and let root own the files.

$ tar -xvJf /ptmp/downloads/nvidia-libs-0.8.1.tar.xz nvidia-libs-0.8.1/ nvidia-libs-0.8.1/version nvidia-libs-0.8.1/x64/ nvidia-libs-0.8.1/x64/nvcuvid.dll nvidia-libs-0.8.1/x64/nvencodeapi64.dll nvidia-libs-0.8.1/x64/wine/ nvidia-libs-0.8.1/x64/wine/x86_64-unix/ nvidia-libs-0.8.1/x64/wine/x86_64-unix/nvml.so nvidia-libs-0.8.1/x64/wine/x86_64-windows/ nvidia-libs-0.8.1/x64/wine/x86_64-windows/nvml.dll nvidia-libs-0.8.1/x64/nvapi64.dll nvidia-libs-0.8.1/x64/nvoptix.dll nvidia-libs-0.8.1/x64/nvcuda.dll nvidia-libs-0.8.1/x64/nvofapi64.dll nvidia-libs-0.8.1/Readme_nvml.txt nvidia-libs-0.8.1/proton_setup.sh nvidia-libs-0.8.1/bottles_setup.sh nvidia-libs-0.8.1/bin/ nvidia-libs-0.8.1/bin/nvapi64-tests.exe nvidia-libs-0.8.1/package-release.sh nvidia-libs-0.8.1/x32/ nvidia-libs-0.8.1/x32/nvcuvid.dll nvidia-libs-0.8.1/x32/nvapi.dll nvidia-libs-0.8.1/x32/nvcuda.dll nvidia-libs-0.8.1/x32/nvencodeapi.dll nvidia-libs-0.8.1/setup_nvlibs.sh nvidia-libs-0.8.1/nvml_setup.sh

I like having a symlink to the actual version with a more generic name so I can upgrade later and simply update the symlink to use the newer version:

$ ln -s nvidia-libs-0.8.1 nvidia-libs

Run the nvlibs setup using the new WINEPREFIX:

$ WINEPREFIX="/daz/.wine" ./setup_nvlibs.sh install WINEPREFIX does not point to an existing wine installation. Proceeding will create a new one in /daz/.wine Continue? (Y/N) y wine: created the configuration directory '/daz/.wine' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 002c:fixme:winediag:loader_init wine-staging 10.0-rc3 is a testing version containing experimental patches. 002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 004c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0054:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0054:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 0054:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 0054:err:ole:apartment_get_local_server_stream Failed: 0x80004002 0054:err:ole:start_rpcss Failed to open RpcSs service 004c:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 004c:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 004c:err:ole:apartment_get_local_server_stream Failed: 0x80004002 0080:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\win32k.sys" 0080:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgkrnl.sys" 0080:err:ntoskrnl:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgmms1.sys" 00a0:fixme:file:NtLockFile I/O completion on lock not implemented yet 00a0:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 00a8:fixme:file:NtLockFile I/O completion on lock not implemented yet 00a8:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 00a8:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5) 00a8:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5) 00a0:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1) 00a0:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1) 0110:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet 002c:err:setupapi:do_file_copyW Unsupported style(s) 0x10 002c:err:setupapi:do_file_copyW Unsupported style(s) 0x10 0134:err:setupapi:do_file_copyW Unsupported style(s) 0x10 0134:err:setupapi:do_file_copyW Unsupported style(s) 0x10 002c:err:setupapi:do_file_copyW Unsupported style(s) 0x10 [1/4] nvcuda : Creating DLL override... Creating symlink to nvcuda.dll... [2/4] nvcuvid : Creating DLL override... Creating symlink to nvcuvid.dll... [3/4] nvencodeapi : Creating DLL override... Creating symlink to nvencodeapi.dll... [4/4] nvapi : Creating DLL override... Creating symlink to nvapi.dll... [1/6] 64 bit nvcuda : Creating DLL override... Creating symlink to nvcuda.dll... [2/6] 64 bit nvoptix : Creating DLL override... Creating symlink to nvoptix.dll... [3/6] 64 bit nvcuvid : Creating DLL override... Creating symlink to nvcuvid.dll... [4/6] 64 bit nvencodeapi64 : Creating DLL override... Creating symlink to nvencodeapi64.dll... [5/6] 64 bit nvapi64 : Creating DLL override... Creating symlink to nvapi64.dll... [6/6] 64 bit nvofapi64 : Creating DLL override... Creating symlink to nvofapi64.dll... Symlinks created in /daz/.wine. Do NOT remove this source folder! OBS! NVML is NOT enabled by default. See Readme_nvml.txt for info or run nvml_setup.sh You need to REMOVE old overrides if older version of nvml have been used in /daz/.wine

Configure your new WINEPREFIX to your liking. I personally like to emulate a virtual Windows desktop when I use Daz, as I find it is much less intrusive (I use "Focus follows mouse" mode, and Windows apps such as Daz routinely steal focus when not run in virtual desktop mode). The other life hack for me is the "Screen resolution" setting. I have seen multiple posts in this thread asking how to change the size of the text in Daz, but it is not possible. However, you can make everything larger, including the text, by increasing this setting from the default. I use 144dpi to get a more usable appearance for my old eyes.

$ export WINEPREFIX="/daz/.wine"
$ winecfg WINEPREFIX="/daz/.wine" 002c:fixme:winediag:loader_init wine-staging 10.0-rc3 is a testing version containing experimental patches. 002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org.

NOTE: Once you have this new WINEPREFIX working as desired, you may want to add the above export command to your login profile so that it is set whenever you log in to your system.

Download the latest Daz Studio Installation Manager (DIM) to start installing the latest version (4.23 as of this writing).

https://www.daz3d.com/install-manager-info

Run the new DIM installer using wine:

$ export WINEPREFIX="/daz/.wine" $ wine DAZ3DIM_1.4.1.69_Win64.exe

Provide your Daz account information when prompted, then complete the installation.

Post Install Steps

At this point the basic Daz 3D Studio app should be able to run and it should see any NVidia GPUs installed on your system. If you're new to Daz Studio on Linux, you're done! Have fun.

On the other hand, if you are like me, and you have been using Daz for a while on Linux in a different WINEPREFIX (that was on a case-sensitive filesystem), then there's more work to do to get back to where you were. The remainder of this post focuses on that scenario.

Relaunch DIM to install all of your purchased content since it doesn't do that as part of the initial install.

$ export WINEPREFIX="/daz/.wine" $ wine 'C:\Program Files\DAZ 3D\DAZ3DIM1\DAZ3DIM.exe'

Reinstall any addons from other sources that were not installed using Install Manager (e.g., content downloaded from RenderHub or other non-Daz Store sources). This is required due to the fact that we installed in a new WINEPREFIX, so any manually installed packages need to be manually installed again.

Any changes made to the old installation (in my case, v4.21) need to be manually copied from the old installation/WINEPREFIX to the new installation. Here are the most notable that I have found thus far:
/daz/.wine/drive_c/users/korb/AppData/Roaming/DAZ 3D/Studio4/user layouts/  (my saved Daz Studio layouts)
/daz/.wine/drive_c/users/Public/Documents/DAZ 3D/InstallManager/Downloads/  (products installed with DIM but manually downloaded)
NOTE: for the InstallManager/Downloads/ subdirectory, there will be lots of files already present in the new installation. As such, you just want to copy those from the old installation that are missing into the new one, then launch DIM again to install these manually downloaded packages. They will be listed under the "Ready to Install" tab when you launch DIM.

Lastly, the primary reason for this entire exercise was to deal with assets that were created on NTFS but the creator was not careful about using consistent case when referencing files/folders (because they didn't have to be!). Any such content that you have installed in an old Daz installation will need to be reinstalled in the new installation. The details of that process are beyond the scope of this post - it can be anywhere from something as simple as unpacking a ZIP file into your "My Library" folder to running a custom installer supplied by the content creator.

Conclusion

If you rely on Daz 3D Studio to do your rendering work but have had enough of the hassles of running Microsoft Windows, what are you waiting for? Follow these instructions and you, too, will be up and running in no time with Daz on Linux. Enjoy!

To anyone that has followed my procedure to install DAZ 3D Studio under WINE on Linux Mint, I ran into some issues that you may hit, too.

I applied the latest package updates to my Mint 21.3 system , including WINE staging 11.1, kernel version 5.15.0-134-generic, and the latest NVidia 580 drivers. After doing so, I was seeing some odd behaviour, including menus not always displaying when I clicked on them, and some desktop artifacts showing through when I moused over the viewport.

Well...to be more precise, I updated Friday, and it installed WINE 11.0, and that version was doing that. I tried to downgrade back to WINE staging 10.20 (which was working fine previously), but the problems persisted. As such, I decided that one of the other package updates (there were several) may have been the cause of the issue.

Then WINE 11.1 was released yesterday, so I updated again and got the above kernel & NVidia driver updates, too. While I was at it, I decided to check to see if @SveSop had released any updates to the nvidia-libs package since last I checked (he had), so I grabbed that, too. The current version is 1.0.0, but an important note: it only supports 64-bit apps now, so if you use WINE with a mixture of 32-bit & 64-bit apps, you may need to follow some of the information suggested in the README that I didn't, since I only use my WINE installation with 64-bit apps.

Note that after downloading nvlibs v1.0.0, you need to run the installer to properly create the symlinks pointing to the new version in your WINEPREFIX.

Long story short (I know, too late for that!), having updated all of those things, DAZ started working well again.

I hope this is helpful for anyone out there in a similar situation.

korb · January 26

korb said:

To anyone that has followed my procedure to install DAZ 3D Studio under WINE on Linux Mint, I ran into some issues that you may hit, too.

I applied the latest package updates to my Mint 21.3 system , including WINE staging 11.1, kernel version 5.15.0-134-generic, and the latest NVidia 580 drivers. After doing so, I was seeing some odd behaviour, including menus not always displaying when I clicked on them, and some desktop artifacts showing through when I moused over the viewport.

Well...to be more precise, I updated Friday, and it installed WINE 11.0, and that version was doing that. I tried to downgrade back to WINE staging 10.20 (which was working fine previously), but the problems persisted. As such, I decided that one of the other package updates (there were several) may have been the cause of the issue.

Then WINE 11.1 was released yesterday, so I updated again and got the above kernel & NVidia driver updates, too. While I was at it, I decided to check to see if @SveSop had released any updates to the nvidia-libs package since last I checked (he had), so I grabbed that, too. The current version is 1.0.0, but an important note: it only supports 64-bit apps now, so if you use WINE with a mixture of 32-bit & 64-bit apps, you may need to follow some of the information suggested in the README that I didn't, since I only use my WINE installation with 64-bit apps.

Note that after downloading nvlibs v1.0.0, you need to run the installer to properly create the symlinks pointing to the new version in your WINEPREFIX.

Long story short (I know, too late for that!), having updated all of those things, DAZ started working well again.

I hope this is helpful for anyone out there in a similar situation.

Quick follow-up: after further use, I discovered that while the desktop artifacts in the viewport issue was resolved, the menus issue was not. After launching DAZ, the first time I open a menu, all is well, but on subsequent attemps, the menu often does not open or more accurately, is not visible. I have seen this in the past and resolved it, but I don't recall what the solution was. I'll keep playing and see if I can get to the bottom of it.

FWIW.

BlueFingers · January 26

@TimberWolf: Lutris was way easier, got it running pretty quickly, Thanks! Unfortunatly I did not backup my manifest so the fight is not over yet.

To everyone who is migrating: Back-up your assets as well as the manifest files before migrating!

Notifications

Daz Studio and Linux

Comments

Setting Up Your New WINEPREFIX and Installing DAZ 3D Studio

Post Install Steps

Conclusion

Adding to Cart…