Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
@BlueFingers
Glad you got it working. Lutris takes the difficulty out of installing most Windows software.
Quick request - once you're up and running could you check the built-in denoiser for me? I've re-installed Mint on a spare drive 3 times now with various different options and it never works for me. I'd like to eliminate my particular hardware or idiocy before I add the preamble to my guide. I have not yet found a Linux distro where I can write 'Daz Studio works without issue' without adding 'but....' to the end of it.
It could be my multi-GPU setup, it could be I installed Mint during the wrong phase of the moon, I just don't know. It appears that Optix thinks it has run out VRAM but it won't denoise a cube with a single spotlight. VRAM it is not. If it doesn't work for you I can place the blame squarely on Mint. If it does work for you then it's something local to my setup.
Everything works perfectly on my distro BUT.... it won't boot if multiple monitors are connected. I ended up buying a hardware switch to solve this and it's just another layer of hassle. There's always a but...!
@TimberWolf
Well, I've been using Mandrake/Mandriva/Mageia for many years, but I've never tried setting up Daz Studio on it. I believe it is, or was, originally based on Red Hat.
So, that's what I would like to try working with for Daz Studio, unless I encounter some insurmountable problem. :)
@PhthaloBlue
I've had a look at the Mageia website and in particular the wiki and.... ummm... no. Mandrake and Mandriva are basically the digital equivalent of archaeology at this point as they died in the early 2000s and Mageia is running a kernel that doesn't support anything even remotely resembling modern hardware.
Maybe, just maybe, there is someone out there who could crowbar the packages that Studio and CUDA need into the corpse of Mandrake and it's offshoots but I'm not that person - I lack both the knowledge and the time.
Can I turn the question round - is there anything preventing you from trying out a more modern Linux distro which is actually compatible with the GPUs Daz Studio needs? Fedora Linux is the desktop OS that Red Hat support now and has the features you'll need to run RTX cards, as well as the software repository with drivers et.al. I doubt it has any resemblance at all to Mageia. What you have now is a total non-starter unfortunately.
@TimberWolf
I never used the denoiser when I was running on WIndows so I am not sure if I will notice the difference (I think I tried it once but did not like it). But I will try it out when I have everything up and running and let you know what I find.
@TimberWolf
I successfully enabled the Nvidia denoiser on Tuxedo OS (Ubuntu base) using the
ln -sfcommand to link the Linuxlibnvoptix.so.1to the Winenvoptix.dll. It initializes perfectly without crashing. However, the performance hit is extreme iterations went from 0.05s to 5.1s. It works, but it might not be practical for active rendering.Once that OptiX link caused the slow-down, Iray seemed to "blacklist" my RTX 3080. Even after removing the link, the card showed up in the Hardware tab but there was no communication and DS fell back to CPU rendering and I just could not get the 3080 to work anymore. After my attempts of fixing it things got real messy and it seems I have to reinstall Daz Studio. Now I am not an IT guy so my interpetation maybe wrong but this is what it looked like to me.
I am staying well away from the Denoiser, it is not worth it for me
EDIT: The symlink makes Daz think it has OptiX, but the translation layer can't handle the compute load, forcing it into a "hidden" CPU fallback that persists even after you delete the link. At least, I think that what went on.
I'm so sorry that bricked your installation. If I had any idea that could happen I wouldn't have asked you to run the test. In Mint it failed pretty gracefully. I've been testing quite a lot of distros for Daz Studio compatibility and none of the Debian-based ones have a working denoiser (which is why I wondered if yours might the 'The One') but none have trashed the wine prefix when the denoiser failed to start; although what I have never seen is it starting in the first place as you managed. I also symlinked the Optix dll although I used the nvidia-libs library - https://github.com/SveSop/nvidia-libs - rather than the wine libraries.
Fedora and Arch derived distros seem to work perfectly, especially with the KDE-Plasma desktop. Cosmic is hit and miss. It works well with Studio in Fedora distros but it's a complete mess in Arch distros.
Best overall compatibility I've seen so far is CachyOS with KDE-Plasma. Everything just works exactly as it does under Windows with no workarounds, no issues and no hassle. Mint Cinnamon is a close second with one or two minor UI discrepancies.
After you mentioned the denoiser I couldn't help myself but to try it out, I just had to see if it would work and you have been a great help, so no worries.
I would still be struggling with bottles if it weren't for you. When I had it running it ran really smoothly, I made a render with some effects and lots of tweaks in the render engine and it went great. So if no denoiseer is needed I can say Tuxedo OS is a good distro for Daz.
To bad I really prefer Debian based distros, and Tuxedo OS due to it's customizations runs really well on my laptop so I don't see myself distro hopping soon.
@BlueFingers
And anyone else interested...
I've just got Studio Alpha to run in CachyOS and I expect you should be able to do the same in Tuxedo and many others with little difficulty. If you can get Daz Studio 4 running, you can get the Alpha running. You'll have to install DIM via Lutris if you haven't already and the process is identical. On startup it fails miserably and the logs are a lengthy and somewhat disappointing list of failures of various DLLs to load which initially confused me because they are all present. It's just one Windows System DLL that's missing and that sets off a cascading failure: icuuc.dll
Grab it from here - https://www.dll-files.com/icuuc.dll.html - it's the very last one, the larger of the two 64-bit libraries. Drop it into /windows/syswow64 or the same directory the Alpha dazstudio.exe is in in your wine prefix (it shouldn't matter) and it will fire up and create the usual set of files on its first run. Symlink the Nvidia DLLs, symlink your libraries again and it should work just as well as 4.24.x.
The viewport performance is possibly worse than in Windows but the rendering times on my benchmark scene were about 10% faster. However, because they are so quick with multiple GPUs I'd say that's within a margin of error - it may not actually be quicker but the logs say it is. It's more than usable as a platform to launch your scene for rendering (or to kick it across to a local Iray server) but it would be a miserable experience to try and actually build a big scene or use strand/curves hair.
After wrestling with this for the past four days, I have come to the conclusion that this is likely a WINE/Qt bug. I have opened a bug report with WineHQ to see if I can get one of the devs to check it out.
https://bugs.winehq.org/show_bug.cgi?id=59338
If anyone else is hitting this one-shot menu bug, feel free to add a "me too" comment to my bug ID. Thanks!
As described above, my experience with the latest WINE updates has been less than stellar, hence my menus bug filed with WineHQ.
However, I am also seeing another baffling new behaviour - significant lag in the UI while working on posing a scene.
For example, I have three characters in a scene and I have the viewport set to Filament mode. When I mouse over the characters, it can take anywhere from 1/4 of a second or longer - sometimes 3-4 seconds - for the node highlighting to be displayed. This is very annoying and really slows down my workflow, though it still works. I have the "__GL_MaxFramesAllowed=1" variable added to prod Daz/WINE to update the viewport more quickly, but with that unset, I still see that weird behaviour. If anyone else has seen that and has some idea as to what to try to get it resolved, I'm all ears.
Perhaps yet another WINE bug is in my future.
BTW, I am seeing this with 11.0 (stable), 11.1 (staging), and 11.1 (devel). Same with the menu issue.
@korb
I've been installing various Linux distros on and off a spare drive for the last week or so for testing and Mint was one of them. I had zero problems with Mint Cinnamon 22.3 and WINE 11.1, using SveSop nvidia-libs 1.0 apart from the Nvidia denoiser not working as discussed above with BlueFingers. The only UI issue I encountered was the resizing of panels; the UI was slightly sluggish and didn't update quite as snappily as it does in Windows 10/11, but it still worked. And that was it. Everything else worked perfectly including all the menus and other UI elements.
This obviously doesn't help with your 21.3 issues but the latest Mint build is not problematic with the latest WINE - no lag, no selection issues, no menu problems, nothing. I'm not entirely convinced this is a WINE issue but when I get a moment I'll install your version and see if I encounter the same.
Any reason why you can't roll back to a snapshot before you ran the updates?
One of the unfortunate reasons why I'm not installing Linux is this: 60 pages and counting of trying to get Daz Studio to work properly including all features and Nvidia GPU utilisation.
I stand up and applaud the coders and users that can spend time trouble shooting and finding fixes. The Daz devs need to really consider a native installer for Linux, not just for Winslop (Windows 11) and Mac. Blender can be natively installed onto Linux.
And someone, please a cycles render engine, so I can drop Nvidea as well.
Cycles would be good. Maybe Eevee as well?
@n.aspros123
I've got Daz Studio 4 and Daz Studio Alpha running under Linux with zero issues. Zero. Everything works. But you are 100% correct.
It's not a case of just double-clicking an installer and it works. It's time consuming and if you encounter any issues it requires knowledge of how your particular version of Linux works and even then there might be some strange mis-match of various code libraries because one time back in July you forgot to update your system properly. I've got everything working in a variant of Arch Linux which is possibly the worst operating system you could recommend to someone just starting out in Linux. I'm working on a guide for it (and more user-friendly distros) and, great, you follow it and Daz software works in your Arch Linux distro. And now you want to install VLC or MS Word, or your favourite game? You'll hit up Google and it will serve you up some AI reponse which might work. Or it might not. Or it might break your whole setup. You know this so you register for some forums and they're no help or too aloof to bother with you. You can spend half a day learning how to do something that would take you a minute in Windows.
Linux in most guises isn't quite ready to replace Windows yet but if you can get everything you need on a day to day basis running reliably, you can drop your Windows installation back to Win10 for the speed over Win11, disable your network adapters so it never connects to the internet and use it for those applications which won't play nicely with Linux. Linux is faster, lighter and actually more predictable than Windows - there are 'immutable' distros (designed to be new-user proof) like Bazzite which really are one-click installs and work superbly but they don't play nicely with the requirements for Daz Software because they lock you out of changing anything at a system level.
Linux distros also won't port your data to a corporation who will monetise it.
A native Linux installation (QT6 works very nicely in Linux) would be superb but Daz would have to see some kind of return for their investment in that dev time - increased store sales, increased subscriptions to Premier, etc. etc. - and I'm not sure, despite me being a Linux flag waver, that they would see that return at this moment in time. Linux adoption is gathering pace so never say never but I wouldn't count on it in the immediate future. This is why I completely agree with your viewpoint.
@n.aspros123 & @Masterstroke
I am not an IT guy at all, but with Lutris and the help of Google Gemini (free version) I was able to install Daz Studio 4.22 and DIM without to much trouble in about a 6 hours. Google Gemini is actually really good in sorting things out for you and guiding you through the process. It was easier than learning Daz IMO, so if you can make renders with Daz you should be able to get DS to run on Linux (at least on a Ubuntu derivative like Tuxedo OS which is what I am using).
I am using Timeshift to make system backups, and Gemini even made a script for me to back-up my Wine registery and Daz Layout so when things break because of an update I'll be up and running again in no-time.
Cycles and Eevee would be a fantastic addition IMO.
Tips if you plan to migrate to Linux:
1. Backup your manifest files as well as your assets, this would have saved me a day or three as I had to re-download my whole library which was actually the most painfull thing during my migration.
2. Bottles+Daz+Linux do not always work nicely together (at least on Tuxedo OS), Lutris is far far easier to get things up and running in.
3. Do not try to get the Denoiser to work, I never used it when using Windows. But when I tried to make it work on Linux, it destoryed my Wine set-up.
4. Use Google Gemini, it is really good in troubleshooting and guiding you through the process.
5. Use a X11 session, not Wayland.
I do have that snapshot, and I have debated reverting to it. However, I am reluctant to purposefully stay behind current software versions due to my background in IT. Many of the updates that come out address serious CVEs, and I don't want to end up with my system in a vulnerable position due to a lack of diligence in keeping it up to date. Silly? Probably. But that's where I am.
With that said, the reason I am still on Mint 21 and not 22 is because I have projects I am working on in Daz whose timelines I did not want to put in jeopardy. However, given these issues, perhaps now is the time to upgrade to 22.
One of the things I did not like about 22 was their stance on ZFS support. Yes, I can still use ZFS on 22 - it's not unsupported entirely - but they removed ZFS support from the installer. Their rationale was that it was not worth the effort given the small number of users that select it. I figure they may be thinking about removing it from Mint entirely, and the other filesystem options are so technically inferior that I can't imagine doing without. If Mint ever removes ZFS, I'll probably switch to a different distro.
Couldn't have said it better myself. I have been 100% Windows-free for 10+ years. Well...mostly. I still have XP installed in a Virtualbox VM so I can play Red Alert from time to time. :-D
But as you say, the switch is not trivial. I've had many people ask me if they should switch, and I caution them about how self-reliant they will have to become in order to get done what they want. But with that said, I have converted my wife over to Linux (though she has a dedicated tech support person available 24/7) and my late father used Linux (Ubuntu or Mint) for the last 10 years of his life at my behest. He only used it for email, web browsing, and writing things in Libre Office (not even spreadsheets, even though he was a retired CPA), so the risk was minimal. However, he would occasionally call me when some company he was dealing with told him they would not help him with something simple because he didn't run Windows or MacOS. That was really annoying.
A Linux-native version of Daz would be splendid. I have debated switching to Blender for the simple reason that it IS a native app, but I have a significant investment in assets that are designed to work with Daz that do not play well with Blender, so I have made the decision to stay put. I am a Daz+ member currently, but would switch to Premier in a heartbeat if that bought me a supported Linux-native port. But I agree, unless and until they see the potential for a positive impact on their balance sheet, why would they bother?
As a recent refugee from Windows, I tried for many hours to get Daz working on Linux (mint). I could not get it to recognize my GPU and the interface scaling was pretty messed up -- extremely small with no option to resolve it without messing with my desktop resolution, which I had already set and had other software optimized for.
I've come to the conclusion that the my best option is to dual boot. Linux as the daily driver, and Windows for the few edge-cases (some gaming, Daz, and whatever else is effectively restricted to Windows). I look forward to the day I can ditch Windows forever.
@luckylappe94
I use a similar Distro and I had the same issue when I tried Daz Studio with Bottles, I spend days on it and it drove me insane. But when I changed to using Lutris the issue disappeared and the installation was not hard and I could get Daz to recognize my Graphics Card without to many issues.
For the interface I used "Emulate a virtual desktop" in the Wine Configuration (under the Graphics tab) set to 1920 × 1080 and a screen resolution of 120 dpi, but you might not need both. That way you do need to mess with your desktop resolution.
Did you see my prior post about getting it to work on Mint? I wrote that for 21.3, but it still mostly applies on 22.3 (which I just upgraded to). If you're not seeing your NVidia GPU, then it probably means you did not install the nvidia-libs package in your WINEPREFIX.
FWIW.
Oh, and I think I touched on font size in there somewhere, too. You'll want to use desktop mode and set the DPI to something larger than the default - I have mine at 144.
FYI, I had been holding off on upgrading from Mint 21.3 to Mint 22 because Daz was working well and I did not want to risk project progress to upgrade.
With the problems I started seeing after my latest apt update/upgrade on 21.3, I decided it was time to take the plunge, so I spent Friday and part of yesterday getting to 22.3.
Unfortunately, that did not resolve the Daz/Qt menu issue, but it did help with the UI lag. It's still there, but much better than it was. The one other regression that I did see was that saving files and enumerating files in a file dialog seem to be taking longer than they used to, but that's not a big deal.
I am now at the latest Daz Studio, nvidia-libs, Linux Mint, NVidia drivers, etc. Even though it didn't fix all my issues, I'm certainly better off than I was. *shrug*
@korb
I'm going to guess you ran the upgrade from the terminal rather than nuking your current installation and starting from scratch with a new ISO? I did not see the menu and lag problems you are experiencing with Mint 22 (Cinnamon desktop) with a fresh install so my suspicion is you have some libraries that are causing problems which aren't part of the kernel. Obviously, I don't know how your system is set up and how easy/disastrous it would be for you to start with a clean slate (and our hardware will undoubtedly differ) but if it's becoming a real annoyance it might be something worth considering.
Anyway, a person with your experience should be on Arch! Everything Daz-related works 100% with zero glitches and with the Diffeomorphic Blender add-on to transfer your assets you really can go 100% Linux and use Daz. And you'll also get to enjoy the rolling updates and rolling update catastrophes :)
On a more serious note, if you haven't seen it, Diffeomorphic is a superb free add-on for Blender with an accompanying script for Studio that makes light work out of transferring characters, expressions, poses (including JCMs and other morphs), environments and props. It's not really set up for any figures older than G3 due to weight-mapping issues (it will transfer them but.... messy) so if the bulk of your work uses G2 or older this won't really help you much but if you're using the more modern figures in your renders it's indispensable.
---
The real answer to running Daz on Linux for every user, beginner or expert regardless of distro without too much development effort, is a Flatpak. It would have to come from Daz because it would include their proprietary code but it wouldn't be time-consuming to build. Even a Steam package would work. If I had to put money on it I think they will at some indeterminate point in the future start supporting Linux. It's still a bit niche, but it's growing rapidly and I believe a lot of companies will start to see that being on the platform is beneficial to their bottom line. Not yet, though, sadly. Not yet.
Hi! I just setup DAZ on a fresh install of Nobara, on a 4070 gamer laptop. I think it might help a few people out there. The troubleshooting steps above need some adaptation to get the Nvidia to be seen by DAZ. It´s surprisingly straightforward:
- Nobara must be fully set up with the Nvidia proprietary drivers. You´ll get Wine 11 by default. You can double check in the terminal with "wine --version"
- Download the DAZ install Manager like you would on Windows and just run the .exe to let Wine take over.
- After a successful install of DAZ and a few assets, running it just worked. I set the default scene to iRay to avoid the Filament issues.
>> Only the CPU appeared in the rendering options, which is expected.
- Download the last nvidia-libs from GitHub: https://github.com/SveSop/nvidia-libs/releases
- Extract the nvidia-libs folder somewhere easy to find. Open the terminal and cd into it (for the beginners: just type "cd Desktop" then "cd cd nvidia-libs-v1.0.0/" if the folder is on the Desktop)
- Run the command ./setup_nvlibs.sh install - you should get the message "WINEPREFIX is not set! This may create a wineprefix in the default distro folder) Continue? (Y/N)" - reply "y"
- If everything works as expected, you will get the message:
"Symlinks created in . 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 can also use: WINEDLLPATH='/home/name/Desktop/nvidia-libs-v1.0.0/x64/wine' env variable to use NVML
You need to REMOVE old overrides if older version of nvml have been used in"
That´s it! After this operation, my Nvidia 4070 was there, and activated in the render settings by default :)
If you try to install the nvidia-libs through the Nobara package manager, it won´t work, you will get the usual error message telling you that the installation is conflicting with X11 or something alike. You need to download the folder manually.
On this system, I didn´t expect it would be that simple.