- This topic has 29 replies, 13 voices, and was last updated 4 years, 9 months ago by
.
-
Posts
-
I was bored so I sat and watched the performance monitor while I loaded a base G8F. Load time was 2:02 minutes and disk activity was maybe thirty seconds of that and was only hitting between 20 and 40 Mbs in short bursts. My content is stored on a 7200rpm mechanical drive that fully saturated with copying a 3gb file to my SSD can maintain a 120 Mbs read rate. That leads me to believe that keeping your DS content on an SSD will make little to no difference in load times for assets as DS is just not hitting the disk that hard when loading.
Looking at CPU utilisation when loading a character, shows DS is running single-threaded and is maxing out whichever core it's running on so a CPU with good single-core performance might speed up load times very slightly. (anecdotally, when I upgraded from an i5-6500 to a Ryzen 5600X, load times felt quicker to me, but I never actually timed them.)
My, entirely personal, opinion is that it's down to Daz to fix the way characters are loaded so that either they switch to multi-threaded processing or change the way characters are loaded so that the morphs are only loaded when used, or load in the background after the main character geometry is loaded. Maybe they'll fix it in Studio V5, but I'm not holding my breath.
I think the characters / morphs should be looked at as a ratio. As far as I know each morph you have is loaded for each character you have.
High amount of Morphs Few Characters
So, suppose you have 1000 morphs and 1 character. That is roughly 1000 files that Daz has to load.
If you have to 2 characters, it goes up to 2000 files with that said amount of morphs and so onHigh amount of characters few morphs
But, if you have fewer morphs you can have more characters.
Suppose you have 100 characters with each at least 2 morphs of their own. The head and body. That is only 200 files that Daz has to load. Plus how many morphs you have from whatever else has sliders like expressions times by the 100 characters is the amount of files Daz has to process.Errors can cause dramatic slow down. I saw yesterday that BJ's Nadya character has a reference in the nadyasmile.dsf to a path referencing Amala instead Nadya in a .dsf file, just edited the dsf file in notepad form Amala to Nadya and got rid of a 25 second slow down. Updated the Growing up morph package to the latest version and got a 50 second speed increase. Uninstalled the Riversoft Art character converters some time ago and scored more than a minute.
Funny thing though, those "Could not find target property for formula: errors." They reference to a .cpp? file that is of Daz source code.
I have around 50, 49 of them acount for less than roughly 10 seconds in total but 1 of them is 1 minute Those errors can be caused by an array of different issues such as an incorrect path, a spelling mistake, not having a product installed it links to and more. But, here's the thing, if I fix the one that accounts for 1 minute slow down, and it's suppose to be gone, but instead one of the errors that was a fraction of second increase to that 1 minute slow down.Current load time for G8.1F is 1m.55sec to 2m.20sec depending on how fast Daz scans the HDD I guess.
I've made a lot of custom characters from many characters slider's and morph packages, gonna combine them into a single character morph and uninstall the sculpting morphs and most of the 200+ unused characters.
Edited my post, was up till 4 in the morning with this.
@Ethiopia, hey bud 🙂 Thumb hurts! I think my math was off on that, but the basic theory is somewhat correct.
Suppose you have 100 characters with each at least 2 morphs of their own. The head and body. That is only 200 files that Daz has to load.
Isn't it,
100 characters with 2 morphs each is 200 morphs. Which is 100x200=20000 files?All I can tell is, in a formula, characters are heavier on load times than morphs. Mad scientist out. Over 🙂
I was installing a pack of new products and while I was testing, I noticed that the loading of G8.1 characters suddenly became very slow. I measured the time - 2 minutes 40 seconds. The culprit was found quickly. It was Gu Yu. After removing it, the G 8.1 download returned to the usual time for me - about 40 seconds.
So I advise everyone who has a character loading time of more than 2 minutes to reinstall everyone with constant monitoring of the loading time.
upd. link fixedThanks for that tip @Yngvarr. Lucky I don't have this character. I wonder if anyone else can confirm what you found.
I've got about a 20 second load time for G8/8.1F. This is probably because I don't just grab every new character that comes along for the sake of it. I look at the skin textures and for unique faces mostly and particularly like characters that come with their own smile morphs. Let's face it, there are so many similar-looking drones out there, there's no point in having 90% of them clogging up your data folder.
When/if my G8F load time reaches about 30 seconds I'll be running a popularity contest and those who I have rarely used will be lined up against a wall and summarily executed... Andera... bang, Celest... nice know'n 'ya girl... bang... ricochet. Cleanse the hive so to speak.
Sorry Daz girls who didn't make the cut....
Oh, I see this thread is still going. I've decided to delete my library, and reinstall just the pro characters. With possibly a separate library folder for other G8 characters.
Unfortunately this is going to take me a few weeks because I have to manually go through my 1TB of zip and rar folders.
@pumpher And I thought my 4TB SSD for Daz3D assets was excessive and it's not even half filled yet.
@pumpher
You said that it is possible to correct errors from log, but how to do it?
For example:2022-01-08 15:12:25.580 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(6975): Formula output property not found: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/DAZ%203D/Base%20Pose%20Head/eCTRLEyelidsUpperUp-Down.dsf#ECTRLEyelidsUpperUp-Down?value - in file: /data/DAZ%203D/Genesis%208/Female/Morphs/P3Design/Get%20Real%20Expressions/GR%20Expression%2020.dsf
this error wastes 1 second when loading GF8. What can be done with it besides removing the package of expressions by P3Design?
And what type of errors can be fixed at all?
- Formula output property not found
- Formula target property not found
- Unsupported formula
In my case, 12 seconds pass from the first warning to the last one. This is a lot, considering that the full download takes 19 seconds.Didn't read the whole thread but I recently completely reorganised my libraries. I created a brand new "base" library that just contained Genesis 3 and 8, and a few extra things you need for basic functionality (starter essentials, etc).
Next I made a second library containing just the figures I intended to use. I only added the morph sets I needed (two or three of them - yes, it's tempting to install that 200 morph pack just for the one hip smoothing morph you "need" - but you don't really "need" it at all, so why bring along everything else with it - rinse and repeat a hundred times and you've got THOUSANDS and THOUSANDS of morphs you never use), and a few pose sets. For me that was literally about four characters.
Loading scenes/figures now takes seconds rather than the previous minutes.
I know it's tempting to hoard data and put everything into your library so you can see it all nicely organised in one place, but I now do that with the .zips on the file system (with a hierarchy of folders) and only unzip and copy over things I intend to use. I remove things I don't need to use, especially from morph folders.
Note that this applies to figures, expressions and morphs. Basically anything that forces Daz to prepare UI controls. So environments, shaders and so on don't count. You can have as many of those as you like.
I've seen people debate how to speed up Daz no end, literally hours and hours of discussion, and it's all nonsense. You've got too much in your library! If you reduce it right down to what you need, everything is faster. Not just loading, using puppeteer, activepose, animation, everything is faster and more responsive.
It’s a simple trade-off of time vs content. I couldn’t care less which is more important to someone else, any more than they would care which is more important to me. It’s either worth it to you or it’s not. No reason to hate on or wrong way/right way. Only what's better for you. If you have use for many morphs, which I do, it’s probably worth it. If you don’t, then it’s definitely not, and if you’re organized, then you can somewhat take advantage of both.
The great thing about DS is that it gives you the choice that other 3d apps don’t. That choice is why I both love and hate DS(mostly love). It may or may not be practical, either way, how DS handles content is a great idea for some, not implemented as well as it could be.
These warnings are inconsequential and normal. There is much info on the DAZ forums about such. If you are experiencing longer load times(unlike @frank22, for me, mins and not seconds), do a Google search about the particular warning you are concerned about. For example, searching "WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp" returns this result:
https://www.daz3d.com/forums/discussion/421811/missing-files-warning-when-loading-genesis-8-female
@pumpher, I have already read this thread on the forum. The first thing I did when I saw a whole bunch of warnings in the log was to Google this problem. I was just hoping to see some new way from you. But in any case, thanks for the answer.
That's what's strange. Richard says that everything is fine, it does not affect the download speed in any way. But the log says the opposite. As I already wrote, 12 seconds pass between the first and last warning. Either Richard is lying. Or daz is doing something useful else in this time interval.@yngvarr
You would be hard-pressed to find many that know more about DS than "Richard." Long story short, listen to Richard@ethiopia
Of course. I’m one that bitches the most, but if there’s a solution to current Daz software then he has the motivation to give an answer to what we’re bitching about. I have found solution after solution to DS’s shitty code from Richard. Till DAZ fixes the software what other answer is there? Besides, let’s be clear, as I’ve already said in this same tired thread, along with complaining about the same old code with you, we are bitching about a luxury.
- You must be logged in to reply to this topic.
