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
Your whole report sounds most excellent. Thank-you for sharing your experience. I hope you’ll update once you’ve got Daz and Resolve going, as those are two of the apps I would want running if I setup a new box.
So, are you saying that using Arch is the equivalent of being a vegan for Linux users? XD
Haha, it's just a meme.
https://knowyourmeme.com/memes/btw-i-use-arch
I even said it wrong, too
(also I don't even know if Arch based distro qualifies or it has to be Arch proper).
Right then. Daz Studio on CachyOS with GNOME and AMD hardware. *Shakes head miserably*
First off, the good news: The DAZ UI under GNOME works perfectly. It's fast, responsive and, as far as I could tell with my 10 minutes of messing around with it, bug and glitch free. You also don't need to install a system-wide WINE because you don't need a CUDA installation. The GE-Proton runner which comes with Lutris works perfectly so there's no need to complicate things at this point. Let's go:
1) Open your console. Firstly, update the system. Always update the system before you install any application. It's important on all Linux systems but it's critical with Arch distros.
sudo pacman -Syu
Install Lutris - this is a manager for Wine applications and sandboxes them.
sudo pacman -S lutris
Select the first repo, extra-v3. You will often be presented with multiple repos to choose from when installing packages. If offered, always select the extra- or cachy- repos in preference to others which are probably not as up to date. If in doubt, do a search for the info.
2) Download the latest version of DIM from Daz.
3) Run Lutris. WAIT for it to update itself and download some packages. It's very easy to miss this but there are progress bars in the left-hand column. If you just pile in, nothing will work and you'll be starting again from scratch.
At the the top left-hand corner of Lutris you will see a + symbol. Click it to begin adding an application. Select 'Install Windows game from executable' and follow the process through. You'll be prompted for a name - DIM is the obvious choice - and at the final screen you'll be prompted for the location of the executable. Simply find the DIM package you downloaded earlier and select that. Let DIM install and run but at the end, uncheck 'launch now', and close DIM.
I hit a snag with this under GNOME and this didn't happen with KDE and Wine11. Just to check it wasn't a one off I installed it all again and had the same problem: If Lutris seems to hang at this point with nothing happening, don't click the abort button on the Lutris window. Instead, open up the sytem monitor and force stop the Daz DIM executable. This will allow Lutris to finish the process cleanly.
You should now have a blank grey panel in the main Lutris workspace called DIM. Double click it to launch and log in.
4) With DIM running, I suggest you don't install all the recommended items that pop up. I assume you have a drive with your Daz content already installed on it so all you need to do is close down that window and install Studio 4.24.0.4 and the CMS. Studio 6.x will not work without additional steps so don't try to install it at this point. Once you're all done, close down DIM.
5) Back in Lutris, right click the DIM icon and duplicate it. Call it Studio or whatever you like. Right click again, select 'configure' and in the Game Options tab change the executable by navigating to the dazstudio.exe executable which is where you would find it in a standard Windows installation - drive_c / Program Files / DAZ 3D / DazStudio4
That's it. One working Daz Studio setup. You will have to symlink your content directories as Daz Studio will be unable to see outside of its little Windows sandbox without this. I can't tell you how exactly how to do this as you haven't provided any information at all about your setup but symlinking your folders from inside the Wine prefix is what you need to do. Plenty of info available out there on how to do it. Once that's done you can add them in the usual way inside Studio. You'll need to update DIM if you use it for installing items you buy from the store to point to the correct locations as well.
It's a bit more complicated if you want to add Nvidia GPU support (but not massively so) and these steps would be required anyway. You don't, so you're done!
Additional Notes:
If your content drives use NTFS, Linux will be able to read them. However, if you try writing to them from a sytsem using btrfs or ext4 then eventually something will go horribly wrong. You'll need to change over the drive(s) by whichever means is the least inconvenient. There are utilities which purport to convert drives on the fly but the safest way would be to copy your data somewhere else and reformat into btrfs or whichever file system you picked during installation.
I suspect you won't want a desktop shortcut but, if you do, the option exists in Lutris on the right-click menu for each application. Renaming or adding fancy icons involves opening the shortcut with a text editor and making the appropriate changes.
So you mean if I install Fedora or Ubuntu and install DAZ 3D on it, but keep my old external USB SSD drives in NTFS Ishould convert those drives BTRFS or my choice ZFS, otherwise Linux will screw the exterrnal NTFS drives up eventually when I run DIM to download new or updated purchases and installl them?
If you can absolutely 100% guarantee that you will never mount those drives using Windows ever again, you'll probably be fine leaving them as NTFS. Probably. Bear in mind that file permissions don't transfer from Windows to Linux (and vice versa) so any read-only protection you've put on your content will be lost when mounting under any Linux distro. Encryption or compression is obviously not compatible. If you will not write to them from Linux, leaving them as NTFS will be fine as well, but this is not what you intend to do.
Linux will quite happily write file names with characters that Windows can't use and it can corrupt the index, even under normal use. The snag comes if you then try to open it up in Windows - watch the drive errors mount up... You will end up with folders and files you can't read or delete when using Windows.
The NTFS compatibility package that most Linux distros provide by default (ntfs-3g & fuse) is woefully slow at both reading and writing, especially so on clockwork drives. However, Windows cannot read btrfs or ext4, ZFS and many others (there are drivers for Windows but my experience of trying them did not end well!) which puts dual-boot users in a bit of a bind. I've got a dual-boot system with NTFS drives and I only write to those from Windows. Linux is read-only but that's self-enforced and I've messed it up a few times. exFAT would be a good compromise as long as you don't have any executables on your drives which you intend to run under Linux and, at some point, that's what I'll get round to doing. It's a pain to do with Terabytes of content though.
My experience of writing to NTFS drives using Linux has always ended up in some kind of recovery scenario requiring Windows. Do your own searches as there's plenty of conflicting advice but I would not recommend writing to NTFS drives if at any point they may be used by Windows.
Here's the real kicker though. If you are ditching Windows completely and have NTFS drives on your system, if something does happen to them you will need Windows to fix the issues. A power cut during a write operation, bad sectors, whatever you can think of. If they are Linux file systems then, well, you don't.
I had no issues so far using the same NTFS drive for both Steam on PC and Steam on CachyOS. However I will probably install everything on Windows and just play on Linux for comparison or a little tinkering. If you're dual booting anyway and do it this way you might be fine?
If you're using one drive that hosts executables for both Linux and Windows then you really don't have a choice - it has to be NTFS. I don't think any Linux distro will reliably run executable files on FAT32 or exFAT. Files written by games and applications tend to have conventional file names or are written to somewhere in the WINE prefix when being run in Linux/Steam so the chances of anything going wrong is slim. Having had to sort these problems out, though, slim <> impossible.
As long as you have access to Windows to correct any errors that may crop up, NTFS drives are... acceptable. @3DIO is ditching Windows entirely so if anything goes wrong with the Daz content drives, which are almost certainly NTFS, there will be problems which is why I recommended them being reformatted if possible. I find the performance difference between WIndows and Linux using NTFS drives very noticeable but, like all things, it depends on your own hardware and how you're using it. Some questions in Linux inevitably devolve into a form of 'What's the best length of string?' :)
If you go all-in on Linux and write to an NTFS drive regularly using DIM or manual installation my own experience is that it is only a matter of time before something goes wrong. I stick to Windows to write to the drives, except when I forget and cause problems. Your mileage may, of course, vary.
This will all pale into insignificance when 3DIO attempts to get an OpenCL driver installed, on Arch, with an AMD GPU that has a somewhat dated architecture using a mix of AMD's own pretty abysmal ROCm stack and open-source drivers. I managed it on a different distro with a modern AMD GPU but I suspect very little of that process will be relevant. There are the three of us that use CachyOS but none of us have ever tried to do that. Honestly, I'm not sure it's possible but I hope it is because I have never seen someone so excited to get a Linux distro up and running and be delighted with it at the end of the process. Most people are back with Windows within a week!