Maximum number of Runtimes

I have a lot of Runtime libraries.

Lately when loading any chaacter the delay in loading is much more than normal.(Program itself starts normally)

This problem is the same in 4.11 and 4.12.

A few months ago I read here that if there are more than a certain amount of Runtimes, Daz slows.

Any truth here?

Thank you.

Comments

  • DrunkMonkeyProductionsDrunkMonkeyProductions Posts: 1,014
    edited March 2020

    yep it's true.

    The more folders you have mapped the longer it can take to load content.

    In previous versions of DS you'd get a warning about mapping more than 10 runtimes.

    The reason this is happening is that it is searching for the particular content in progression, starting with the top most mapped folder.

    If the content is in the first runtime, it'll load pretty quick, if it's in rutime 100, it'll be slower.

    edit: just to clarify, there isn't an actual 'maximum' number of runtimes you can map.

    Post edited by DrunkMonkeyProductions on
  • bicc39bicc39 Posts: 589

    How about 45 Runtimes?

    Each over 45 gbs 

    Thank you for the response

    top most mapped folder.

    Does the order listed in the Content Library play a Factor? 

    Have no problem deleting, all, then readding in reverse order.

    Thank you

     

  • SpottedKittySpottedKitty Posts: 7,232
    bicc39 said:
    Does the order listed in the Content Library play a Factor? 

    Have no problem deleting, all, then readding in reverse order.

    Not the Content Library, the Content Directory Manager dialog. There are buttons to move items up and down the list, no need to delete/re-add/get it wrong/start again (yes, I did do that... once...)

    As for speed of loading, another factor might be how many characters and morph packs you have installed for that Genesis figure. The actual morph data doesn't load for zeroed morphs when you load the character, but the placeholders for the parameter channels do, and if you have a lot of them, it can take more than a few seconds to churn through the list.

  • the morph pack issue
    ---
    only load the ones that the duf file calls for
    ---
    the rest should be in the content library ready to be loaded if you call them..  ie "all those no user interface files" 
    but I've noticed all the morph files for characters seem to be in the shaping menu .. so I don't really have to load a character but can just use a slider
    would be nice if they stayed in the content library
    ----
    plus, since I haven't counted morphs for different characters to figure out the part that plays 
    but genesis is a minute, gen2 a couple and 3 - 8 pushing 3 minutes to load. 
     

  • Richard HaseltineRichard Haseltine Posts: 102,308

    the morph pack issue
    ---
    only load the ones that the duf file calls for
    ---
    the rest should be in the content library ready to be loaded if you call them..  ie "all those no user interface files" 
    but I've noticed all the morph files for characters seem to be in the shaping menu .. so I don't really have to load a character but can just use a slider
    would be nice if they stayed in the content library
    ----
    plus, since I haven't counted morphs for different characters to figure out the part that plays 
    but genesis is a minute, gen2 a couple and 3 - 8 pushing 3 minutes to load.

    Many people do want the sliders available, and in nay event DS has to read them all in to establish the relationships so it knows whether Morph X triggers Y, Z and W - if morphs were litellay loaded on demand then DS would have to go through checking for relationships by rading every single fle every single time a morph was added, which would make morph application as slow as figure loading. The bulk of the data, the dletas recording how the shape changes, is not kept in memory initially but loaded only at need.

  • bicc39bicc39 Posts: 589

    Followup.

    There are 62 runtimes, each having more than 40 gbs apiece (see Attached)

    I have both 4-11 and 4-12 installed (separate locations).

    Issue and times apply to both.

    I double click to start program, it is running in under 2 minutes.(standard)

    I apply the genesis g8 basic female (or male). Figure takes over 9 minutes to appear. This is approx 4x the usual amount.

    In one of the programs I unchecked all of plugins I do not use.

    I eliminated all the poser runtimes from the content directory.

    The Current runtime has been in use for weeks and the problem did not appear until well after it was started.

    The runtime with the figures mentioned was moved to top of list

    No hardware /software changes. No nvdia updates

    It is still taking under/close to 10 minutes for the figure to load

    Open to any and all suggestions

    sec 2.jpg
    398 x 617 - 36K
    sec1.jpg
    454 x 422 - 37K
  • Richard HaseltineRichard Haseltine Posts: 102,308

    When loading a native figure each content directory has to be chacked for support assets - they are not required to be in the same content directory as the base. Have you tried with only the one content directory (you can save you current set as a set, then reload it when done testing).

  • bicc39bicc39 Posts: 589

    Not sure of answer, but.

    One of the Runtime folders 20a is just for the daz genesis 8 figures.

    If you were to do a install of Daz Studio from scratch, this would be the Runtime.

    It was the runtime I moved to the top of the list.(Conteent Directory)

    The basic figures from here now take 10 minutes to load

    I ask this question with baited breathe. My "pipeline" is Daz 4.11, Zbrush plugin,Maya Plugin. The resulting scene is exported from Daz to

    Keyshot 9. Took awhile to work out problems, but it works.

    Could I do a third installation of Daz Studio 4.11, bypassing all the  runtimes, plugins etc.

    Further Have you tried with only the one content directory (you can save you current set as a set, then reload it when done testing).

    How would I do this???

    Thank you so much for help,,,,,,,as usual

     

Sign In or Register to comment.