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
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Taking the knowledge gained with AMD, we can also make it work for Intel CPUs. I did not test to make it work for Intel GPU yet.
Prerequisites:
Download these files:
[1] http://registrationcenter-download.intel.com/akdlm/irc_nas/11396/SRB5.0_linux64.zip
[2] http://registrationcenter-download.intel.com/akdlm/irc_nas/9022/opencl_runtime_16.1.1_x64_setup.msi
If you have beignet installed, consider to uninstall it.
If you don't have it installed already, install clinfo:
sudo apt-get install clinfo
arch:
sudo pacman -S clinfo
1. Install CPU OpenCL (Linux)
Please note:
You should do this step only if you don't already have Intel OpenCL drivers installed for linux.
If you do, please skip this and proceed to step 2. You can check it with clinfo
Also, chances are high that you don't need this step at all, you can try with doing step 2 only and if that fails, come back to step 1.
Create a temporary folder, open the file [1], extract the file intel-opencl-cpu-r5.0-63503.x86_64.tar.xz to your temporary folder.
Extract the file intel-opencl-cpu-r5.0-63503.x86_64.tar.xz
Copy the contents of the extracted opt folder to your systems opt folder:
Create the vendor file at /etc/OpenCL/vendors:
Run clinfo and check that you have at least 1 device listed.
clinfo might segfault, no idea why it does, but that should not stop us. :)
2. Install CPU OpenCL within Wine (Windows)
Copy file [2] to your DAZStudio wineprefix, e.g. to drive_c.
Run the installer (please adjust the paths to match yours):
Install that thing, should work without problems.
3. Start DAZ Studio 4.10 and test
At this point you should have CPU OpenCL for linux and your wineprefix.
Start up WINE and D-Force should recognize your CPU this time.
GL&HF! :)
Speed-wise this performs much better than my AMD at home, but I need to say at home I use Xubuntu and this Intel version is installed on Manjaro (Arch).
Also my Xubuntu OS is quite old and I messed with it A LOT over time.
Uhm does anybody know where I can get the icon for DAZ 4.10 from?
Edit:
Meh, nevermind, I realized it has not changed since 4.9. :)
Followed your guide for the intel CPU OpenCL drivers, but no luck.
According to clinfo under linux (Arch) both the Nvidia and Intel OpenCL drivers are available. Installing the intel drivers in wine (staging) also went smoothly, yet still DAZ refuses to find a valid openCL device. Any ideas what might be amiss?
I also tried to test the Intel Opencl with a benchmark suite (compubench), but that finds only the Nvidia OpenCL, even on Windows. (I don't get why DAZ does not find the Nvidia openCL in the first place given that both compubench and Luxrender for windows do find it no problem).
Followed your guide for the intel CPU OpenCL drivers, but no luck.
I'm on Archlinux with AMD Ryzen 8-core CPU, Nvidia GPU GTX 1080
CLinfo gives me 3 devices detected (pocl (platform independant OpenCL implementation - worth a shot) Nvidia (GPU) and the AMD CPU.
- Opencl versions 1.2, 1.2 and 2.0 respectively (Daz specifically noted OpenCL 1.2 required)
However Wine installation of AMD, Nvidia or Intel OpenCL is aborted by installer. Luxrender for Windows finds OpenCL though, but no idea if that works as it constantly sticks on loading scene (with or without OpenCL selected).
Lux works fine using Linux Native though, OpenCL or non.
Not sure if it's a typo of yours, but if you are on AMD cpu, you need to use the AMD guide on the previous page. :)
Did you try to install the AMD OpenCL SDK I've linked there? (AMD-SDK-InstallManager-v1.4.87 (1).exe)
It should install without problems. If it aborts for whatever reason, is there some kind of information displayed in your console?
Note that OpenCL on CPU is really really slow, compared to the GPU (which I cannot get to work in wine)
I ran through that one first. Then on the off-chance I tried the Nvidia then in desperation, the intel one (supposedly openCL is platform independant, so the SDK should be independant from the H/W).
I'll give it another go this weekend.
Got it to work, turns out all that was missing is adding opencl to the library overrides in winecfg. Still wish it would also find the Nvidia openCL, but it's a start.
Hello everyone! It has been a while since I popped in this site ever since I quit Windows (on all my computers). I was browsing around and saw this thread & noticed the OpenCL discussion. This is a tricky part to work on, especially when one runs on an AMD card. The proprietary drivers leave a lot to be desired. NVidia does a much better job, as far as I have seen.
When running Wine, there is a package called "wine-opencl", so not sure if you guys have added it in, since it's an optional dependency.
Also, some programs act a bit strange when there are seveal ICDs that declare the OpenCL devices on your system, and most of them don't like seeing more than one. I experienced this with BlackMagic Design's Fusion, which wouldn't start on an AMD card. I had two devices showing on CLINFO. Naturally the AMDGPU (Open Source) and side-installed AMDGPU-Pro's OpenCL.
The workaround I found for it was this:
Or you could do it with all the ICD files, leaving the one of your GPU.
That solved the problem and the application was able to run properly, with OpenCL capabilities - though there are some bugs here and there. Perhaps this could direct wine-opencl to focus on the actual device you wish to use. Keep in mind, when you want to focus on your GFX card's OCL capabilities, it's best to not have beignet or pocl in your system - or at the very least, make sure the vendor ICDs are renamed - which temporarily disables them.
I hope this helps some of you guys.
P.S. I'm running Arch - hence why I can't really use the AMDGPU-Pro driver (which relies on an older Kernel version)
Hi vakont
You might have a point about multiple opencl devices, although I find it hard to believe anything is more tricky than trying to get anything running well on Nvidia proprietary drivers on 'Linux.
I am confused by your reference to using Archlinux and an wine-opencl package - no such package exists on offical repos or AUR - Opencl is included in community/wine on Arch - perhaps you also use another distro? Quick search reveals Fedora carries a 'wine-opencl' package.
Personally, I have an Nvidia GFX card (a 1080-something) but my CPU is an AMD (Ryzen 7), so I kind of want to keep both ICDs on, Daz never uses the GPU for Iray renders, so I'm doubtful of it's ability to put OpenCL or Cuda into play with it - personally I'm really regretting the choice of an Nvidia card, it's given me no boon in Daz usage and has only been a drag on the rest of the system - no KMS, no Framebuffer and Wayland no longer a current option either.
Personally I'd switch to Nouveau, just to get KMS and framebuffer back - another couple of months and I probably will - I'm getting GPU processing on Luxrenders on Linux native currently, but switching to CPU sees little overhead in comparison (possibly 'cause of my 8 core CPU and 32GB RAM).
Actually, eliminating (useless) Nvidia GPU from the OpenCL list might actually improve matters - Ive already removed my Pocl install (actually due to AUR update issues).
It is possible to use AMDGPU-Pro on Arch, but it entails doing your own kernel compilation on ABS (now replaced by ASP) - personally, last machine I had that had an AMD GPU I didn't think it worth it as it had a Kabini chipset (would really need to be useful, considering how often the kernel gets updated on Archlinux, and Kabini was/is barely supported by PRO drivers - at least at the time)
I got the AMD SDK installed OK, but no change to Cuda availability so far. Has anyone any details on winecfg and library overrides Cederien was talking about - I've tried setting it, but I'm not sure what I'm doing RE: Windows libraries anymore - I'd not touched a Windows OS since 2000 odd (beyond officey applications)
Just open winecfg, go to the Libraries tab, select opencl from the pull down menu and add it to the overrides. That's all I had to do.
I find it odd that you can't use CUDA/Iray in Wine with your Nvidia. That worked for me pretty much out of the box for my 1070. I guess you are familiar with Amyaimei's guide on DA (at least you commented on the 32 bit version of it). If you want to double check I added what I did (differently) on Arch in the comment section for the 64bit thread: https://amyaimei.deviantart.com/art/Install-DAZ-Studio-4-9-on-Linux-621288063
Wondered the same about the wine-opencl possibly it is the same as the opencl-icd-loader? At least that's the only optional opencl connected Wine dependency I can find in Arch.
Can't use Cuda/Iray in Wine
Iray works just fine, I'm just not getting GPU processing with Iray, it always selects CPU only - since I've a Ryzen 7 and plenty of memory, it's fine - could be better, but fine. Cuda and Iray are not synonamous. My only current bug-bear is having stupidly and optimistically plumped for Nvidia GFX hardware - Iray on Wine don't use it, Daz can't seem to use it, and it might even be blocking it dropping back to the CPU for dForce use and it's a handicap on the Linux side. It's a MSI 1080XS pretty new last July, as was the Ryzen and the mobo - I usually never buy brand new when running 'Linux, neither the OSS driver projects nor the manufactuer are up to speed on the Linux side for 6-8 months.
Luxrender using the Reality plugin seems to find Nvidia for GPU processing, but the Windows Luxrender always hangs loading the scene - I export to file and use the Linux native Luxrender which is damn nippy. 3Delight also is unstable in Wine, but the linux native version is damn fast (except using Marshians Reflective Radiance). No much Linux fallback for Iray available, thankfully, the Iray engine is quite stable under Wine, few to no issues, even as figure heavy as I run.
amyaimei how-to
The only change I made to the Amyaimei how-to was to add the cmscfg.json file to public as well as user - (actually just linked it) my Wine folder is riddled with soft-links as is my Runtime to add some sane organisation.
That how-to mostly covers getting CMS to work by setting it to bridge through SQL on Linux. I switched it to Windows7 from Amys recommendation of XP too, mainly as Reality plugin refused to install on what it thought was an XP install - Windows7 designation gave me no issues re: CMS (32bit or 64bit).
winecfg
The winecfg setting, yeah that's what I thought, I just wanted confirmation. No change when I override opencl in winecfg at all.
Daz Freezes
RE: Your experience of odd freezes - yeah, I get those, nothing to do with launchers, nor Xorg I think, more to do with Wine being unable to field some Windows call. I often use the i3 window manager, Xmonad, KDE, Gnome, Cinnamon, Qtile, others, mostly get freezes a lot some days, other times it can run for days, no problem.
Sometimes 'top' will indicate Dazstudio.exe is asleep 'S', sometimes the system thinks it's still running 'R' - program output (if your launched from terminal) will sometimes indicate a thread is blocked and it sits there, retrying every 30 seconds, sometimes there appears no indication - it appears much the same as if it's waiting for a dialog closure or some input to continue which never got launched. Sometimes It'll happen repeatedly in an evening until I switch to older figures (can only assume the code in Daz for Genesis and ealier is a little more robust), sometimes 'freezes' 'cause I've overloaded a scene, or merely tried to load an entire costume at once. I've found doubleclicking on a shader without have the surface selected helps then selecting the surfce and repeat reduces the likelihood of it freezing trying to apply the shader.
Or maybe it's just my experience on Archlinux wih Daz.
Archlinux Issues
Using Archlinux, you've introduced a more changeable system to trying to get Daz to run. Arch libraries and S/w get update far more often. Personally I upgrade at least once a week, reboot once a week. Sometimes some necessary lib doesn't get updated same time, causing running issues - A few months ago I kept getting thread blocks trying to run Daz for almost a week - started working again when libpng got an update (I was running -Syu every day that week)
wine-opencl - same as opencl-icd-loader - very probably...The latter is, along with the lib32 version (extra/ocl-icd & multilib/lib32-ocl-icd) and the only dependancy labeled 'opencl'. Linux distros with radically different bases package things a little differently.
I run on Wine (not Wine-staging as I don't believe there are any unapplied patches to Wine that will help Daz run better).
Did you have dificulty with dim (install manager)? - I've had issues with 32bit applications on Debian based distros before (like Kubuntu)- no issue with the Arch system though - even got it running on a 64bit prefix, but it wants to redownload my entire catalog, despite being softlinked to the existing 32bit repo.
At some point the next Dazstudio version will require a new prefix (wine bottle) and mabe it will all work better on the new prefix - I only got 64bit version set up right after third install last year, really only started being usable March/April last year - I started on Daz December 2016.
Iray working with the CPU is very much a given, so I've been talking about GPU rendering only and there CUDA is very much required. Your 1080GTX and my 1070GTX are very similar cards of the same generation. There is zero reason GPU rendering sholdn't work for you (unless the AMD Chipset on your board does something very odd). Yes CPU rendering might be sufficently fast for you, but honestly even a Ryzen 7 can't compete with the brutal raytracing power of a modern GPU. 3Delight runs pretty stable under wine for me as well. Can't help it but either the AMD chipset is a POS or something about your install is borked.
Freezes: Actually I've since determined it's a Plasma problem. While programs running under wine tend to trigger the freeze more often, about every non-native programm (i.e. non-KDE application) can trigger that freeze. A recent KDE update actually improved things, Plasma resets after a freeze ... mostly (and the freezes seem to have gotten more rare). The main panel still remains frozen, so the issue hasn't been resolved completely. Anyway it's definitely a KDE bug, not something directly wine related.
That said I do occasionally experience DAZ freezes, it's pretty much limited to loading (large) scenes though. Load times in general can be a bit of a nuissances of course, but that's a known problem of DAZ in general and under Wine in particular.
DIM: Actually it's the other way around for me. I had zero issues with DIM on Kubuntu 16.04 but in Arch I can't get it to install plugins for me (everything else works). That's running in a 64bit prefix. It works in a 32bit prefix, but that's not helping as it refuses to find the stuff installed in the 64bit prefix (and of course tries to install 32bit plugins for my 64bit DAZ Studio).
If you've no issues with GPU rendering through wine, something must be wrong my end - I'm not 100% the mobo doesn't need a firmware update to work better with the GPU and/or motherboard (current mobo onboard GPU is deactivated by the presence of Ryzen chip). I'm not missing any winetricks necessities like vcrun etc.
What architecture are you running your 1070GTX on?
I put it down to my particular hardware configuration, but doubt the AMD chipset has anything to do with the software borking out on GPU rendering. I do need to reinstall Arch though - I just swapped over the HDDs when my last machine went kaput and changed the boot line in Grub, swapped drivers, and picked up where I left off.
Daz Freezes - I get them on and off - and not any more often on Plasma than a minimalist window manager or even Gnome with its memory leak, I've not scene Plasma freeze-ups since the early Frameworks 5 days, and up until recently I was running from KDE-Testing repo on Arch.
You should try running Daz on another desktop other than KDE Plasma - I use a tiler as I like having independant workspaces on 2 screens, a simple window manager would free up extra memory - Openbox is a good one - see if you get the same number of freezes as you are seeing with plasma.
Daz freezes for me oddly occassionally - I've had several tonight, but over the last weekend none, often on applying hair shaders or certain clothes, and more often on later figures. Too many runtimes certainly slow up the system, recently found that saving poses takes a while, which I don't recall earlier versions than 4.10 did. Scene loads are not as bad as they were on my old 4-core (16GB) - could be waiting an hour if it ever responded again.
I run Dim on a 32bit prefix, so yeah, it fails to install 64bit plugins because of the sandboxing nature of the winebottle/prefix - your 64bit Daz install might as well be on another machine for all Dim on a 32bit Wine knows about it - you need to run Dim on both the 32bit prefix for your 32bit Daz install and the 64bit prefix for the 64bit install - it shouldn't be trying to install 32bit plugins on a 64bit install unless you've managed to tell Dim a 64bit install is a 32bit install. I install my 64bit stuff manually.
You could install both 32bit and 64bit Daz along with 32bit Dim on the same prefix.
Wow,
I can't believe this thread is still running! After completely messing up Linux Mint (which is probably detailed in here somewhere) I gave up and have been happily using Windows 10 for ages. Props to all of you that have persevered with this though and I'm glad that you have had results.
Keep up the good work
CHEERS!
Heh, you began this thread.
I know some users are just doubtful of the direction Windows is going, others just don't want to have to fork out for an upgrade. I'm sure there are other drivers for persevering.
Personally, I have been on Linux for a while, and it works for all my other uses, and while Daz is far from perfect on Wine, it's more convenient for me than dual boot or a second machine just at the moment.
Nice to see you popped back.
There were so many horror stories, theories and conjecture surrounding Windows 10 and none bore fruit when I eventually got it, on the very last day it was going to be free I might add. Their last feature update did cause a few issues, but, being an owner of the Pro version, it was easily fixed. I found it far easier to irretrievably screw up Linux than I ever did Windows. Linux reminds me too much of DOS based stuff and I never did get on with that much.
CHEERS!
I lot of IT proffessionals now refer to microsoft as 'slurp', due to the excessive 'telemetry' collection - that and fears of being tied into a subscription based service (which might yet come to pass).
Meh, I switched a decade ago or more, around Windows ME I think - I just prefer it for the commandline focus and it's modular nature, I love playing around with new desktop/ui paradigms.
You shouldn't be able to muck up 'Linux as much as windows, unless you are overusing sudo ( root (administrator in windows) - But I know I did it a lot in my first few steps with 'Linux, I learnt to fix things myself after a while and not have to re-install.
If you are happy with Windows 10, that's fine. I've a copy in a VM I try to get used to should I ever have to use it professionally or to get full function in Daz, I've still found Windows too reboot happy though, and Linux on windows doesn't cut the mustard for me.
...first, good to see you still here
Second, I would have received the much more restricted Home Edition as I had W7 Home which means my system would be at the total mercy of MS with no way to defer updates and unable to disable many "features" I don't want. I now have W7 Pro and am content with it as I still feel MS went of the deep end with their crusade to "keep computing safe" via force fed updates foisted on both the casual user as well as the savvy one. I had no trouble with once a month spending patch Tuesday reading reviews of updates before saying "yea" or "nay" to them (saved me from a lot of BSODs and boot up issues). I also don't need some inane personified "digital assistant" (which after an upgrade said Home Edition, I understand can no longer be disabled), I still have the faculty to search for what I need on my own and don't need a computerised nursemaid nagging me.
I just had the file manager (Win 10 Pro) stop showing my network click on network get green bar nothing in network.
I rebooted the machine and got my network back but Win 10 deleted 3 zip files from my downloads folder and removed 2 od my 3d utility programs (geometry stripper,and UVMapper) these were not on the C drive I install no programs on the C drive
I found how to safely uninstall Cortana completely. You have to have Classic Shell installed (this comes with the old style Windows Search), but, once you do, you can kill her with fire! You can also reactivate Windows easily if you make hardware changes, you activate it under a digital license tied to your Microsoft account and it's easy after that. I'm happy with things as they are. If there's anything I want to know I can look it up from reliable sources and not "Kev down the pub reckons.." guesswork.
If you're a programmer at heart, get Linux, if, like I found I wasn't, you're not, then Windows will be more our bag
CHEERS!
...however you have W10 Pro which offers more user choices through workgroups. I would have received 10 Home Edition which gives you almost no options except to turn off telemetry and disable updating completely.
I'm again content with 7 Pro and not too terribly concerned with the 2020 deadline as I have a very tough firewall.
I got 10 Pro becasue I upgraded to it from 7 Pro. I didn't know 7 expired in 2020, that's good to know.
CHEERS!
Be careful with the updates on Win7 they've been breaking it repeatedly even more so than W10
Never had one problem with 7 updates, have had some with 10 though.
CHEERS!
There have been a lot people myself included that had our machines down due to Microsoft updates took Microsoft about three days to release a fix for it
One of their latest borked peoples networks it got fixed pretty quick as the I.T. departments for the business world were all over them about it
Oh, sorry to hear that, they are unlikely to maintain things with 7 as well as they used to.
CHEERS!
Could have been worse Nephew had three systems borked beyond repair and had to wipe the drives and do clean installs even though he had backups on his server couldn't access them
Oof, I know the Fall Creator's Update caused carnage with 10, but, that was solved by installing an earlier build and deferring feature updates (only available in Pro). Never had it as bad as you described.
CHEERS!
I'm still running an i5-4670k on a Z87 Chipset Mobo. I've been looking into getting a Threadripper. Needless to say your experiences made me hesitate, twice now that I got dForce working. Loosing both GPU rendering and dForce again would make getting that new CPU pretty pointless.
I might try, but since I see those freezes pretty rarely nowadays comparison would be difficult and rather subjective/luck dependend anyway.
Why would I want/need a 32 bit DAZ install? I see only disadvantages (like no Iray engine) from it. Aside from DIM being able to install plugins there.
Why would I want/need a 32 bit DAZ install? I see only disadvantages (like no Iray engine) from it. Aside from DIM being able to install plugins there.
Good point - if you are totally Iray dependant. - I still do the odd 3DL render (it has 'some' advantages over Iray, still), and have been trying out Lux - and being Linux, there's no memory limitation like there would be with 32bit Daz on Windows.
I got 32bit working first, in the following months, the 64bit version become more usable with (Wine well into version 2) (although maybe some Daz changes helped). Since plugins install without intervention, and even updates over Dim run, it keeps itself up-to-date. I keep two 64bit prefixes, one for latest, one on the previous version (for fallback) - I like that I have to update manually on the 64bit side just now. - prevents a potential broken version coming down at me.
Yeah, I'm pretty much reaping the harvest of breaking my usual rule of not buying the latest h/w for linux, I think. Mobo, Chip and GPU were just out, last July. I'm looking into a Mobo firmware upgrade, and maybe trying out the Beta Nvidia drver on Arch..