Daz Suddenly Crashes When Loading G8F
h_3858391
Posts: 42
Hi everyone,
Had a very sudden and major problem with Daz studio. Whenever I load any G8f character (preset, base, dev base) DS crashes. G8M, G3F adn G3M all work fine. I have updated my graphic card driver, cleared my temp files, cleared DS's DSON Cache, uninstalled and reinstalled some G8F characters and even un and then reinstalled DS, all to no avail.
Havent bought anything new, was working perfectly alright earlier today and then suddenly crashes 100% of the time. Opened a ticket but its 4-6 weeks wait for a response and I can't really use DS atm.
Anyone have any help?
Thanks in advance
Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Have you checked the log (%AppData%/daz 3d/studio4/log.txt) after the crash to see if there are any errors 9it's quite possible there won't be)? Have you tried using a different version (the beta if this is in the General Release)?
There is hundreds of lines similar to this one:
WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(6843): Could not find target property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/DAZ%203D/Expressions/eCTRLHappy_HD.dsf#eCTRLHappy?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/DAZ%203D/Teen%20Raven%208/eJCMTeenRaven8_Happy_HDLv2.dsf
Should I just start going through my paypal and requesting refunds on every Daz purchase or is there a way to make the items I paid for actually work?
Those are warnings, not errors. They mean you have some characters including correction morphs for other morphs you don't have installed (in your example, Teen Raven including a correction morph for a HD smile morph).
Are there actual errors in the log?
I'm not sure. Ctrl=F "error" brings up the following though:
2021-04-22 07:33:39.290 Error writing author data.
2021-04-22 07:33:39.308 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(480): Could not add path: "C:/Users/User/AppData/Roaming/DAZ 3D/Studio4/shaders/iray". Due to unknown error -2
2021-04-22 07:33:39.308 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(480): Could not add path: "C:/Users/User/AppData/Roaming/DAZ 3D/Studio4/temp/shaders/iray". Due to unknown error -2
WARNING: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed
Edit: Searching through the CloudLog I found these as well:
2021-01-07T14:29:28Z Startup
2021-01-07T14:29:28Z Query (SELECT * FROM "customer") failed with exception: ERROR: relation "customer" does not exist
LINE 1: SELECT * FROM "customer"
Error in metadata for product 'Armchair Poses and Prop for Genesis 8' (68631), metadata for file 'people/genesis 8 male/poses/atgl/armchair poses and prop/app 024.dse' has no corresponding file
2021-01-29T02:42:59Z Error in metadata for product 'Claudia Hair for Genesis 3 and 8 Female(s)' (56911), metadata for file 'people/genesis 3 female/hair/oot claudia hair/mats/claudia hair base xp color 01.duf' has no corresponding file
2021-04-22 07:33:39.290 Error writing author data.
Could be a permissions issue, try running Daz Studio as administrator...
Steve.
thanks for the tip. When trying to run as admin:
"Daz Studio cannot be run with elevated permissions."
When Daz crashes, sometimes a window pops up with an "Exception Reason":
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Windows\SYSTEM32\ntdll.dll" at 0033:00000000E507A16F, RtlCreateTimer()+1055 byte(s)
If I'm not mistaken though the .dll changes each crash, and the listed one above is just the one that happened to appear this crash.
"DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\tbb.dll" at 0033:00000000022E94EE, tbb::interface7::internal::task_arena_base::internal_max_concurrency()+16382 byte(s)"
Running DS as an administrator is a bad idea as it can cause permission problems for the next time you use it. And IIRC you can't even do this with recent versions of DS.
OK those look more like actual errors. If you check permissions on that folder, what do you see? IIRC there have been cases where a Windows update had set some DS technical folders to readonly, which caused problems.
Those "Could not add path" can be found in just about every log. One can be added manually, but DS deletes the other one if it's there.
Okay, "..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(480)" I don't know where that is and can't find any of the folders in a search.
"C:/Users/User/AppData/Roaming/DAZ 3D/Studio4/shaders/iray" and "C:/Users/User/AppData/Roaming/DAZ 3D/Studio4/temp/shaders/iray" don't exist.
The relevant errors would be at the end of the log, assuming you open it just after DS has crashed and before restarting the application.
No error after the warnings but there was this even though I was just opening a base G8F figure.
"2021-04-22 22:34:49.266 Begin Loading Character Addons...
2021-04-22 22:34:49.291 Loaded Morph Deltas in 0 min 0.0 sec.
2021-04-22 22:34:49.291 Loaded file: XT_Chen Ting Head.dsf
2021-04-22 22:34:49.308 Loaded Morph Deltas in 0 min 0.0 sec.
2021-04-22 22:34:49.308 Loaded file: XT_Chen Ting Body.dsf"
Sounds as if there may be a character with a non-zero default, and perhaps corrupt data that is causing the crash (or it may be unrelated to the crash). That isn't a Daz character so you will probably need to find the files and manually remove them, then see if DS will load the base figure.
The Chen Ting character has worked fine plenty of times in the past so I don't think that's the problem. Still I have removed them from my library and crashes remain.
The only thing I can think of is I may have used X-Transfer to transfer the G3F Chen Ting figure to G8F but didn't realise there was already a G8F figure, but I don't know how to remove the X-Transfered version which I'm assuming is causing the problems. I uninstalled X Transfer but the crashes still occur.
Edit: Found the XTransfer files and deleted all of them, at least I think so anyway. Everything seems to be working again now as far as I can tell. Big relief and big thanks to everyone who helped.
im having this issue now and nothing is solving the issue. where do you find xtransfer files???