Has any one else noted the loading time difference between genesis and any mil4 figure?
Geneis loads fast like pop there it is. Where as V4 takes close to 4 minutes to load, why?
That wouldn’t explain the massive difference in load time, we are talking a few seconds verses several minutes. I could understand taking twice to 3 times as long to load, but that would still be less then a minute.
It’s entirely a difference in the way morphs are handled in Gen4 vs. Genesis. Especially if you have a lot of morphs injecting into your Gen4.
If you want a more accurate comparison of load speed take your fully loaded Gen4 character and save a scene file. Then load that scene file and compare that to how fast Genesis loads (because that’s what the Genesis file more or less is, an advanced scene file).
V4 and the other Mil4 figures, if you are loading them from cr2s (which within them call large numers of pz2s) are Poser figures, entirely in Poser format. This is not - and never has been - DS’s native format. When you ‘load’ them in DS, you are actually importing them via a plugin that converts them into DS figures. This takes more time tha simply loading something that’s a DS native figure in the first place. For instance, DS has always used weight mapping for joints ‘under the hood’; loading V4 from cr2, for each joint the data for the Poser legacy spherical joints and their zones have to be read in, then converted by the importer into weight maps that give very similar (though not absolutely identical) results on bending the joint to what the Poser legacy joints do in Poser (much as Carrara does, I believe). Converting from Poser figure to DS format figure on the fly while loading the data takes much longer than simply reading DS figure data.
I aven’t looked into this, but I also have the impression that DS does something regarding cacheing DSON figures on loading and saving, so subsequent loading of a DSON figure is quicker than the first ever load of it.
What? So you’re saying that V4 takes so long to load because studio has to convert a studio figure to use in studio? And you wonder why this stuff confuses me.
What? So you’re saying that V4 takes so long to load because studio has to convert a studio figure to use in studio? And you wonder why this stuff confuses me.
No, it takes so long to load because Genesis loads morphs AS they are used, not with the figure. If you load a Genesis Figure with a huge number of active morphs, it’ll take just as long or longer to load than Gen4.
Genesis is just a more advanced figure that takes advantage of advances in the technology that were unavailable or not widely known back when the Gen4 figures were created… what? Seven years ago?
What? So you’re saying that V4 takes so long to load because studio has to convert a studio figure to use in studio? And you wonder why this stuff confuses me.
No; because it has to convert a POSER figure to use in Studio.
What? So you’re saying that V4 takes so long to load because studio has to convert a studio figure to use in studio? And you wonder why this stuff confuses me.
No; because it has to convert a POSER figure to use in Studio.
Indeed, that is what I was saying. V4 is a Poser figure, that has to be converted into a DS equivalent figure when you load V4 from a cr2. As it has always been. Genesis is the first native DS figure DAZ have ever released.
And it is at its worst when you load V4 from a cr2 that also injects all the Morphs++, Elite, A4, Creature, S4 etc, etc morphs you have. Not only does V4 have between three and 4 times the number of vertices as compared with Genesis, meaning three times as much data to load for the geometry, but the morphs, of course, also contain at least three times as many deltas because of that. So if you load a V4 in DS from a cr2 that injects all the morphs for her you have (even though all or most are set to zero), DS has to load over three times the data for the mesh as with Genesis, and over three times the data for each morph as with Genesis, AND it will load all that morph data whereas with Genesis it will actually only load the data for any morphs not set at zero; and on top of THAT, DS has to convert the Poser figure into a DS figure on the fly during loading, inlcluding creating weight maps to (roughly) match the effects of the joints in Poser, and try to create all the ERC linkages between the channels in the DS system where ERC does NOT work the same way as in Poser.
I aven’t looked into this, but I also have the impression that DS does something regarding cacheing DSON figures on loading and saving, so subsequent loading of a DSON figure is quicker than the first ever load of it.
Ah, I see it. There’s a cache folder for DSON figures in AppDate. For each DSON figure I’ve loaded, there’s a .dsf file in there containing all the morph channels (though not the deltas) from all the morph files for that figure in the Library data folder.
So first time load of Genesis DS has to load each morph file from the data folder (one per morph) to get the info for each channel as it loads the figure. All those separate file disc accesses take some time. Subsequent loads of Genesis it just has to load the one cached file for all the channels, which is much quicker. So subsequent loads of Genesis (or any other figure in the library in DSON format) are quicker than the first.
I would imagine that loading V4 from cr2, injecting all morphs, saving V4 in DSON format, then loading that so it is cached in the DSON cache would then give much faster loading of V4 from a .duf file than from cr2. Though likely still longer than Genesis as the figure is still higher rez, so more data.
I would imagine that loading V4 from cr2, injecting all morphs, saving V4 in DSON format, then loading that so it is cached in the DSON cache would then give much faster loading of V4 from a .duf file than from cr2. Though likely still longer than Genesis as the figure is still higher rez, so more data.
Interesting train of thought…
It should be considerably faster than a ‘stock’ V4 load, slower than Genesis…but probably not 3x slower…
Also, since most of the load time involved is disk based…it stands to reason a faster hard drive will give faster times. A ‘green’ drive will extend the load times to painful levels…an SSD…don’t blink, you’ll miss it.
Hmm, but didn’t V3 load very fast too (including morph injection)? I think V4 reads parts of files and/or sorts them or does some other slow type of operation.
So there!
