Genesis 8 Female 30+ minute load time

mathiasdeckman

Hi All,

So I've been very reluctant to use any Genesis 8 Female figures for a few reasons, but the main one is that it takes between 30 to 40 minutes to load a single base model female figure. Not only does it take 30+ minutes, but it also comes with the "Duplicate Formula" thing (of which I've grown acustome to with G3 Figures in my library and not worried). While I can deal with the Duplicate formula error, I cannot deal with it taking 30+ minutes to load a single base G8F figure.

Where as, I have another scene that is 900 Megabytes in size, multiple Genesis 3 Figures, dozens of articles of clothing- some with revamped and custome textures, and it takes 20 to 25 minutes to load. I can easily understand this G3F file taking 25 minutes to load, but I cannot understand nor accept is a single, base model Genesis 8 Female figure taking 30 to 40 load. (A single G3F model takes only a few minutes. It used to take seconds until I upgraded to 4.10 from 4.9- but that's another can of worms.)

Can someone please explain to me why this is? I have the latest daz studio 4.11 version, latest updates and drivers, along with enough computational horse power and RAM to launch a Nasa shuttle.

Any and all help to getting this load time cut down to less than 5 minutes would be greatly appreciated. Thanks.

Apologies if this is the wrong section.

Penguinisto

Please further define this part:

"...enough computational horse power and RAM to launch a Nasa shuttle."

The issue might be disk I/O-based... are you using an external drive (like over USB, perhaps?) What do the logs say (Help -> Troubleshooting -> View Log File)? Are you getting a ton of errors in your OS event logs?

These are but a few places to start...

RayDAnt

mathiasdeckman said:

Hi All,

So I've been very reluctant to use any Genesis 8 Female figures for a few reasons, but the main one is that it takes between 30 to 40 minutes to load a single base model female figure. Not only does it take 30+ minutes, but it also comes with the "Duplicate Formula" thing (of which I've grown acustome to with G3 Figures in my library and not worried). While I can deal with the Duplicate formula error, I cannot deal with it taking 30+ minutes to load a single base G8F figure.

Where as, I have another scene that is 900 Megabytes in size, multiple Genesis 3 Figures, dozens of articles of clothing- some with revamped and custome textures, and it takes 20 to 25 minutes to load. I can easily understand this G3F file taking 25 minutes to load, but I cannot understand nor accept is a single, base model Genesis 8 Female figure taking 30 to 40 load. (A single G3F model takes only a few minutes. It used to take seconds until I upgraded to 4.10 from 4.9- but that's another can of worms.)

Can someone please explain to me why this is? I have the latest daz studio 4.11 version, latest updates and drivers, along with enough computational horse power and RAM to launch a Nasa shuttle.

Any and all help to getting this load time cut down to less than 5 minutes would be greatly appreciated. Thanks.

Apologies if this is the wrong section.

How big is your installed content library? Assuming you are like most people and tend to install content sets en masse to a content library folder somewhere and NOT remove them when not needed, you probably have tens (if not hundreds) of gigabytes of files your Daz Studio Content Management System is having to contend with each and every time you attempt to load another individual item. And there are only so many files you can install together before you start eventually running into ID number/naming conflicts. 

Saxa -- SD

mathiasdeckman said:

but the main one is that it takes between 30 to 40 minutes to load a single base model female figure. Not only does it take 30+ minutes, but it also comes with the "Duplicate Formula" thing (of which I've grown

Would say, something is very wrong with your setup.

Takes me exactly 34 seconds to load a new base g8f.  One of my heavily (and I mean Heavy) morphed G8F characters with hair/outfit included in scene-load (before reconverting to a new obj-shape) can take up to 3 minutes.  And I have over 600 GBs of content for Daz alone, never mind other stuff.

If was in your booties, would look at ways to setup a fresh new runtime to test for much better performance.

Also for long-term planning, you may want to consider what is posted in this thread> https://www.daz3d.com/forums/discussion/372136/how-to-load-a-character-faster-solved-with-a-workaround/p1

Richard Haseltine

It could also be down to security software, if every file in the load process is being scanned.

mathiasdeckman

Ok, i'll give my best shot as it's late, so my apologies if i'm short on things.

Please further define this part:

"...enough computational horse power and RAM to launch a Nasa shuttle."

The issue might be disk I/O-based... are you using an external drive (like over USB, perhaps?) What do the logs say (Help -> Troubleshooting -> View Log File)? Are you getting a ton of errors in your OS event logs?

These are but a few places to start...

specs: 1950x threadripper, 128 GB RAM, OS has solid state drive, as well as daz scratch.  Content drive is a 7200rpm, NAS grade 10 TB drive connected directly to the motherboard via SATA 3.  Logs are at end, of what I could find.

How big is your installed content library? Assuming you are like most people and tend to install content sets en masse to a content library folder somewhere and NOT remove them when not needed, you probably have tens (if not hundreds) of gigabytes of files your Daz Studio Content Management System is having to contend with each and every time you attempt to load another individual item. And there are only so many files you can install together before you start eventually running into ID number/naming conflicts. 

The issue started from 600 GB and has stayed consistent up 2.6 TB, so size is not an issue. Clothes take a few seconds, males take a few seconds, G3F takes 5 minutes. G8F takes 30 minutes.

Would say, something is very wrong with your setup.

Takes me exactly 34 seconds to load a new base g8f.  One of my heavily (and I mean Heavy) morphed G8F characters with hair/outfit included in scene-load (before reconverting to a new obj-shape) can take up to 3 minutes.  And I have over 600 GBs of content for Daz alone, never mind other stuff.

If was in your booties, would look at ways to setup a fresh new runtime to test for much better performance.

G3F used to take 3 seconds. I could select a dozen G3F models in 4.9, hit 'merge into scene' and they'd all be loaded in 1 minute. The moment I upgraded to 4.10, I got clobbered with Duplicate IDs, which slowed everything down. (I did read somewhere here that Duplicate IDs were because of a version mismatch in content creation from 4.9 to 4.10- as the issue only started when i upgraded to 4.10.)  The moment I tried 1 G8F model, it took 30 minutes. I actually thought it froze several times. If i were to recreate my library...I'd likely have a panic attack- I've spent way too much time working on getting my library sorted and organized because of content not having a relatively consistent file structure (Daz and Renderosity creators are both at fault for this.)

It could also be down to security software, if every file in the load process is being scanned.

I uninstalled my antivirus software due to other reasons and it still takes 30 minutes for it to open.

So i used a converter to convert 'Jo for G8' to G3 and my time of 30 minutes was cut down to 5 minutes. I tried a Genesis 8 character, it had been 25 minutes before I said to hell with it and killed it. And it will also give me that duplicate ID error. I don't move any files around except for the duf files in people/characters/genesis 3/8. Alright, time for bed.

Log entries:

2019-12-19 22:10:54.352 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis3Female
2019-12-19 22:10:54.352 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: Genesis3Female:/data/DAZ%203D/Genesis%203/Female/Morphs/DAZ%203D/Head/CTRLCheekbonesSize.dsf#CTRLCheekbonesSize?value
2019-12-19 22:10:54.352 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis3Female:/data/DAZ%203D/Genesis%203/Female/Morphs/Anagord/LustGirls/FHM%20Coco.dsf#FHM%20Coco?value

 

2019-12-19 22:15:12.591 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(7841): Could not find reference: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/3D%20Universe/G8F/ctrlMouthOH.dsf#ctrlMouthOH?value
2019-12-19 22:15:12.591 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1451): Failed to create alias!
2019-12-19 22:15:12.620 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5759): Could not find output property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/DAZ%203D/Base%20Pose%20Head/eCTRLEyesClosed.dsf#eCTRLEyesClosed?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/zoro_d/Chameleon%20ROse_Genesis%208%20Female/CTRL_ChRO_Smile.dsf
2019-12-19 22:15:12.620 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5759): Could not find output property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/DAZ%203D/Base%20Pose%20Head/eCTRLMouthCornerBackL.dsf#eCTRLMouthCornerBackL?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/zoro_d/Chameleon%20ROse_Genesis%208%20Female/CTRL_ChRO_Smile.dsf
2019-12-19 22:15:12.620 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5759): Could not find output property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/DAZ%203D/Base%20Pose%20Head/eCTRLMouthCornerBackR.dsf#eCTRLMouthCornerBackR?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/zoro_d/Chameleon%20ROse_Genesis%208%20Female/CTRL_ChRO_Smile.dsf
2019-12-19 22:15:13.872 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5818): Could not find target property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Zev0/Aging%20Morphs%208/Jaw%20Side%20Smoother.dsf#Jaw%20Smoother?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/Zev0/Aging%20Morphs%208/CTRLMD_N_Value_1_AM_Z.dsf

Padone

As @RayDAnt is reporting, this depends on how many morph packages and characters you have installed in your content library. That is, the morph data itself is only loaded when used, but all the dependencies have to be loaded first. What I personally do is to use one library for every project where I only install the assets needed for the project. This keeps things easy and fast.

It has also been reported that 4.12 seems slow to load some morph packages that 4.11 has no issues with. But I don't know if this is your case and/or if this has been fixed in the beta. You may test it yourself.

mathiasdeckman

Padone said:

As @RayDAnt is reporting, this depends on how many morph packages and characters you have installed in your content library. That is, the morph data itself is only loaded when used, but all the dependencies have to be loaded first. What I personally do is to use one library for every project where I only install the assets needed for the project. This keeps things easy and fast.

It has also been reported that 4.12 seems slow to load some morph packages that 4.11 has no issues with. But I don't know if this is your case and/or if this has been fixed in the beta. You may test it yourself.

I'm starting to think it's the amount of morphs and their IDs- as I have hundreds of characters and i read recently that someone has 800 custom characters and doesn't have this issue. I know what you personally do as we debated back and forth at length on other topics. I cannot unload and load different items up for different projects as I have too many projects that I work on and create to keep track of and customized content that would prevent me from doing that anyways (nor do i want to detangle 2.6 TB of data).   I have not upgraded to 4.12 because of the fallback issue and crashing issues.  What i'm very likely to do is isolate the duplicate IDs and try to 'fix' a few of them to see if they show up again (quite frankly there should be an option to ignore them) - then go through and try to get rid of the gargantuin amount of morphs i have for G3F/G8F and see if that lowers my load time(s).  But what gets me is that i have more morphs for G3F than I do G8F and G8F takes 30 minutes, not 5...

ugh, frustrating.

p0rt

buy o&o defrag, and defrag your drive by file name, or put your content library on a SSD or nVME

Ati

There's a solution to this here: https://www.daz3d.com/forums/discussion/comment/5170611/#Comment_5170611

mathiasdeckman

p0rt said:

buy o&o defrag, and defrag your drive by file name, or put your content library on a SSD or nVME

Yeah, shifting 2.6 TB to a solid state drive is not going to happen; there isn't a solid state big enough to hold over 4 TB that i can currently afford or fit into the system. and currently, my 2.6 TB is 5% fragmented.

 

Ati said:

There's a solution to this here: https://www.daz3d.com/forums/discussion/comment/5170611/#Comment_5170611

The morphs it is loading have links going to the ones that are no longer there (presumably you removed the head and body morphs, which are likely to have a lot of corrective links) so the log is telling you that there's an unresolved link - which is harmless in itself, and the log isn't actually written to disk until there's a quiet moment to do so (which is why it sometimes is behind the times if there's a crash) so producing those warnings isn't impacting load times.

I'm in the process of working out problem files. For example; a file called 'lashes.duf' under A&A morphs, created about 2/3s of the warnings in the log file for G3F. I deleted that file and my 5 minute load time went to 2 minutes.  I'm hoping that by repeating this practice, I can drop G8F down to something similar. Currently, 'animation' values are causing G3F problems. Then it's down to Duplicate IDs.

mathiasdeckman

So i took out a few morphs that were causing excessive log file bloat (the first log file was 887 pages in microsoft word 11x17 size). The following are the files that i removed first:

2019-12-20 09:56:10.432 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking xOrigin & LB Zuki Head in E:/Content/data/DAZ 3D/Genesis8/Female/Morphs/Anain&Akasha/Little Beauties/LB Zuki Head.dsf.
2019-12-20 09:56:10.433 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 09:56:10.433 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: hip:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#hip?center_point/x
2019-12-20 09:56:10.433 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Anain%26Akasha/Little%20Beauties/LB%20Zuki

%20Head.dsf#Zuki%20Head?value
2019-12-20 09:59:22.059 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking xOrigin & LB Zina Head in E:/Content/data/DAZ 3D/Genesis

8/Female/Morphs/Anain&Akasha/Little Beauties/LB Zina Head.dsf.
2019-12-20 09:59:22.059 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 09:59:22.059 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: hip:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#hip?center_point/x
2019-12-20 09:59:22.059 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Anain%26Akasha/Little%20Beauties/LB%20Zina

%20Head.dsf#Zina%20Head?value

2019-12-20 10:02:34.252 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking xOrigin & LB Vero Head in E:/Content/data/DAZ 3D/Genesis

8/Female/Morphs/Anain&Akasha/Little Beauties/LB Vero Head.dsf.
2019-12-20 10:02:34.252 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 10:02:34.252 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: hip:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#hip?center_point/x
2019-12-20 10:02:34.252 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Anain%26Akasha/Little%20Beauties/LB%20Vero

%20Head.dsf#Vero%20Head?value

2019-12-20 10:05:50.666 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking xOrigin & LB Mika Head in E:/Content/data/DAZ 3D/Genesis

8/Female/Morphs/Anain&Akasha/Little Beauties/LB Mika Head.dsf.
2019-12-20 10:05:50.666 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 10:05:50.666 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: hip:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#hip?center_point/x
2019-12-20 10:05:50.666 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Anain%26Akasha/Little%20Beauties/LB%20Mika

%20Head.dsf#Mika%20Head?value

2019-12-20 10:09:06.519 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking xOrigin & LB Lola Head in E:/Content/data/DAZ 3D/Genesis

8/Female/Morphs/Anain&Akasha/Little Beauties/LB Lola Head.dsf.
2019-12-20 10:09:06.519 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 10:09:06.519 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: hip:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#hip?center_point/x
2019-12-20 10:09:06.519 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Anain%26Akasha/Little%20Beauties/LB%20Lola

%20Head.dsf#Lola%20Head?value

2019-12-20 10:12:28.614 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking xOrigin & Karina Head in E:/Content/data/DAZ 3D/Genesis

8/Female/Morphs/Anain&Akasha/Little Beauties/Karina Head.dsf.
2019-12-20 10:12:28.614 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 10:12:28.614 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: hip:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#hip?center_point/x
2019-12-20 10:12:28.614 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Anain%26Akasha/Little%20Beauties/Karina

%20Head.dsf#Karina%20Head?value

2019-12-20 10:15:48.145 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking xOrigin & Kala Head in E:/Content/data/DAZ 3D/Genesis

8/Female/Morphs/Anain&Akasha/Little Beauties/Kala Head.dsf.
2019-12-20 10:15:48.145 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 10:15:48.145 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: hip:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#hip?center_point/x
2019-12-20 10:15:48.146 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Anain%26Akasha/Little%20Beauties/Kala

%20Head.dsf#Kala%20Head?value

2019-12-20 10:19:05.887 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking xOrigin & Gigi Head in E:/Content/data/DAZ 3D/Genesis

8/Female/Morphs/Anain&Akasha/Little Beauties/Gigi Head.dsf.
2019-12-20 10:19:05.887 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 10:19:05.887 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: hip:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#hip?center_point/x
2019-12-20 10:19:05.887 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Anain%26Akasha/Little%20Beauties/Gigi

%20Head.dsf#Gigi%20Head?value

2019-12-20 10:22:24.214 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking xOrigin & Dora Head in E:/Content/data/DAZ 3D/Genesis

8/Female/Morphs/Anain&Akasha/Little Beauties/Dora Head.dsf.
2019-12-20 10:22:24.214 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 10:22:24.215 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: hip:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#hip?center_point/x
2019-12-20 10:22:24.215 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Anain%26Akasha/Little%20Beauties/Dora

%20Head.dsf#Dora%20Head?value

2019-12-20 10:25:42.623 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking xOrigin & Dani Head in E:/Content/data/DAZ 3D/Genesis

8/Female/Morphs/Anain&Akasha/Little Beauties/Dani Head.dsf.
2019-12-20 10:25:42.623 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 10:25:42.623 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: hip:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#hip?center_point/x
2019-12-20 10:25:42.624 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Anain%26Akasha/Little%20Beauties/Dani

%20Head.dsf#Dani%20Head?value

It dropped to 10 minutes. I thought "Awesome! I do it again and again until it takes seconds." Boy was I wrong.

Took out the following:

2019-12-20 09:52:15.032 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5995): Duplicate formula found linking yOrigin & FHM_LY_Briallen in E:/Content/data/DAZ 3D/Genesis 8/Female/Morphs/Lyoness/LY_Briallen/FHM_LY_Briallen.dsf.
2019-12-20 09:52:15.032 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5996):     owner: Genesis8Female
2019-12-20 09:52:15.032 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5997):     output: head:/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#head?center_point/y
2019-12-20 09:52:15.032 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5998):     input: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/Lyoness/LY_Briallen/FHM_LY_Briallen.dsf#FHM_LY_XXX?value
 

It went to 15 minutes.  Then took out the following thinking I goofed.

2019-12-20 09:51:20.656 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5759): Could not find output property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/DAZ%203D/Base/PHMMouthRealismHD.dsf#PHMMouthRealismHD?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/Zen3D/Katyusha/f0015-body.dsf

2019-12-20 09:51:20.597 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5759): Could not find output property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/DAZ%203D/Base/PHMMouthRealismHD.dsf#PHMMouthRealismHD?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/Zen3D/Tara/a0005-head.dsf
2019-12-20 09:52:06.755 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5759): Could not find output property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/DogZ%26Zev0/200%20Plus/Nose%20Lower%20Height.dsf#Nose%20Lower%20Height?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/Lyoness/SpicyFusion/Preset%20025.dsf [including presets 01 to 24]

It then took over an hour...

2019-12-21 12:36:37.648 File loaded in 65 min 42.8 sec.

Needless to say, I'm pretty pissed.  Minus the rant I just had, expressing my extreme displeasure with G8F, I'm gonna load back in two files that gave me a 10 minute load time. I'd still like to know why my system takes 10 minutes to load a base figure in while others say it should only take seconds. If you want, I'll attach the first log file and you can have at the 47 thousand lines of log file.

Ati

Try taking out all the morphs like in the suggestion I linked above. Although I didn't start from a 65+ minute load time (oh my...), I went from 4 minutes 25 seconds down to 7.7 seconds.

mathiasdeckman

Ati said:

Try taking out all the morphs like in the suggestion I linked above. Although I didn't start from a 65+ minute load time (oh my...), I went from 4 minutes 25 seconds down to 7.7 seconds.

yeah, now it won't work. <_< reverting back. *sigh*

mathiasdeckman

sylvie1998 said:

This can be caused by morphs with duplicate formulas. I have a very fast computer (it loads G8F in under 30 seconds with a lot of morphs installed), but if I install a certain morph package, that time goes up to 4+ minutes.

Make sure you don't see any duplicate formula mentions in the log and if you do, remove the offending morphs.

I'm currently working on that- the last duplicate formula error that I have for G8F belongs to daphne for olympia; the CTRLDaphne.dsf.  So I redownloaded the content package to see if the creator fixed the issue. It's not fixed, it's still a dsf file, which tells me what i read somewhere else on this site is guaranteed true; not all authors are going to update their stuff every time Daz studio updates/upgrades how it works.  I'm not going to name names, but of all the threads that I've come across that concern users having issues with content- a particular user prefers to throw the blame onto the content creators and users instead of stating that Daz Studio itself is the problem.

Right now, the only errors I have left are for 'could not find output property for formula', then it gives a long pathway. I literally have dozens of them, and they deal with dsf files, something that I read here on the forums is an outdated file type- stated by the same individual, which seems kinda silly since Daphne is a genesis 8 figure. A new figure, using an old file type...oxymoronic really. Maybe the file isn't as outdated as this individual thinks it is and maybe the daz team should think about adding a switch for the program to ignore the dsf file error- since the contents can't be ready by humans...

I've got it down to six minutes with G8F and now 16 with G3F.

I have hundreds, if not thousands of errors for G3F for 'could not find property for animation'.

Seven193

Is there a tool that can split the Daz content library into separate locations or drives?

Let's say I have one big content library, and I want to split it into 3 locations, separated by Genesis generation. So, one location has all Genesis 2 content, another has all Genesis 3 content, and another has all Genesis 8 content.

I was just thinking if one could organize their content this way, you could effectively shut off access to it by removing the path to its location, so Daz Studio wouldn't try to load it.  Shouldn't scenes load faster then?

Richard Haseltine

mathiasdeckman said:

sylvie1998 said:

This can be caused by morphs with duplicate formulas. I have a very fast computer (it loads G8F in under 30 seconds with a lot of morphs installed), but if I install a certain morph package, that time goes up to 4+ minutes.

Make sure you don't see any duplicate formula mentions in the log and if you do, remove the offending morphs.

I'm currently working on that- the last duplicate formula error that I have for G8F belongs to daphne for olympia; the CTRLDaphne.dsf.  So I redownloaded the content package to see if the creator fixed the issue. It's not fixed, it's still a dsf file, which tells me what i read somewhere else on this site is guaranteed true; not all authors are going to update their stuff every time Daz studio updates/upgrades how it works.  I'm not going to name names, but of all the threads that I've come across that concern users having issues with content- a particular user prefers to throw the blame onto the content creators and users instead of stating that Daz Studio itself is the problem.

Right now, the only errors I have left are for 'could not find output property for formula', then it gives a long pathway. I literally have dozens of them, and they deal with dsf files, something that I read here on the forums is an outdated file type- stated by the same individual, which seems kinda silly since Daphne is a genesis 8 figure. A new figure, using an old file type...oxymoronic really. Maybe the file isn't as outdated as this individual thinks it is and maybe the daz team should think about adding a switch for the program to ignore the dsf file error- since the contents can't be ready by humans...

I've got it down to six minutes with G8F and now 16 with G3F.

I have hundreds, if not thousands of errors for G3F for 'could not find property for animation'.

As for file types, .dsf is no longer (since DS 4.5) used for user facing files - it is still the correct extension for most non-user facing asset files in the Data folder tree.

No, PAs will not "update for new versions of DS" - but usually they will fix bugs as they emerge and are reported.

"Could not find output property" is not an error - it means that there is a property in something installed that has a link to a property from a different product that you do not have installed. Usually these will be morph-controller morphs, corrections that enable two shapes to work together. Unless you have every character and add-on for a figure then you are very likely to have a lot of these - they are listed in the log because they might be an error, if soemthing is meant to be linking to an installed proeprty but isn't (due to a typos in the name, for example), so the log entries may sometimes be needed for troubleshooting. Bear in mind that the log is not written while DS is busy, it is held until there is a lull, so writing these entries is not in itself going to impact your load times.

As for your rem,aining duplicate formula - bear in mind that these are very rarely product bugs per se, they are naming conflicts - two products both having a named property that each links to another named property. In this case it's quite likely, I should think, that there's another Daphne shape that has a link to a correction (for something like the eyes close or smile morphs, perhaps) just as Daphne for Olympia does and so, between them, they generate the Duplicate Formulae error.

Saxa -- SD

Padone said:

As @RayDAnt is reporting, this depends on how many morph packages and characters you have installed in your content library.

So how many GB of data are you guys figuring triggers this issue?

I have over 600GB of content as I already posted with extremely heavy morphs and characters, and am not having this issue.

What kind of runtimes do you guys have?  lol that you say this? Really curious.

 

Also, just rebuilt my CMS and DS is way snappier.  Am going to do that more often. 

mathiasdeckman

Richard Haseltine said:

mathiasdeckman said:

sylvie1998 said:

This can be caused by morphs with duplicate formulas. I have a very fast computer (it loads G8F in under 30 seconds with a lot of morphs installed), but if I install a certain morph package, that time goes up to 4+ minutes.

Make sure you don't see any duplicate formula mentions in the log and if you do, remove the offending morphs.

I'm currently working on that- the last duplicate formula error that I have for G8F belongs to daphne for olympia; the CTRLDaphne.dsf.  So I redownloaded the content package to see if the creator fixed the issue. It's not fixed, it's still a dsf file, which tells me what i read somewhere else on this site is guaranteed true; not all authors are going to update their stuff every time Daz studio updates/upgrades how it works.  I'm not going to name names, but of all the threads that I've come across that concern users having issues with content- a particular user prefers to throw the blame onto the content creators and users instead of stating that Daz Studio itself is the problem.

Right now, the only errors I have left are for 'could not find output property for formula', then it gives a long pathway. I literally have dozens of them, and they deal with dsf files, something that I read here on the forums is an outdated file type- stated by the same individual, which seems kinda silly since Daphne is a genesis 8 figure. A new figure, using an old file type...oxymoronic really. Maybe the file isn't as outdated as this individual thinks it is and maybe the daz team should think about adding a switch for the program to ignore the dsf file error- since the contents can't be ready by humans...

I've got it down to six minutes with G8F and now 16 with G3F.

I have hundreds, if not thousands of errors for G3F for 'could not find property for animation'.

As for file types, .dsf is no longer (since DS 4.5) used for user facing files - it is still the correct extension for most non-user facing asset files in the Data folder tree.

No, PAs will not "update for new versions of DS" - but usually they will fix bugs as they emerge and are reported.

"Could not find output property" is not an error - it means that there is a property in something installed that has a link to a property from a different product that you do not have installed. Usually these will be morph-controller morphs, corrections that enable two shapes to work together. Unless you have every character and add-on for a figure then you are very likely to have a lot of these - they are listed in the log because they might be an error, if soemthing is meant to be linking to an installed proeprty but isn't (due to a typos in the name, for example), so the log entries may sometimes be needed for troubleshooting. Bear in mind that the log is not written while DS is busy, it is held until there is a lull, so writing these entries is not in itself going to impact your load times.

As for your rem,aining duplicate formula - bear in mind that these are very rarely product bugs per se, they are naming conflicts - two products both having a named property that each links to another named property. In this case it's quite likely, I should think, that there's another Daphne shape that has a link to a correction (for something like the eyes close or smile morphs, perhaps) just as Daphne for Olympia does and so, between them, they generate the Duplicate Formulae error.

Yeah, my experience with it today told me otherwise. The more errors I encounter, the slower it gets. I get plenty of the 'could not' and it's still several minutes long. Really getting tired of this and the excuses.  Getting ready to just figure this out on my own and report back with my results (and they won't be pleasantly written if things go south). As for the Daphne, I looked at the files, looked at the product, there is only one. And i'm not saying it's a bug, but Daz studio needs another feature added; a 'leave the error alone and move on' switch.

I'm really getting sick of being told it's my library when i'm merely using the content, the software and it blows up in my face. I had absolutely no issues at 4.9. But as soon as 4.10 came down, it blew up in my face. I've been dealing with it for two years. Since Riversoft came out with the G8F to G3F converter, I have a huge inclination to stick to G3F since I have almost no issues with that figure (and with a load time of like two minutes).

 

Saxa -- SD said:

Padone said:

As @RayDAnt is reporting, this depends on how many morph packages and characters you have installed in your content library.

So how many GB of data are you guys figuring triggers this issue?

I have over 600GB of content as I already posted with extremely heavy morphs and characters, and am not having this issue.

What kind of runtimes do you guys have?  lol that you say this? Really curious.

 

Also, just rebuilt my CMS and DS is way snappier.  Am going to do that more often. 

I believe it happens when you have duplicate morphs for the same characters. I took out the duplicate morphs and the duplicate IDs went away.

Richard Haseltine

mathiasdeckman said:

Richard Haseltine said:

mathiasdeckman said:

sylvie1998 said:

This can be caused by morphs with duplicate formulas. I have a very fast computer (it loads G8F in under 30 seconds with a lot of morphs installed), but if I install a certain morph package, that time goes up to 4+ minutes.

Make sure you don't see any duplicate formula mentions in the log and if you do, remove the offending morphs.

I'm currently working on that- the last duplicate formula error that I have for G8F belongs to daphne for olympia; the CTRLDaphne.dsf.  So I redownloaded the content package to see if the creator fixed the issue. It's not fixed, it's still a dsf file, which tells me what i read somewhere else on this site is guaranteed true; not all authors are going to update their stuff every time Daz studio updates/upgrades how it works.  I'm not going to name names, but of all the threads that I've come across that concern users having issues with content- a particular user prefers to throw the blame onto the content creators and users instead of stating that Daz Studio itself is the problem.

Right now, the only errors I have left are for 'could not find output property for formula', then it gives a long pathway. I literally have dozens of them, and they deal with dsf files, something that I read here on the forums is an outdated file type- stated by the same individual, which seems kinda silly since Daphne is a genesis 8 figure. A new figure, using an old file type...oxymoronic really. Maybe the file isn't as outdated as this individual thinks it is and maybe the daz team should think about adding a switch for the program to ignore the dsf file error- since the contents can't be ready by humans...

I've got it down to six minutes with G8F and now 16 with G3F.

I have hundreds, if not thousands of errors for G3F for 'could not find property for animation'.

As for file types, .dsf is no longer (since DS 4.5) used for user facing files - it is still the correct extension for most non-user facing asset files in the Data folder tree.

No, PAs will not "update for new versions of DS" - but usually they will fix bugs as they emerge and are reported.

"Could not find output property" is not an error - it means that there is a property in something installed that has a link to a property from a different product that you do not have installed. Usually these will be morph-controller morphs, corrections that enable two shapes to work together. Unless you have every character and add-on for a figure then you are very likely to have a lot of these - they are listed in the log because they might be an error, if soemthing is meant to be linking to an installed proeprty but isn't (due to a typos in the name, for example), so the log entries may sometimes be needed for troubleshooting. Bear in mind that the log is not written while DS is busy, it is held until there is a lull, so writing these entries is not in itself going to impact your load times.

As for your rem,aining duplicate formula - bear in mind that these are very rarely product bugs per se, they are naming conflicts - two products both having a named property that each links to another named property. In this case it's quite likely, I should think, that there's another Daphne shape that has a link to a correction (for something like the eyes close or smile morphs, perhaps) just as Daphne for Olympia does and so, between them, they generate the Duplicate Formulae error.

Yeah, my experience with it today told me otherwise. The more errors I encounter, the slower it gets. I get plenty of the 'could not' and it's still several minutes long. Really getting tired of this and the excuses.  Getting ready to just figure this out on my own and report back with my results (and they won't be pleasantly written if things go south). As for the Daphne, I looked at the files, looked at the product, there is only one. And i'm not saying it's a bug, but Daz studio needs another feature added; a 'leave the error alone and move on' switch.

I am not saying that the underlying issues are not slowing loading, I am saying writing them to the log is not slowing loading. Nor am I saying that there are two of Daphne for Olympia - I am saying that there is another Daphne installed, perhaps some other Daphne character or perhaps a named shape in a collection of named shapes, and that both Ctrl Daphne are linking to a property (or properties) with the same name - it could be as simple as each driving its on Daphne Head and Daphne Body. The products are not at fault - each will be fine in isolation - but it's having both installed that shows the clash of names. If DS left the error alone what should it do? You wouldn't want the Daphne for Olympia slider to drive both the head and body shapes of Daphne for Olympia but also the head and body shapes for SomeOtherDaphne, nor would you want it rendered inoperable - especially if there was nothing logged to help you figure out what was happening.

mathiasdeckman said:

I'm really getting sick of being told it's my library when i'm merely using the content, the software and it blows up in my face. I had absolutely no issues at 4.9. But as soon as 4.10 came down, it blew up in my face. I've been dealing with it for two years. Since Riversoft came out with the G8F to G3F converter, I have a huge inclination to stick to G3F since I have almost no issues with that figure (and with a load time of like two minutes).

 

Saxa -- SD said:

Padone said:

As @RayDAnt is reporting, this depends on how many morph packages and characters you have installed in your content library.

So how many GB of data are you guys figuring triggers this issue?

I have over 600GB of content as I already posted with extremely heavy morphs and characters, and am not having this issue.

What kind of runtimes do you guys have?  lol that you say this? Really curious.

 

Also, just rebuilt my CMS and DS is way snappier.  Am going to do that more often. 

I believe it happens when you have duplicate morphs for the same characters. I took out the duplicate morphs and the duplicate IDs went away.

 

fastbike1

@mathiasdeckman "I'm really getting sick of being told it's my library"

How else do explain that your load times  for Genesis 8 are extremely long compared to most? I have 628 Genesis 8 characters and 67 different Morph packages, yet I load a gen 8 character in ~ 2min, 15 seconds.

Seven193

fastbike1 said:

@mathiasdeckman "I'm really getting sick of being told it's my library"

How else do explain that your load times  for Genesis 8 are extremely long compared to most? I have 628 Genesis 8 characters and 67 different Morph packages, yet I load a gen 8 character in ~ 2min, 15 seconds.

He either needs to rebuild it, or split it up.  From the very beginning, I had all of my "essentials" content installed in a separate directory. So, if I ever need to update or rebuild the core, I can do that without messing with other content.  But, I guess since he has so much content, he's reluctant to do what it takes to fix it.

With just the core essentials installed, it takes me about 25 seconds to load the Genesis 8 character, from a fresh restart of Daz Studio.

mathiasdeckman

fastbike1 said:

@mathiasdeckman "I'm really getting sick of being told it's my library"

How else do explain that your load times  for Genesis 8 are extremely long compared to most? I have 628 Genesis 8 characters and 67 different Morph packages, yet I load a gen 8 character in ~ 2min, 15 seconds.

I cleared out my genesis 3 morphs folder and the base took 5 minutes to load.

Dave230 said:

fastbike1 said:

@mathiasdeckman "I'm really getting sick of being told it's my library"

How else do explain that your load times  for Genesis 8 are extremely long compared to most? I have 628 Genesis 8 characters and 67 different Morph packages, yet I load a gen 8 character in ~ 2min, 15 seconds.

He either needs to rebuild it, or split it up.  From the very beginning, I had all of my "essentials" content installed in a separate directory. So, if I ever need to update or rebuild the core, I can do that without messing with other content.  But, I guess since he has so much content, he's reluctant to do what it takes to fix it.

With just the core essentials installed, it takes me about 25 seconds to load the Genesis 8 character, from a fresh restart of Daz Studio.

 

I don't have the luxury of rebuilding my library, nor can i split it up. Rebuilding would require a effort that would consume a month of time (160 hours) and find all the vendor screws once more (here and at rendoricity) and reorganize everything.  I can't split it up because the log file indicates genesis 8 files pulling on genesis 3 morphs and vice versa.

As far as I'm concerned, because of the past three days of trying to figure this issue out, I'm going to abandon Genesis 8 character creation (both male and female alike as there are issues with the male as well).  I can only bandaid the problems with what's been said here- i can't ever fix it because i can't fix the fundamental errors - Daz studio 4.11 and it's duplicate formula bs (and lack of switch for it to ignore them) and Genesis 8 idiocracies.  Maybe I'm the guy who's gonna get all the worse bugs at once.

My last piece of advice- Richard; as I googled for answers for my problems with Daz studio- most of them in the forums, I came across many of your posts and found a common thread amongst them. You have been very inclined to state that it's 100% the user's fault and never the software's. Take note that the software was created by human hands- therefore, foullable. Maybe acknowledge that the softare can make mistakes- big ones and that the user isn't always at fault.

RayDAnt

mathiasdeckman said:

I don't have the luxury of rebuilding my library, nor can i split it up. Rebuilding would require a effort that would consume a month of time (160 hours) and find all the vendor screws once more (here and at rendoricity) and reorganize everything.  I can't split it up because the log file indicates genesis 8 files pulling on genesis 3 morphs and vice versa.

Can confirm from personal experience that attempting to "fix" a borked installed content library in the 2+ GB range (much less the 2+ TB one) is an exercise in futility. Especially since, even if you do manage to work the current kinks out, it is only a matter of time before some new conflict or missing file (disk errors are still a thing) leads to a whole new cycle of having to manually search through literally thousands to millions of files for the fix.

 

mathiasdeckman said:

As far as I'm concerned, because of the past three days of trying to figure this issue out, I'm going to abandon Genesis 8 character creation (both male and female alike as there are issues with the male as well).  I can only bandaid the problems with what's been said here- i can't ever fix it because i can't fix the fundamental errors - Daz studio 4.11 and it's duplicate formula bs (and lack of switch for it to ignore them) and Genesis 8 idiocracies.  Maybe I'm the guy who's gonna get all the worse bugs at once.

Simply abandoning Genesis 8 character creation is not an adequate fix for this because it is only a matter of time before something in the massive Genesis 3 or earlier domain of your runtime similarly goes funny and you lose that usability too. Here's how you (or anyone else potentially facing the same/similar situation) should go about permanently dealing with this:

1. Leave your existing installed content library well enough alone (that way what still works continues to work - which is what you should be more concerned about at this point.)
2. Install (assuming you haven't already) the Daz Installation Manager and learn to love it. Although it may not initially seem like it from the initial interface, DIM is an extremely useful tool for keeping your content in line because it supports things like having multiple independent content libraries and importing/exporting custom CSV lists of installers (great for silo-ing projects.)
3. Get yourself a roll-your-own DIM installation package maker such as this one (freeware options also exist - my personal favorite is a commandline one called MakeIMZ that unfortunately seems to have fallen off the internet.)
4. Use DIM to set up a new Content Library installation directory alongside your existing one and set it as the default installation location.
5. Use DIM to install the latest Daz Studio BETA release (version doesn't matter here since the goal is to use it for just its independent content library reading functionality) and delete all of its default content library location paths. Then set it to only look in this new installed content library location you've created.
6. Continue working on existing projects in the 4.12/11/10/9/etc general release where your original content library is still the only one known.
7. Start gradually redownloading (when nencessary) the original installers for all of your 3D content and filing them away in some easily navigable directory tree somewhere (this should be your actual content library - not the actually installed content library folder that Daz sees) using your DIM Maker to generate DIM compatible installers for any non DAZ3D store native content along the way.
8. Begin installing (via DIM only) all of your content to the new installed content directory, using the DS Beta to occasionally check to make sure things are showing up there as expected.
9. Once you are confident that you have all the easily re-sourceable non-custom content items duplicated to your new installed content library, switch DIM over to using your old installed content library location as default and start installing (always via DIM only)  then immediatley uninstalling all of your now properly filed content to the old location. This should eventually leave you with a much smaller mixture of just customized items and improperly installed content in the old location. 
10. Save what you want (packaging as DIMs where possible) out of what's left to the place where you are now permanently filing the installers for your content, and then switch both DIM and the DS general release version you use for actual production to only seeing the new installed content location.
11. Once you no longer have to keep going back to the old location to dig out unexpected bits and pieces to get existing projects working again (there is simply no way to avoid this completely) get rid of the old install location completely.
12. The next time (because there will be a next time since Daz supports an open-ended content ecosystem) you start seeing ridiculously long loading times/content identification errors in the DS log file, use DIMs chronological installation views and rapid content uninstall/reinstall capabilities to troubleshoot out the conflict.

 

 

mathiasdeckman said:

You have been very inclined to state that it's 100% the user's fault and never the software's. Take note that the software was created by human hands- therefore, foullable. Maybe acknowledge that the softare can make mistakes- big ones and that the user isn't always at fault.

To be fair, the issues you are currently facing with redundant/conflicting content library assets leading to cripplingly long loading times are technically results of user error. Just not necessarily yours. Because Daz Studio/DIM supports an open-ended content ecosystem (thank the heavens) content creators technically count as users. Meaning that whatever errors their content introduces into your runtime (with the exception of content hosted/curated directly by Daz on this website) are out of Daz's hands.

Seven193

mathiasdeckman said:

I cleared out my genesis 3 morphs folder and the base took 5 minutes to load.

That'll work for a temporary fix, but I hope you just renamed it instead of deleting it. :)

I think Daz Studio will ignore this folder if you renamed it like:
\data\DAZ 3D\Genesis 3\Female\Morphs_OLD\

jpetersen1

I'm using external USB drives, I have an enormous content library, and it only takes seconds to load Genesis models.

I don't know what to suggest, but your situation doesn't sound normal.

Darkend

Credit to the many people that suggested going through the log file

Pretty sure this has been solved for a lot of people, but I have had this problem for the last few weeks, so I tried the log file method to find specific issues when loading a scene. With your scene finally loaded help > troubleshooting > view log file. I first cleared the log file, Select all, then delete on notepad. Then save it, you will have a clean slate. Then load your basic genesis 8 (female) - this is the source of our problem because she has many, many morphs, add-ons, etc.

Now, once she loads - can take upto an hour if things are really messed up - it did for me. Then go to help > troubleshooting > view log file. Then ctrl-F and search "warning" and find your problems, some are bigger than others. If you notice one particular set of morphs keeps cropping up in your ctrl-f search, try uninstalling and re-installing if the morph is important to you. I have also found an instance where I had an hd-add on installed but not the main character. That caused a massive delay even though I never used the character.

Cut my time from G8 basic Female load time from 30 minutes (she has no morphs, nothing) down to about 3 or 4 minutes. Complex scene with 2 G8 Female (each loaded to the brim with morphs and customizations) down to a load time of 20 min > and I'm not done cleaning yet. Small errors are inevitable, so there will be delays, but if it only adds a few seconds, no problem, but when a big morph is messed up, it can add huge chunks of time. I'm happy to go do something else for a few minutes, shower, cook dinner, but 1 hour wait time can erase inspiration and destroy the joy of working with DAZ. And DAZ3d is fun to use and you can do some incredible things with it.

Get the process started and look at it as an investment of a an hour or two to save a chunk of time each time you load a scene. It is painful, but it saves time and frustration long term. Also, you don't have to fix everything in the same sitting.