Adding to Cart…
![](/static/images/logo/daz-logo-main.png)
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
I got the installer to run under Wine/Linux Zorin Linux 16, but I get the follow error message when I start DAZ Studo, and none of my products appeaar even though they seemed to install.
HP Probool 650 G1I/I7/16GB/2TB SSD.
HALP!
I remember PostgreSQL being an issue in earlier wine versions (I think wine 7.X or something). But that was quite a few years ago.
What wine version are you using (wine --version)? Have you tried wine-staging?
Seems like I'm on wine 6.0.3.
I'll see if there is an upgrade.
It complain hen I try I upgrade update.
I've had quite the success going back to Lutris to do the installs. Even have the simulation running.
I got everything to run great in Fedora 41 using the fusion RPM version of Wine and the flatpak version of Doors.
I installed everything using this excellent instructions in here on Arch.
But I have an issue that I cant select anything in the viewport. It's like no object was loaded (but I see it obviously).
Any suggestions ?
Which tool is active?
It's the wine10.0-staging - from multilib repos.
I've installed the nvidia-libs0.8.1 (the latest release from repos).
Appreciate your help.
cheers.
I meant which Daz Studio tool (checked in Tools menu) just in case it wasn't actually a Linux issue.
It's Daz Version 4.23.0.1
I was asking about the tool that was active - open the Tools menu and see which is checked.
It was the Universal Tool, but it didn't work in Translate or Rotate Tool either.
Ok I solved it. It seems I have played around in the Interface Settings and activated the Pixel Buffer and set it to on.
After disabling it, the selection is working again.
Thanks for your help Richard.
Cheers.
Sorry but I have to come back.
While the IRAY Rendering performance under Lutris/Linux is close to Windows, the viewport rendering is very slow - like 2 fps slow. I use texture shading, so nothing really too fancy.
Edit>Prefernces>Interface tab has several settings related to draw performance, check that the two system match and/or try nudging them in the direction of performance.
Thanks again!
I enabled the Hardware-Antialiasing and set the Display Optimization to Best - runs smooth and fast like in Win.
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:
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:
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!