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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Subjectively, after a few days of use, the latest (4.12.1.118) seem a bit more prone to crashes or I may be holding my mouth wrong. Anyone else notice? Meanwhile, saving early and often.
I have 2. questions , why it install outside Program Files ( unable to use my GoZ plugin ) even if I put it in the plugin folder, once I close the app it remove the plugin by it own.
My installation went into C:/Daz 3d/Applications /
very unusual location , I can't even manually remove it and my weekly software backup don;t want to include it together with my library , it just skipping the whole folder
why?
Cath
How are you installing? Are you using DIM? Did you check and verify the application instlation paths in DIM, if that is what you are using? I hope you aren't using the new Daz Central, because a lot of people have had that redefine their paths and they ended up with lots of problems.
I used the Daz Central and I run in troubles I had to reset my PC this morning to early point , my system freak out some how shutting off and on until I get rid of everything manually, no way I could uninstall this normal way.
My old Library is on my backup HD so nothing lost. I am going to install again using DIM with the traditional path so I can make backup
Thanks for the tip
With me, Studio doesn't really crash often but it does freeze VERY frequently (ten or twelve times today), and I have to close it with Task Manager (Windows), and so I'm tending to use the more stable Beta.
I have tried waiting up to an hour for Studio to 'un-freeze' itself, but that did not work. And it can freeze with any scene including just a basic figure that I'm setting up with textures and clothes (Genesis 8 down to Genesis 1). As far as the error logs are concerned, nothing went wrong.
EDIT TO ADD: My PC has an i7 processor with 32G of RAM and a GTX-1080 GPU.
I get the reder error for Iray, even after upgrading my drivers
Just wish for once they had a crew that could make the software actually flawless or close to it in some way. Something in DAZ is always dying out or breaking
I mean I downloaded to 4.12 from DAZ CENTRAL and now I can't even have no more than one window of DAZ open, the vignetting dont even work anymore either (not that I was using it a lot). I use to be able to have multiple Daz windows open. So if one is rendering an image, I can be working on another image in another window of DAZ. But not anymore...I cant even completely close the program down unless I do it through the Task Manager...It just seems like no one really knows what their doing with this program because there is always something wrong with it. A lot of stuff just feels disabled or non-working, and the beta versions are always the complete version when the complete version is suppose to be better than the beta. Which means all the issues with the beta is going to be in the "complete/finished" version...Not being able to have multiple DAZ windows open is already a disappointment...
Daz changed the way you can open multiple instances, because the old way could cause problems due to all instances sharing some technical folders (for example one instance could sometimes overwrite or delete temp files used by the other).
It's still possible to launch multiple instances, just not directly. There are instructions there: https://www.daz3d.com/forums/discussion/comment/5112696/#Comment_5112696
and one user posted powershell scripts to do it easily here: https://www.daz3d.com/forums/discussion/comment/5620181/#Comment_5620181
One can still create instances by using the script posted at the end of this post:
https://www.daz3d.com/forums/discussion/comment/5112696/#Comment_5112696
As for the dark scene, did you check the Render Settings? If you set it to Defaults, it should be fine.
I made the same mistake , it did not worked messed up everything , uninstall it and use DIM for the real instalation , you will have 80% less problems , I did works better , but as you said, Not being able to have multiple DAZ windows open is already a disappointment
but there is a script for I believe , but why make easy stuff difficult , they must have a reason .
Thanks a lot, I was just searching for that !
Installed fine. All free starter content installed fine. No free starter content (including Genesis 8 starter essentials) will load. Complains about internet connection to do with postgre sql or w/e. i made simple custom firewall rules allowing all active processes for this program and it still says it can't load the content due to no connection.
i was wanting a pro pack, admittedly for the bits, but if i can't even load the FREE stuff without an internet connection i'll keep using character creator. i'll check you all out in another year or so.
I think what is happening is that the content managment system isn't seeing the files as installed, so when you double-click it reads that as a request to download and install and pops-up a log-in dialogue. If you look at the Starter Essentials in the products tab of Smart Content do they have a greyed-out thumbnail (not installed) or a coloured icon, and if they have a coloured icon do they have a circled triangle icon at top-right?
Only after recently using DIM, which I usually don't, as installs with it are taking up more space than a manual install, I realized that 4.12 was available. I'd seen 4.11 and 4.12 listed on product pages, but I've been totally neglecting paying attention to my Daz version, just checking for updates through DS, so I'm still using 4.10x.
So, I'm wondering if I should update or not. And I'm using MacOs.
My suggestion would be to get the public build beta 4.12 and install that alongside your current working 4.10, that way you can test and see if you actually want to update.
Because of the Apple-NVidia feud, GPU rendering in Iray won't work in the latest release (4.12.1.118).
Thank you for this, if I had absentmindedly just installed 4.12, I would not have been able to use 4.10 to delete keyframes that I cannot delete in 4.12 (at least not without first figuring out where to redownload 4.10).
Thank you. I'm using 3DL almost exclusively with Daz, as I have found Iray to be far too slow (not a complaint about the quality of the iray renders I'm seeing from people who do use it), and my comp is a 2015 with a 3.1 i7 cpu, and intel gpu, so I think I'll definitely avoid iray with 4.12.
That may be ending soon with Nvidia being the only offering company to buy up ARM and with Apple's move to ARM processors/Architecture which is licensed from ARM. If it does happen and Nvidia gains control of ARM processors- it could likely mean a very large shift in Apple's computer design (which will end up being a good thing for everyone).
Hi - I have been investigating this issue. It is still happening on 4.12.2. I think I know why....
The plugin calls DzMainWindow::addShutDownCheck(DzShutDownCheck *check) to register a DzShutDownCheck function.
DzMainWindow::addShutDownCheck(DzShutDownCheck *check) is defined in dzmainwindow.h of the 4.5.0.114 SDK. However it is not documented in the 4.5.0.114 SDK documentation.
DzShutDownCheck is also not documented.
Is it possible the DAZStudio 4.12.2 has changed the behavior of the DzShutDownCheck?
Paul
Posted in Nuts n Bolts, but see that this thread is covering issues 4.12.1.118
1) Following update none...NONE...of my Dforce Hair products work in Iray render, nor does Line Tesselation have any affect on Texture "Preview" or Iray render (Interactive & Photoreal)
2) Every Time I attempt to close Daz programk - File>Exit, or "X" out of program, I cannot reboot Daz again...UNTIL I manually go in Win10 Process manager and close out a running Background process of the Daz application. It NEVER closes on its own
Worked before update normally.
-The Background process at least I can work around, so I don't really care about it.
-The Dforce one sucks, because nothing is working. I can seemingly adjust Line Tesselation from 0 to as high as 12,000+ with no effect, I remember before that it would change things at 2-3. Also, there was no new "Dforce starter essentials" so I uninstalled and reinstalled it, but still nothing working good. Feels like Update broke it.
UPDATE: to my above post, I tried using the 4.12 Beta I have, and all of the DForce works properly, both render by Iray and effect by Line Tessellation slider adjustment.
Also when closed, it closes itself ouit of the Process Manager like you would expect. So both of my listed items work in Beta, but not on latest release. But all on same machine...That's weird, right?
UPDATE 2:
I compared settings in my Beta vs Pro related to Dforce in action during session:
A) for the products themselves - 1) Parameters, 2) Surfaces
B) for the engine itself - Simulation Settings, Render Settings
I have found both are identical in every listed node and attribute parameter. I follow the same steps and can replicate detachment of the Dforce product from the character on both Beta and Pro, so you get a rather shapeless Dforce product floating in space, exactly the same.
But when attaching the Dforce products to the character, this is when there is a difference - the Beta responds and shows a difference of the Dforce shape in the Texture Preview, and also likewise renders it as you would want. But, the Pro does not; like it just never connects the product in display even though the object is conneted to the character in the scene menu. I am wondering if there is a technical point breakdown between the scene menu and the display for the Dforce setttings in the Pro, such that the menu shows it as being attached to the character, but it really is not being attached. Like, the menu is showing what you want (attached), and the display is correctly showing you what you actually really have (detached). Just somehow the Scene menu and the display are not talking to eachother for Dforce.
If anyone has any suggestions for what else engine-wise I could compare the Dforce-working Beta vs the Dforce-non-working Pro, I am very ready to take your guidance and troubleshoot comparitively. I have a feeling the Pro-update has a bug which is presenting on my system in the form of Dforce, because the fact that Pro won't, when closed, release its used memory and close out of the Win10 Process manager, is weird. Maybe that is tied into the Dforce running some ongoing unfinished process that never completes or something.
Check to see if you have the same plugins installed and activated in each one. (Help>About Installed Plugins)
Check to see if you have the same plugins installed and activated in each one. (Help>About Installed Plugins)
Hi, thank you for taking interest and for providing your suggestion. I have found that most of th plugins are different versions. I had 2 enabled in Pro not found in Beta (Alembic, and GoZ). I disabled these and then found that nothing changed, I also was thinking maybe that I could try using the Dforce Smiklution plugin from th eBetya and put that in the Pro folder, to see if that would make a difference.
It was by chance while navigating that I randomly noticed that I had some surface selection tool on the character when I dragged the pointer over it, like I couldn't pose the character limbs. So I clicked on / switched to the Universal tool and BOOM!- all of the sudden the look of the Dforce products showed, and now work! I can even suddenly render with Iray in Pro, no problem with Dforce! Now, when I close out Daz it stil shows as using memory in the Process manager, which is weird. But, it seemed that switching to the Universal too to pose the character activated evrything back to normal. I don't know what mode it was on after the update, it was some face-selection tool, and I had not yet tried posing a character's limbs with the Universal tool. Kind of a fluke, but AWESOME that you gave me the incentive to explore the tools beyond what I had already done.
If anyone has a Dforce issue make sure you are using the Univeral tool on your character, it may get it working.
Barbult, Thank You!
Good that it is working for you now. When you update Daz Studio to a new version, you also need to update the Daz Studio Plugins to match. So, it makes sense that the release version and the beta version might have different plugin versions. Just be sure that you have updated those plugins to match the Daz Studio update that you did.
There are documents in the zip with the headers. As for the behaviour having chnaged, I'm told not and it seems that there's little to change since these features are used by the plug-in developer to clean up their code on close: