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
There's a guide, but it's in small chunks throughout this thread.
I considered pulling together all the bits into one, but I'm not sure I'm qualified, I've not gotten Iray on GPU or dForce working yet.
Any installation commands on the 'Linux side will vary according to what distro you are using, and whether or not you decide to use Codeweavers, PlayonLinux, or just Wine with winetricks to set up Wine.
Anyway, I've put together a rought draft, consider it Daz on Linux Install Guide ver 0.1 (draft).
Anyone here want to add/change redo entirely, please do so and repost it.
Nice! I figured there was a lot of info in this thread, but I don't have the attention span to go through all the pages. I've heard some people had luck with wine-staging, so I'm going to look into that this weekend. The main thing I want is hardware iray support, but I guess I can use Reality/Luxrender if that works instead. Also DIM would be a great help. I can't imagine trying to install content manually.
I think DS is the last app keeping me from switching to Linux. I don't work for the gov't anymore, so I don't have to use Win/Adobe/Internet Explorer anymore.
Nice thing about Lux (and 3Delight) is the native renderengines (provided Reality doesn't crash on scene conversion) - There's also the mcjteleblender script to save scenes as Blender Render or Cycles for rendering on Blender. Iray lacks the same without paying after the trial period (I think it's still that way) - Luckily Iray seems very stable on Wine.
Wish I could track down why I'm not getting CPU OpenCL on Wine (and Iray GPU).
Wine-staging didn't fix my issues, and seems to make Daz unstable (a lot of freeze ups).
Good Luck over the weekend.
What is that? Is there another Iray application for Linux? I wasn't aware of anything with a trial period.
I might be thinking of Iray server, but even if it is, I don't think it's server farm category setup, something not within reach of the hobbyist. When I realised It'd probably be complicated to set up and operate and too expensive I lost interest https://www.daz3d.com/forums/discussion/71255/iray-network-rendering.
Oh, ok. I forgot about Iray server. I never really paid attention to it because I don't really like subscription services, especially to use hardware I already own.
Yeah, that's about when I disregarded it as an option too.
Just wanna point out that if you're on the latest Ubuntu kernel (18.08) then the PostgreSQL version on the repositories is different than the one mentioned in the tutorial. this version will not work for the CMS setup, because DS will still not connect after all steps are completed. If I am doing this wrong, someone please tell me.
I've update the Guide (see below) - the orginal was a very rough draft to kick off with, but this forum is a little quiet just now.
I found the CMS instructions I'd hastily pasted in not very clear so I've swapped them out for another set.
The biggest thing I did to get my GPU working was installing wine 3.9 or later. These versions are in the wine-staging branch and will need to be manually added to a ppa (debian based) or similar for RPM. The information is here: https://wiki.winehq.org/Download
Also need to have proprietary drivers installed.
That sounds promising. I got totally sidetracked. My computer has an intermittent problem where it may boot with 1 or 2 beeps, or may not boot at all. It doesn't happen all the time which makes it so hard to find the problem. I'm thinking maybe motherboard touching something and getting grounded, or a bad cable coming from the power supply. Anyway, I haven't touched Linux since this started happening.
Sadly, the most recent version broke the GPU Iray rendering (on my machine at least). Only the CPU is listed.
4.10.0.123 is working fine with GPU rendering though!
Gods, Nvidia proprietary drivers suck on 'Linux
Poor KMS, no Wayland, strange behaviour and screen tearing unless you out a load of odd tweaks and strange settings into Xorg and still performance is rubbish.
And even putting up with all that, to have none of the benefits you bought an Nvidia card for in the first place.
Maybe they are marginally better optimised if you are a gamer, but I doubt they put much effort in there either.
Nvidia can't be bothered to provide asistance to Nouveau, who're building a more compatible driver for their cards on Linux, and supporting older nvidia cards. It's even money whether my Pascal card will even be still supported by Nvidia by the time Nouveau have full compatibility.
I know I'm buying AMD next time around, to hell with faster Iray, it's not worth the other caveats, even if it was working on my system (which it isn't).
From what I've seen in the Linux forums AMD has very little and very poor support for Linux
AMD used to have poor Linux driver support. That was a while ago (days of the old Catalyst vs. fglrx driver). But most the yack on video drivers on Linux is the gamer people, and they generally care about framerates and other performance math. Unless there is an overriding shift in the balance of power in terms of performance, they'll keep repeating the old status quo as was.
AMD cards aren't as powerful as Nvidia cards ∴ AMD has very little and very poor support for Linux
While AMD Cards still lag behind on performance for games, the driver situation on AMD cards is much, much better than it is on the Nvidia front. AMD provide documentation and manpower to the OSS AMDGPU developpers, while Nvidia have been considerably less helpful (I'm not even sure there is a point of contact between the teams any longer due to the previous contact point at Nvidia leaving).
The AMD proprietry drivers are built to run ontop of the OSS drivers, which show the level of interoperability. AMDGPU_PRO provide OpenGL, OpenCL, Vulkan (although some of these are also provide through the OSS AMDGPU driver). The AMDGPU driver is lightyears ahead of Nouveau because the latter project gets so little help and has to reverse engineer everything and was held up a year due to Nvidia bringing in signed firmware and failing to release a copy of the keys to the Nouveau devs as they'd promised for a year.
In most cases, the OSS drivers (AMDGPU) are the recommmended solution, even with recent hardware, certainly not the case with Nvidia hardware, where Nouveau are really only recommended for hardware Nvidia themselves no longer support.
Even if the clear and overriding performance benchmarks were totally on the side of Nvidia, I'd still prefer to support the company that worked well with the OSS world than one whose response was lackluster.
Lots of info and a regularly update selection of new items on the Linux hardware front on sites like Phoronix rather than trying to get an accurate picture from random linux forums that might contain info years out of date.
I'm currently working on a new computer build, to be completed in the middle of 2019 for final installation of Mint 19. I use Daz3D for original content creation for my book cover art (and ONLY for that). Generally, I just get the models, poses and positions I want, use OpenGL rendering and toss that JPG into Gimp to do any touch-ups, add titling and such. I rely on the search functionality to find things, but I COULD spend time creating my own organized library of content, so if searching content is an issue, that's probably a simpler way to deal with it.
I'm also something of a gamer, and would like a future-looking GPU to go with my build. I've settled on one of the newer AMD CPUs, but I've actually had good experiences with (admittedly older) nVidia GPU's, and my experiences with AMD GPUs never passed out of the 2000's due to major issues with them. But that was all in a Windows environment. I haven't made any hard choices about the GPU yet since Linux isn't Windows, and GPU's have changed a lot.
Since ALL of my other programs have open source equivalents (or are open source themselves), the only program I have yet to tackle in factoring into my build is Daz. Currently I use Daz 4.10. I understand from the guides (thank you for those!) that it's the same version for Linux. In scanning over it, I plan on using all 64 bit versions, mostly because of memory and drive size access (I plan on a dual 4TB platter drives in a RAID 0 with external backups for the boot drive, which I expect to be a 256-512 GB SSD).
Since my NEED for Daz is relatively low (I only write a few books a year, so I only do cover art maybe once every 3-4 months), my priority isn't on getting ALL of it to work. Only static scene construction, photo rendering (OpenGL works just fine for me!) and the usual content access and alterations. Some of my scenes involve a lot of objects, but it's mostly positioning them, shaping them and whatnot. I don't do much more than that.
With all this in mind, what video card would folks suggest with an eye to a gaming future, but with an infrequent, but critical, need to use DAZ? I can play with Mint 18, but I understand there are some big changes in 19 whose impact on the instructions may, or may not be equally big. So I'm trying to start fresh, no preconceptions about builds and such and go with what hardware will work best overall for both Daz and gaming (I presume everything else will work with minimum fuss) for Mint 19 and onward. Given an AMD CPU, what GPU's (within the last couple of years or so) are the most stable options for both general gaming and Daz?
Any suggestions folks?
If you don't mind installing Windows in VM and your hardware supports virtualization technology (in Intel jargon: VT-x and VT-d), you can try KVM/qemu + GPU passthrough route.
My time is > 95% on Linux, so booting to Windows just to use DAZ studio is quite annoying. But for me it's solved problem now, with KVM+GPU passthrough.
I followed GPU passthough tutorial, mainly from here: https://davidyat.es/2016/09/08/gpu-passthrough/
Hi
Seems this discussion is a little ghost town of late - and Daz have stopped notifying me of new posts.
If you've not already decided, I'd weigh in and say if you are only using Daz minimally and just OpenGL, there hardly seems much point factoring it into you GPU purchase - AMD or Nvidia or even Intel onboard would do fine. More RAM is what you want to give Studio plenty of resources to run more memory equal more items you can squeezein a scene - 3DL or Iray will run just fine on CPU - without an Nvidia GPU you sacrifice GPU rendering on Iray - but it's still possible with Luxrender (should you decide to expand your Daz activities later).
Nvidia is still a Gamers favorite I think, but I feel the Nvidia proprietary driver has too many issues running on the Linux kernel (no Wayland mostly, low resolution bootups, poor console resolution, sensors still can't detect the temperature on my card). Nvidia are still slow to comunicate with the OSS driver group (Nouveau) while AMD have actually built their new proprieatry driver ontop of the OSS one.
Just for the record. Installed a fresh Antergos (Arch linux) on my desktop for a dual boot. Managed DAZ almost without hoops.
6.Install DAZ Studio and co
- Download DIM from DAZ site
- Create a 64 bit wine bottle (standard) and execute
- Go through installer, uncheck last checkmark (the one of run DIM after install)
- Create automatic launcher (right-click on desktop, create launcher, type DAZ Install Manager it will show up)
- Install samba, smb4k and python-ntlm-auth packages
- Run DIM through launcher
- Click on Account and fill in Name and E-mail
- Log in
- Install DAZ Studio and GOZ
- Installer will create an automatic shortcut on desktop for DAZ
- Set the proper folders for DIM: /run/media/..../Users/Public/Documents/ and then proper Downloads folders and Manifest folders (if you use Windows drive and have a dual boot with shared folders)
- Leave the Software paths intact
- Restart DIM - should show all the content as properly installed now
- Download the postgresql-9.4 9.4.19-1 snapshot from AUR website: https://aur.archlinux.org/packages/postgresql-9.4/
- Unzip the archive
- cd to the unzipped folder
- Run in terminal: makepkg
- Run in terminal: sudo pacman -U postgresql-9.4-9.4.19-1-x86_64.pkg.tar
- Run in terminal:
sudo su postgres -l # or sudo -u postgres -i
initdb --locale $LANG -E UTF8 -D '/var/lib/postgres/data/'
exit
sudo systemctl enable --now postgresql.service
-Run in terminal:
sudo -u postgres psql
CREATE ROLE dzcms LOGIN
SUPERUSER INHERIT CREATEDB CREATEROLE REPLICATION;
CREATE DATABASE "Content"
WITH OWNER = dzcms
ENCODING = 'UTF8'
TABLESPACE = pg_default
CONNECTION LIMIT = -1;
\c Content
CREATE EXTENSION citext
SCHEMA public
VERSION "1.0";
ALTER ROLE dzcms
SET search_path = dzcontent, public;
Just run the first line, put in password, then copy lines one by one
- Edit the file <your wine bottle>/drive_c/users/<your_linux_user_name>/Application Data/DAZ 3D/cms/cmscfg.json with the following contents:
{
"Port" : 5432,
"ConnectionURI" : "postgresql://dzcms@localhost:5432/Content"
}
CMS runs, render on CPU works. Unfortunately can't try the GPU render, don't have one. Dforce doesn't find any Open CL devices.
Chanteur-de-Vent
Thank you for all the detail. Will be trying this real soon.
Chanteur-de-Vent
Nice run though - though I see some some extraeneous steps only necessary for dual boot systems (you are running dual boot?) and Daz on the Window partition.
That's about what I get (I am on vanilla Arch) - so Postgres is on the main repo (no need to resort to AUR).
If you had Nvidia GPU, running Wine Staging does indeed give you Iray GPU (but still not dForce - at least on my system). I found Wine staging quirky and Daz Studio ran poorer under it than regualr wine and Iray renders seemed ready to crash the system anytime and I didn't get the kind of quick renders people promised - Probably work better with the Nvidia reserved for Iray only, and another GPU running the display.
You might try a few pages back on this forum user 'Mork' posted a list of instructions which might get you slow dForce. I've not had any luck though.
What does CLinfo say? (canget it here <a href="https://github.com/Oblomov/clinfo">CLinfo</a>; Click the highlighted windows binaries at bottom of page)
Yep, dual-boot. Moreover, I have two boot sectors on two different drives. Somehow Windows loading from Linux boot sector doesn't start up with my mouse and keyboard. But maybe that's exactly because I installed an additional boot sector. :)
I found the normal postgres on the main repository, wasn't sure it was enough. So I installled the 9.4 from AUR. Could be it was just an extra hoop I made and just postgressql would have been fine.
I tried what I could find - installed the windows open cl driver in the same wine bottle and installed the open cl driver for linux from AUR website. Didn't help. I'll check the CLinfo when I come home and post. ))
I found the normal postgres on the main repository, wasn't sure it was enough. So I installled the 9.4 from AUR. Could be it was just an extra hoop I made and just postgressql would have been fine.
Version certainly doesn't have to match the one running on Wine. As long as it's fairly recent and One is not a sudden and unexpected major rewrite of course.
RE : OpenCL - others have reportedly gotten it working, none of them using an Arch base (not many others use it).
Run CLinfo on your Linux side and the windows side. If both identify your CPU as an Opencl device it has to be Studio or Wine.
Linux side I don't even have my CPU recognised right now, AMD have buggered up their s/w stack by removing their standalone OpenCL driver on Linux. The AUR package remains broken, Mesa CLover isn't up to it yet, I can't install AMDGPU on a NVIDIA GPU system and Nvidia is not about to let an AMD device talk to their software.
If there was a half legitimate competitor to Nvidia, AMD or Intel I'd be shopping with them.
Long shot here - this forum has been quite of late.
Has anyone else had problems with DIM 64bit since 1.2.0.6? 32bit still ok, but I get errors on the console when tryingto launch the 64bit version -error and no ui or just no ui - on ocassion it does launch it reports it can't connect and the username/password might be wrong.
Mint 19, wine 3.19 with dotnet4.5 64-bit set to win7:
DIM 64bit, no problems. Installs, logs in, filters, downloads, installs, uninstalls.
Studio, still no dforce or gpu iray. Dang! I want dforce! I'm so tired of blender cloth sims...
Smart Content Connect/CMS works with postgresql10 if you follow the guid and change the schema ver to 1.4.
Wine is still missing the libraries for OpenCL on most distros, and also seems to be missing some library GPU processing requires (CUDA probably).
Try Wine-staging instead of Wine - I've not gotten dForce with it with my setup, but the GPU option was there last time I tried (Daz Studio) using staging on my system - it did make Studio feel more flimsy though (more graphic glitches than usual) - may work better if you had a GPU dedicated for 3D (i.e. not also running the display).
How to set up OpenCL in Linux
*daz studio dForce clothing simulation.
the information is outdated.
sudo apt install pocl-opencl-icd
Linux OpenCL check tools
1. clinfo : a command line tool on linux
On Ubuntu you can install it with:
Windows OpenCL check tools
1. clinfo.exe : a simple command-line application
2. GPU Caps Viewer : a graphics card / GPU information and monitoring utility
Note: daz studio dForce to work requires atleast OpenCL 1.2 version. But as on today winehq latest OpenCL version support availability is limited to OpenCL 1.0 version.
Update April 2019: Now 'wine-4.5 (Staging)' has 'OpenCL 1.2' version support.
click here to track current status of the winehq opencl 1.2 version availability
PS: for me nvidia GPU is now showing up in nvida iray render advanced settings and opencl device is now showning in dforce simulation advanced settings.
my setup: debian latest, nvidia gpu driver, winehq-staging latest, daz 4.10 64bit.
keywords: daz studio dforce clothing simulation requires opencl 1.2 device.
Has someone made D-Force work in wine? I think that the wine wrapper supports only opencl 1.0.
How to setup daz with NVIDIA Iray Render Engine on Linux ?
*always refer to your linux distro guide for installing latest nvidia driver. pls dont break your system in hurry.
so install wine-staging branch latest and apply system wide.
installing wine-staging will solve most of the issues. remove your old wine-stable.
last checked on wine-staging version 4.0-rc3
Linux CUDA check tools
Windows CUDA check tools
PS: for me nvidia GPU is now showing up in nvida iray render in advanced settings.
my setup: debian latest, nvidia gpu driver, winehq-staging latest, daz 4.10 64bit.
my skills: daz-beginner, linux-intermediate.
So far their seems to be no way to use the GPU as OpenCL device in Wine, it is possible to use the CPU though. There are some guides and follow ups on them on page 26 and 27 of this thread.