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
Unable so far to get OpenCL working on NVidia. Did I miss the solution, are we even sure this can work at all?
@3DIO
The final command must be something I've installed then. Try inxi -Fxz
Tell me what it says re. your GPUs but I think you might not have installed the drivers properly. At no point was this ever going to work just on its own, but you do need to get the drivers installed as a first step.
@bluejaunte
dForce works out of the box with nvidia-libs on Nvidia hardware but I've never tried installing Daz Studio via Steam. It's a novel approach and I suspect that's what causing you problems :) You can either get Studio running using bog-standard system WINE (make sure it's v.10 or greater), or via a WINE manager like Lutris. Symlink the CUDA libraries by simply running the installation script as described on the github page and everything will just work: dForce, iRay, and the denoiser.
Oh ok, will try that. I didn't install anything, this is Daz Studio installed on Windows started through Steam/Proton. The idea is to get the speed of Proton that makes gaming possible today. Or am I misunderstanding that completely?
@bluejaunte
Hadn't realised you were using Steam to run Daz Studio. I didn't even know that Daz Studio was on Steam. I had no Steam or WINE installed at all when I first installed CachyOS, and it was basically Lutris that handled everything to do with installing whatever needed to be installed to get Daz Studio working.
@TimberWolf
Ah, that one worked fine and it does at least look positive in so far as it recognised my graphics hardware (Copy and Paste below):
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: XFX Pine driver: amdgpu v: kernel arch: GCN-4 bus-ID: 29:00.0 temp: 54.0 C Display: wayland server: Xwayland v: 24.1.10 compositor: gnome-shell driver: gpu: amdgpu resolution: 1920x1080~50Hz API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms: active: gbm,wayland,x11,surfaceless,device inactive: N/A API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 26.0.5-arch2.4 glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 580 Series (radeonsi polaris10 ACO DRM 3.64 7.0.1-1-cachyos) Info: Tools: api: clinfo, eglinfo, glxinfo x11: xprop,xrandr@bluejaunte
I don't know if that approach will work but I think it's going to be problematic. I very much doubt the steam runner includes Optix and OpenCL, but I don't know for certain. I can, however, guarantee it will work if you install Studio via DIM (or the complete packagae executable from your product library) from within your Linux OS. If you follow what I suggested for 3DIO earlier, all you'll need to do additionally is grab the pre-compiled nvidia-libs package from Github, and then execute the install command from the terminal. There are full instructions on the web page itself. Should be child's play for a man of your talents :)
@3DIO
I remain unconvinced it's working (looks like the default Linux AMD driver to me), but there's an easy test. Install Blender, head to the system preferences and see if you can assign your 580. If you can't, you don't have the rocm stack installed.
Daz Studio is not on Steam. You can manually add whatever game or software to it and it will run through the Proton layer. Which I assumed has the most performance benefit (not for Iray of course, just the general viewport performance).
@TimberWolf
Ah right, bit beyond me that stuff, but as far as Blender goes, I assume you're referring to this screen. I should point out that this never worked on Windows either. I used CPU rendering on Windows just as I'm doing on Linux. Nevertheless, my dForce did work on Windows despite the Blender thing being exactly the same on Linux.
@bluejaunte
I understand what you've done. I just don't understand how you've managed to tie the (essential) nvidia-libs DLLs into that setup properly. Anyway, I didn't find any particular runner gave an advantage in terms of viewport performance. 4.24 on my system is running on system WINE (11.7), and 6.x is running on proton-cachyos-slr. The viewport performance in the Beta is pretty woeful even in Windows and the only reason it's still on that runner is I neglected to change it back to sys-wine.
I can't tell you how to get it working in the configuration you're using I'm afraid. Give it a whirl in Cachy itself - I doubt you'll find the viewport is any different in how it performs on Windows.
@3DIO
I'm showing my lack of expertise as well here. I didn't realise it had to be an RDNA card for rendering which yours is not. The only thing I can suggest is to join a Cachy forum and ask people who will be experienced with AMD hardware how to get the ROCm stack and OpenCL (Rusticl is probably what you'll need) working properly. I doubt any will have experience of Daz Studio but someone on there will be able to point you in the right direction but I have my doubts this will be successful.
Still, all it will cost is time and you'll undoubtedly learn a lot. I am not really the person to speak to for AMD stuff.
@bluejaunte
Thanks for the explanation. I'm not familiar with the Proton thing but will look into that once I get dForce running. No issue with performance here though. I'm actually quite mind-blown by the performance in some respects. For example, the speed at which Blender boots is truly mind blowing!
Even booting GIMP must be at least four times quicker than was on Windows!
@TimberWolf
Your expertise, time and effort is truly appreciated. I'll just have to hop between Daz Studio and Blender for the time being. I did invest in some nice Blender plugins a few months back, and they include cloth stuff. So not the end of the world, although I suspect you're in for another brain-picking when I get that Nvidia card :-D
Very easy, as mentioned just add Daz Studio exe to Steam then in the launch options add this.
PROTON_NVIDIA_LIBS=1
DS6 I've not gotten to launch at all yet. That is interesting it works for you using proton-cachyos-slr. I think I've read about that somewhere but didn't try it.
Those are native Linux apps though. Sure that stuff is fast and may be faster than on Windows for various reasons. The Proton thing is Valve having done a hell of a lot of engineering to get Windows games working on Linux at amazing performance. If you're just using Wine then at least as far as I understand you're not getting that immense engineering effort for your 3D accelerated applications. But it's absolutely possible I'm misunderstanding how it all works, or how much Proton affects OpenGL performance. It was just my gut feeling that anything 3D should best be run through Proton. I'll do some more testing at some point.
@bluejaunte
Well the thinking sure makes sense, I just hope you get it all working. I also do need to install Steam since I've got a perpetual license of Substance Painter on there.
I've not been paying too much attention to the whole Steam thing so far since I intend to read back when the time comes to install it. At least it does run though from the sounds of it, and my purchase does include a native Linux licence, so from that perspective at least, I have reasonable confidence it'll run.
After reading this again, since you're not running Steam you are doing this using Lutris or Bottles I guess? Essentially that's the same thing as I do on Steam. They're all just launchers really. And if your approach works with Iray and dForce I see no reason to try doing it through Steam. Have you tried at all to run DS4 through Proton like that as well or just DS6?
@bluejaunte
Yes - both running in Lutris in the same wine prefix. Lutris allows you to reconfigure the wine environment on the fly with a drop-down selection for all available runners. Both 4.24 and 6 work with basically every single runner apart from a very early version of Proton that's included for backwards compatibility. I could not see the slightest difference in performance with any of them.
The headscratcher for me is really why your dForce kernels won't compile. I wasn't aware Steam could auto-load the nvidia-libs until you mentioned it but if you can render, which you can, that's working fine. As an experiment I uninstalled my nvidia-libs and, as expected, the GPUs could not be used. However, dForce still worked so, under wine, Studio appears to be using the system OpenCL drivers.
What do you get if you type clinfo in the console?
Yeah weird. Same result as you with clinfo. Also finds OpenCL C 1.2 further down which is what Daz Studio is not finding. I tried DS6 from Lutris as well and doesn't open at all just like Steam. Tried with proton/cachyos/slr as well and didn't help.
Do you have a Wine prefix entered under Game options? Mine is empty at the moment.
Yup, that's the fundamental difference in our setups. You're running Studio from a pre-existing Windows installation, I've got both installed under Linux in a wine prefix. Also, DS6 needs a WIndows DLL copying into the prefix which is missing from the default wine repo - without icuuc.dll, it will completely fail to run. You can grab that from your existing Windows OS but you'll need somewhere to put it...
If you just want it working, install DIM using the DAZ executable in Lutris, creating a wine prefix. Run DIM to install 4.24 and 6.x, duplicate the Lutris DIM entry twice and change the executable for both Studio versions (so you'll end up with 3 Lutris entries, but only one prefix), symlink the nvidia-libs from the Github repo and finally add that missing DLL into the prefix's /syswow64 directory. You'll then need to symlink your content directory(s) from inside the prefix. Pick any runner you like in the config - they all work identically on my hardware. It's easier if you install the latest system WINE before you start this as well. It's not essential, but it allows you to use the nvidia-libs installation script rather than manually linking everything.
I'll have a go with Steam tomorrow but I can't imagine I'll be able to get something working that you couldn't to be honest.
I know you're discussing Nvidia in bluejaunte's case, but do you reckon that would happen with an AMD card as well? What I mean is, if I did what bluejaunte is doing by adding it as a custom program to Steam, and Steam using the OpenCL drivers, is there a chance that would work for AMD as well?
@3DIO
Unfortunately, no. All that did was re-confirm that the diagram that Csaa provided holds true for Nvidia as it does for AMD; OpenCL in Wine/Linux is not part of the GPU drivers. You still need the GPU drivers for Studio to recognise the card as a valid OpenCL device but after that they're not relevant for dForce. If you look in your Simulation pane, the Advanced tab shows something along the lines of 'No valid OpenCL device found. dForce is not available' - Studio is not aware you even have a GPU so step one for you is getting ROCm installed. At that point we could start looking at.
I'm still uncertain why you had problems installing the ROCm drivers which is why I suggested joining a forum where there will be people who are experts with the hardware you have. And, as you'll see below, I don't think Steam will help at all...
@bluejaunte
I can't get dForce working using Steam as the wine manager either, but DS6 started and ran with no other problems. I also can't get my GPUs recognised using Bottles. The only way I've managed to get full functionality in Linux is using system wine (just running the Windows executables directly and letting wine take over) or Lutris.
No point me joining a forum like that. Asking you this stuff is very different to joining a tech forum and expecting them to have patience with me. I'd be an absolute laughing stock since I have no idea about this stuff. I can feel my way around graphically with Linux, poke it around a bit and hope for the best, but that's about it.
But that first part about installing the ROCm drivers. Is there another, more beginner-proof way I could get those installed? Like is there a specific product that would trigger an auto-install and auto-configuration of that ROCm driver stuff for me, as opposed to installing them solo?
@3DIO
Nail, meet coffin. I still think it might be possible to get OpenCL working via Rusticl, as we did with a 9060XT (which also involves editing environment variables), but I'm raising the white flag. Don't be put off getting involved with a Linux forum; yes, there will be people who are curt and unpleasant but just ignore them. You will be able to get help.
Alright thanks, I should try installing through DIM and see if that makes a difference. Starting through Wine as far as I remember didn't show any GPU at all, but that was probably because nvlibs wasn't there right.
Don't know if this will be of any help but this is from AMD https://rocm.docs.amd.com/projects/install-on-linux/en/latest/
and this is from Reddit https://www.reddit.com/r/ROCm/comments/1qj9eom/rocm_72_official_installation_instructions/
@TimberWolf
I hear you, and after reading that lot I'm not even gonna try. I just have to face the fact that buying an AMD CPU was a good decision, but buying an AMD GPU was a bad one. I feel really bad for saying that since it's flawless in every other respect. But it seems it's always CUDA this and CUDA that, or you're left out in the cold.
Man, I really cannot stand Nvidia (and it really pains me to have to buy one of their cards at any price), but it is what it is, and I'll just have to buy one.
@RobertFreise
Big thanks for the links, but as TimberWolf mentioned, the architecture of my card doesn't support what is needed for it to work on Linux. This is confirmed by what's at the links, and it seems the only way around it would be to use a different distro altogether, and I'm very hesitant to do that because I'm very pleased with CachyOS.
What I'll do is wait until I've got the move over and done with, and then start putting cash away for an Nvidia card (again). Hopefully by then, some epic crash in the AI hardware market might lead to a whole wave of dirt-cheap RTX 5060 TI 16GB cards hitting the market, which to be honest is the only one I'm thinking about right now.
So after doing all this I now have DIM and Daz Studio 4 and Daz Studio 2026 in Lutris under a separate wine prefix (as opposed to the default which was just .wine) and Daz Studio 2026 does indeed start now. Both versions still report that no valid OpenCL 1.2 device could be found though.
When I set Wine version to System 11.7 Staging it finds the RTX 4090 as OpenCL device but it won't render. I get those CUDA # devices listed but they don't render.
@bluejaunte
Have you downloaded and installed the nvidia-libs package from here - https://github.com/SveSop/nvidia-libs/releases/tag/v1.0.2 ?
I say installed, but you're just running a script that creates the symlinks that are needed for Studio to use your GPU. If all you see is CUDA xxxxxxxxx in the hardware tab then that has probably not been done correctly. Once it is done, you'll still see the CUDA # devices but in addition you'll see your GPU named as you would expect.
Download that package and extract it to anywhere you like (but be aware you will need to keep the extracted files in that location as they will be symlinked from your wine prefix - I put it in the wine prefix itself so I don't inadvertently get rid of it but that's not essential in Cachy), navigate to it in Dolphin and open the console there. All you need to type is this:
WINEPREFIX=/your/wine/prefix ./setup_nvlibs.sh install
You can find the full path you need by right clicking on your Studio Lutris entry and clicking 'configure'. At the bottom is the full path to the directory.
If you have already done this - I suspect you have - then there is something odd with your setup. Uninstalling the nvidia-libs library leaves dForce working on my setup but with no rendering capability, exactly as expected, although the fact that you don't see your GPU as a named device in the Render Settings leads me to think it might be worth revisiting.
What Nvidia drivers do you have installed?
I did run setup_nvlibs.sh for the new Lutris specific Wine prefix. Only I had it built from source the other day, not realizing the binaries could be downloaded. But same thing otherwise. Without that the GPU wasn't detected for rendering either so definitely helped with that.
I'm a little uncertain as to what's working for you and what isn't. Can you render with iRay in DS4 and DS6 on the GPU? If not, your nvidia-libs library isn't installed correctly. If you can render on the GPU in both versions, but dForce is unavailable, something is otherwise borked in your driver setup. It's basically impossible to do an autopsy via a forum unfortunately as it could be a myriad of things.
How open are you to nuking your current Cachy install and starting again if this is the case?!
Zero open for nuking. But it's ok anyway, I'm just messing around. There is no actual reason for me to do any serious Daz Studio work on Linux. It's just neat to tinker
The obvious difference with my nvidia-smi is that I only have one RTX 4090. Who knows, maybe your Daz Studio uses the second card for OpenCL? Just odd that I get OpenCL on Wine-Staging, and rendering on Proton but not both in any of them.
I can pick either card for dForce and it works. With any runner. One is just significantly slower than the other. I can't pretend I understand what's happening with your Cachy install because I don't - lots of folks in this thread have had no problems with Debian, Fedora and Arch distros and just the one GPU so there's something unique with the way yours is configured.
Like you, though, I don't use Linux for serious work. Cachy is on my home PC but at the company I own and run it's Windows on every PC. I can't run unsupported operating systems for Unity, the Adobe suite, Studio and a fair few others when it's the main income for six of us.
The problem for me with Windows, as an individual, is that every update brings 'features' that nobody asked for, resource-consuming software with you providing the resources, claiming to solve problems that nobody actually has or that Windows itself created in the first place. WIndows serves Microsoft's interests, not yours or mine. We've become the product. I have no choice but to use it at my company, albeit the Enterprise version is marginally better than the quarterly revenue report generator that masquerades as Windows 11 Home - but in my own time? No thanks. I can still bring ideas and concepts home and work on them on Linux without some self-aware Clippy firing ads at me :)
Sorry I couldn't help further - hopefully you'll figure it out - but your OS is coughing up very, very strange results!
@TimberWolf
If you were me and were lumbered with my graphics card situation, which distro would you install to get it working with dForce?
Forget about my love for CachyOS. Forget about my love for GNOME. Forget about any previous display of enthusiasm I've shown for any specific thing. This is just a what would you do personally kind of question, if you were to choose the most likely route to getting it working. The way I see it is I'm out of luck for GPU acceleration with this damn thing regardless of whether I use Linux or Windows. I can (and so far always have) lived without CUDA, but not having dForce, that's just too much and I cannot go on like that.
So if you think you could get dForce working an a specific distro, I'd give that a try. And if that fails, then I suppose I could use one SSD for Windows with only Daz Studio installed, and the other SSD for Linux with everything else on it as my main OS. My thinking is that as long as I access the Windows SSD from my Linux installation and not the other way around, there is nothing Windows can do to my Linux install. As far as Windows is concerned, my Linux install woud not exist if I set-up the BIOS boot options in such a way.
But man, I really have to do something, cause lack of dForce is just not doable for me and I reckon it'll be some time before I can afford an Nvidia card.