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
A monster rig, right enough.
I can't recommend going all out on multi Nvidia GPUs for Linux users looking to use Daz at the moment, as chances are GPU render avilability is patchy.
I really don't think Linux buyers of Nvidia hardware get the same value for money as Windows buyers.
At least AMD support the OSS AMDGPU project, even if their GPUs are not up to the same level as Nvidias, and Prorender is not tied to AMD hardware like Iray is with Nvidia and Cuda.
I see you like to build 'em too. I can't visualize this. Two chassis, two power supplies, but one system.
That's the perception, although I've seen it said otherwise. IMO, it is about the ability to remove heat. The efficiency of the medium. Water cooling takes up where air cooling leaves off. A 12-core can be cooled comfortably with a Noctua D15. 16-core is marginal. More than 16 cores, I would use water. That's the reason I stopped at 12 cores. Water may also be quieter, depending. The air flow in the case itself is a big factor. The air flow in the Silverstone FT01, which I am using, is as robust as it gets. It's the only case I know of with 180mm fans. I hope they don't pull the case across the room. ;-) I expect to be able to watch the temps drop as I adjust the fan speeds. If I can run these fans at half their rated speed, they will be inaudible. Mind you, I'm in the New Mexico desert, and I've had no heat problems so far (this will not be my first big box).
I separated the hard drives and part of the cooling from the motherboard and its cards, the smaller power supply runs the hard drives and part of the cooling system and the larger one runs the rest
Ah HA! You made a mongo case! You doubled the available cooling air, for one thing. Very innovative!
This is the case
https://www.amazon.com/gp/product/B00TQI9BY8/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
That's a big case. My own is a bit more tradional.
This is what my other systems are in https://www.newegg.com/p/N82E16811147245?Item=N82E16811147245
Rosewill makes good stuff, I like them.
Robert Freise, nice system. I'd like to have one like that someday, but I don't think my air conditioner would approve. It has enough trouble dealing with the heat here in the Carolinas. My room gets pretty hot with just a Ryzen and a 1080ti.
This weekend I decided to take another try at rendering a Daz Studio scene on my Raspberry Pi. I had cooling issues before, but I got those straightened out (desk fan).
I was hoping to render a Genesis 1 figure with clothes, but I don't think it's going to happen. Even though the textures for the scene only came to about 65Mb, it caused Blender to crash no matter what I tried. I think that PBR renderers uncompress the textures when they load them which takes up a tremendous amount of space. So the only way to make it work would be to resize all the textures to a much lower resolution which I'm not really interested in doing.
Other than that the biggest challenge was copying the texture files over to the Pi and making sure Blender could find them.
I did complete a render of the Daz material ball this time and it only took 22 minutes, compared to 15 seconds for the 1080ti.
Hardware: Raspberry Pi 3B+ 1.4Ghz 4-core, 1Gb RAM
attempt 1:
attempt 2:
Careful, I killed* my last system (bought before I got into Daz), by trying to run an Iray and 3delight** render simulteaneously on a hot day.
** 3delight running on a terminal in linux using rib file, while Daz did the iray in wine.
* A Compulabs Fit-PC 4, passively cooled. She went before her time, poor thing.
Oh I made sure to keep an eye on the temp. Before, it was too hot to touch the heatsink, but with the fan, the temp didn't go above 56C. If I ever get a Pi 4 I'm definitely going to get a fan with it.
Hi there!
I updated my system (stupid, stupid me!) and now my Daz Studio (4.10) is broken. After showing the launch window for a second it crashes. This is what the console says:
~ $ wine .wine/drive_c/Program\ Files/DAZ\ 3D/DAZStudio4/DAZStudio.exe
002c:fixme:winediag:__wine_start_process Wine Staging 5.13 is a testing version containing experimental patches.
002c:fixme:winediag:__wine_start_process Please mention your exact version when filing bug reports on winehq.org.
0044:fixme:x11settings:X11DRV_ChangeDisplaySettingsEx Changing non-primary adapter L"\\\\.\\DISPLAY2" settings is currently unsupported.
00b8:fixme:heap:RtlSetHeapInformation 0000000004020000 0 000000000111E770 4 stub
00bc:fixme:file:NtLockFile I/O completion on lock not implemented yet
00b8:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
00b8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute
00b8:fixme:win:FlashWindowEx 0x111e7e0 - semi-stub
00b8:fixme:heap:RtlSetHeapInformation 000000000E8F0000 0 000000000111EE60 4 stub
00b8:fixme:nvapi:unimplemented_stub function 0x1053fa5 is unimplemented!
00c4:fixme:ver:GetCurrentPackageId (0000000029E8FE40 0000000000000000): stub
00c4:fixme:nvapi:unimplemented_stub function 0xd9930b07 is unimplemented!
00b8:err:ole:CoGetClassObject class {82c5ab54-c92c-4d52-aac5-27e25e22604c} not registered
00b8:err:ole:CoGetClassObject class {82c5ab54-c92c-4d52-aac5-27e25e22604c} not registered
00b8:err:ole:create_server class {82c5ab54-c92c-4d52-aac5-27e25e22604c} not registered
00b8:fixme:ole:CoGetClassObject CLSCTX_REMOTE_SERVER not supported
00b8:err:ole:CoGetClassObject no class object {82c5ab54-c92c-4d52-aac5-27e25e22604c} could be created for context 0x17
00b8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute
00b8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute
00b8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute
00b8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute
00b8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute
00b8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute
00b8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute
00b8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute
00b8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute
00b8:fixme:seh:dwarf_get_ptr unsupported encoding 9b
00b8:fixme:seh:dwarf_get_ptr unsupported encoding 9b
00b8:fixme:seh:dwarf_get_ptr unsupported encoding c1
00b8:fixme:seh:dwarf_get_ptr unsupported encoding 9b
00b8:fixme:seh:dwarf_get_ptr unsupported encoding b1
00b8:fixme:seh:dwarf_get_ptr unsupported encoding bd
00b8:fixme:seh:dwarf_get_ptr unsupported encoding 9b
00b8:fixme:seh:dwarf_get_ptr unsupported encoding b1
00b8:fixme:seh:dwarf_get_ptr unsupported encoding bd
00b8:fixme:seh:execute_cfa_instructions 1d080: unknown CFA opcode 2e
00b8:fixme:seh:execute_cfa_instructions 1d080: unknown CFA opcode 20
I'm assuming fixme means 'warning' (but I could be wrong). Focussing on the few lines with "err" points to 'CoGetClassObject' errors. I googled that and used winetricks to install mdac28. That didn't help. Then I tried to install jet40, that failed(?) with: "01ac:err:ole:TLB_ReadTypeLib Loading of typelib L"C:\\Program files\\Common files\\Microsoft shared\\dao\\dao2535.tlb" failed with error 2"
However, retrying yields "jet40 already installed, skipping" so I'm not sure it failed. I'm not even sure jet40 would be required.
The funny thing is, before updating wine, same installed DAZ version worked fine, so I don't understand how it could suddenly require something now that it didn't have before... so maybe I'm looking at the wrong place.
Anybody any idea I could try?
After making sure you reboot after a big update, and it still doesn't work, you might try downgrading Wine-staging back to a previous versions -
ubuntu - how to downgrade a package with apt
I've been having intermittent issues with Wine in recent releases (being on a rolling distro, wine updates point releases frequently) 5.10 and 5.12 were both problems, rolling back to previous wine version in both cases,corrected the issue.
Daz Studio frequently becomes unlaunchable due to problems like this for me due to Archlinux busy and continuous release schedule, it usually clears after a day or two.
An alternative to try - and I did this for a month or two last year - is to launch dazstudio.exe from 'wineconsole' (usually for cli programs) instead of 'wine' - for some reason last year, using 'wineconsole' worked while 'wine' resulted in a crash for some time.
Hm. My distro left me with the choice of 5.10, 5.11, 5.12 and 5.13, no older version. From your reply I can't deduce if you skipped 5.11 or that 5.11, as opposed to 5.10 and 5.12, was okay?
Hm. funny. For me that gives no change though. What I just now tried is switching back to 5.13 vanilla; that works: Daz Studio launches. Alas without GPU support so it's not a solution for me. But it would indicate that the prerequisites are all there... I'll try all older versions, starting with 5.11.
Thanks
Problems with 5.10 where I rolled back to 5.9 then it was ok. I then refused to let it upgrade to 5.10-1 or 5.10-2 (yep, Arch gets every single update from upstream). I gave 5.11 a chance, and it was fine. When 5.12 was released - exactly the same problem as 5.10, so I dropped back to 5.11 and waited for 5.13 (currently on 5.14-2.
My experience is no guarantee your's will work the same way though.
Vanilla?
Do you mean the distro repo version (as opposed to a PPA) or do you mean plain Wine (and not staging).
By 'no GPA support' do you mean Iray (Cuda) or OpenCL and hence dForce?
The latter, I find I need to run clinfo (the linux native version, not the widows version inside wine) in order to 'wake up' the Nvidia as to OpenCL before running Studio. If I don't, dforce isn't available if I go looking for it, and I have to save, quit, run clinfo and restart studio and load the scene again.
I've only set up the old 4.10 iray plugin inside a backup Studio 4.12 prefix install of Daz...I've mostly written off Iray GPU, even if it is working, my scenes generally blow GPU memory anyway.
Thanks. But were your troubles a total inability to launch the program, or other instabilities?
So far I've tried 5.10 and 5.11, no luck. I did observe peculiar things though. The first time I try to launch DAZ studio after a wine version switch I get errors that do not appear at subsequent runs. So those might be significant:
00b4:err:setupapi:create_dest_file failed to create L"C:\\windows\\system32\\atl100.dll" (error=80)
00b4:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
0120:err:setupapi:create_dest_file failed to create L"C:\\windows\\system32\\atl100.dll" (error=80)
0120:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
These only appear at the first run attempt. It is 100% reproducible after switching wine version.
Heh. No PPA's here, I'm on a rolling distro like you are, but it is not arch. My distro offers wine-vanilla and wine-staging, and they can all coexist next to each other. There is a mechanism that allows me to choose the active one.
They are thus distro-packaged versions, not directly from upstream.
Never used dforce. Yes I meant the former, iray (cuda). This is also why I am still using DAZ 4.10. I don't want to lose that recently (for me) gained feature of GPU rendering.
My card has 6GB. Frankly I haven't experienced that yet, running out of GPU memory.
Program failed to launch, just spewed out some output to the terminal
Sorry, I can't keep straight what distro people are runnning - I did try to flip back through the thread to see if I could find a reference in one of your previous posts, but my net is slow today.
If you are on Manjaro, it's a similar base as Arch, same package manager 'pacman'
GPU rendering: maelstrom posted a fix for that several pages back - make a wine prefix for a Studio 4.12, install Studio, and copy over the iray files `DAZ 3D/DAZStudio4/plugins/dzirayrenderer.dll` plugin file and `DAZStudio4/libs/iray` folder from 4.10 to 4.12.
I don't use it much myself (as I usually use the BETA) and as I said, I usually blow the GPU memory.
I do large scenes with as many figures as I can squeeze in
Aww shit, that sounds awfully similar yes.
I've tried to fix the "vulkan" thing but frankly it is more likely that it is unrelated so didn't put much effort into it. I also checked for updates: now 5.10 is gone and 5.14 is added. I'll try that but I'm not holding my breath.
I guess at this point might as well load up DAZ with wine vanilla, see if that works stable, and perhaps try how bad CPU rendering really is on a Ryzen...
I never mentioned what distro I use. It doesn't strike me as important, as I am not seeking support for my distro, and I'm familiar enough with my distro to translate any hints/tips to the correct commands for my environment.
I'm aware of the workaround, I just haven't gotten around to it and there are more pressing things I want repaired in my DAZ, like the content/database thing that is fully broken here. I'm going insane trying to find my content. I'm completely amazed that DAZ either doesn't seem to have a function to bookmark favorite content or offer a search function, or that such functions are tied to the content database working. I've apparently never succeeded in getting that working. I have a working database connection, but stuff just doesn't get populated. In any case, the update to 4.12 was not even on my to-do list yet.
Hm interesting. 5.14 brought changes. Now there is no early abort, there is a "please wait" box on screen for a long while (10-30 seconds) and then a "Daz Studio encountered a fatal error, and must close" box.
So no resolve yet, but there is certainly some movement.
I often get a vulkan error even when Daz is working.
Depending on the the scene, CPU processing on a Ryzen isn't half bad - well lit, HDRI scenes I usually get good results in under an hour - sometimes a half hour. I think I'm more than happy to put up with longer render times to have a more native graphics driver experience.
Well, there aren't many rolling distros compared to release based ones (but looking, more than I thought). If it's on a slower update ring than Arch. you might indeed be encountering the wine release problem that cleared on my system a week or so ago, but not knowing which, it's difficult to say for certain.
I didn't find Smart Content particularly helped as regards finding content - it suffered most the same problems as the Content Library as many products are sloppily tagged - e.g. the main Daz draw, the figures are often dumped in varied locations, some in 'People', some in 'Figures' and stylized, animals and robots can be in all sorts of non-relevant tags. Smart doesn't index older content, so anything in the Poser 'half' or runtime is ignored.
Daz should have implemented a shared library update system so when one user flagged something in a bad category, the correction gets logged, reviewed and then shared.
I ended up going through the runtime manually creating soft links to build up a properly categorised tree structure inside the Props / Environment folders and correcting (two panel FM or two FM windows open next to eachother, it's not too onerous to go through folders collecting (i.e. Sci Fi props into a ! Sci-Fi folder in props) (I didn't try to separate props from Environments, as so many props that aren't scenes keep getting filed under Environments. Runtime side, I also linked Pose Materials and Clothing props (i.e weapons, hats) into the Clothing folder, gathered all Hair under Hair folder (some were originally in Character and parent too hair props are in Props) along with Pose mats (some older hairs stored non Poser materials in the Materials folder - nothing in Materials should be needed by Daz studio folks, it's for Poser materials.
Yup, it's an overhead, having to update links for new bought content, doubly doing it first time - but I went through in waves, categorising most used themes first.
Pop! OS has Smart content working with Wine out of the box, no need to sort out a Postgresql db linux side. You have been installing with DIM (or the new installer)?.
If Studio isn't popping up with a CMS connection error on launch, it can find the CMS db, it's just not populated - you could access the db refresh from the Triangle menu on the Smart Content Tab/pane - see if that works.
OK, looked up a forum thread...
5.10 is gone? I guess I'm used to arch, which keeps minimum of 3 old versions in the local repo (I was tempted to allow more previous versions, but it can only do it for all, not per package). Even so, I've taken to keeping a copy of the latest working wine-staging package in /home, just in case I clear the package cache at a bad time.
'Please wait...' - Yup, it's crashed at this point (I hate how the crash report preparation seems to take a hell of a lot longer recently. Used to be less than 30 secs, now you can wait a moment or two)
Yeah. I figured that might be a wild goose chase, unrelated to my problem.
Same-ish. As of yesterday, they offer wine-staging in 5.11, 5.12, 5.13 and 5.14 versions, and wine-vanilla in 4.0.3, 5.0.1, 5.0.2, 5.11, 5.12, 5.13 and 5.14. So plenty of choice.
I guess I have to test how bad rendering via CPU is. I did some quick tests yesterday. but Daz was very unstable, I could not load an existing scene so I rendered a scene with one figure and one prop on transparant background plus headlight, so that offers no usable benchmark.
I tried following a "reorganize your DAZ content" howto but it depended on the database working. I guess everyone wants their own personal approach. For example, are special poses to pose a figure on a prop more logical under the prop, or under [poses]? Or both places via an alias? Furthermore, vendors and users have opposite interests. A vendor might want his handcuffs located under [props]"Law Enforcement Procuration Services inc." whereas I just want them under [props][restraints][metal]. So that has no one solution. But the absence of a search function is unexcusable. I find myself using grep -ri ~/Documents/Daz 3D/ to locate things deemed lost. That's insane.
I tried this a while ago. The problem is that it, if I remember correctly, reports that the command has been executed succesfully, but when checking with psql nothing changed. Like it just was using a shadow database. But If I shut down the database, I would get errors, so it did talk to my instance. Stuff to make you pull your hair out.. :(
So, which version had youn installed when Daz last worked?
That'd be my strategy, if I was desperate to get it working again, otherwise I'd try them all (I'd be less likely if I were using Gentoo though - all that compiling)
I don't find it too onerus on my Ryzen 7, as long as it's not a low light indoor scene
Daz has a search, at the top of the content tab/pane - you have to change the little disc drum icon as, i think, as it's usually set to db search, not file search.
I don't use it - it used to crash Studio fairly regularly on Wine - but that was ages ago (2017), I've not tried it in a year or two.
Hmm, might be worth going over your postgresql setup again.
Did you check the port you've told it to use is actually open by default on your distro? - I'm not sure whether it'd detect postgresql CMS running ok (and not give an error) even if the port to the outside is closed
You could try using the triangle menu and selecting the 'search for content' button (can't be more exact, running render, so can't refer to studio for exact) - I used this to populate all the content in runtime into the db - a lot of work though, without the db files that come with most modern Daz content, it doesn't know which is material, and which prop etc. Lot of work assigning categories.
As far as Iray software rendering goes, what I lost in performance, it made up for in stability. No more driver issues, I haven't seen any memory leaks(yet), and not having a VRAM limitation. But I have a Ryzen 5, so things get pretty slow sometimes.
I've been using it and it works ok, at least the db search. I never tried the file search.
So far a life passed since the needing of DAZ for linux has born.
No releases for linux were made even if there was a request (so actually it seems to be not a priority for the DEVs).
So in the end have anybody of you found a workaround to make it work on linux with GPUs? :(
The decison to devote resources to developing a Linux version would have to be made by management, not the devs.
I'll bite. How might we get managements attention?
File a ticket
@Kyan001
I don't expect a dedicated Linux version is particularly likely.
Linux marketshare as a desktop/user OS really isn't big enough for the effort to be worth it in any extra store sales.
Studio works well enough through Wine, luckily - and certainly Studio on Wine has improved greatly since 2017
Another user posted a workaround a few pages on this thread back on getting Iray GPU rendering.