Saved poses take longer to load

Let's say I have a set of poses for G8F and they all load with an additional item conformed to it. I'll have to manually remove this item everytime I load one of these poses since I don't want it at all. The easy way shouold be to resave each pose of the set once I have removed the item, yet I noticed something: the original pose loads way faster than my own version. I explored the pose setting options and unticked all third party settings whcih weren't part of the pose and yet, the pose that I save then still takes twice as long if not more, than the original.

Can anyone enlighten me on this? :)

Comments

  • Are you sure they are poses and not Wearables presets?

  • JD_MortalJD_Mortal Posts: 760
    edited November 2019

    Current "loading issues" aside...

    This is a total "guess" here, but... When you load a scene, Daz may have to check every item in the scene, to see if it "still exists". From a list of out-of-sequence items, as you said that you removed some things.

    Unlike when you simply load a model, which may be "cached", and the files have already been confirmed to exist, at once, from the meta-data and CMS database. Which leaves just the "apply", process, which is done to a fresh model which is "zeroed-out". Unlike the "posed model", in the save file, where other items have been removed and the scene is sort-of jumbled data, not a full ordered load-sequence.

    I know that the first time you load a model, it takes a bit longer. The next time, it loads a bit faster. (in most cases) {Talking about the base-models or scripted models with morphs, opened from product files. Partially due to "checking for shared files", and "file existance" and "database loading". Things that a "saved scene", does not have the luxury of being able to do, unless it is "cached" somewhere.}

    Have you tried to reload the saved file, a second time, to see if that may also be the case? (To see if it "caches", the data about file-existance. Maybe it was just that initial reload that has taken a long time.)

    Also, there is the whole bit about, "clearing the scene", which can also stall loading. (Even if nothing is in the scene, but there previously was. It's like its not actually empty, when it appears to be. I question the "Clipboard, and UNDO system", but that is another shot in the dark.)

    Also... Could you have adjusted other model settings, like sub-D levels, or adjusted materials, which the "new model", will not have done to it. Thus, loading a new model and then a pose, will surely load faster. Also, a "scene", is not just loading the models, but also may be loading render-settings and various other saved assets, cameras, groups, etc... Stuff that you don't actually see on the screen, but all have to be unloaded of old values and reloaded with new values.

    Post edited by JD_Mortal on
  • JD_Mortal said:

    Current "loading issues" aside...

    This is a total "guess" here, but... When you load a scene, Daz may have to check every item in the scene, to see if it "still exists". From a list of out-of-sequence items, as you said that you removed some things.

    Unlike when you simply load a model, which may be "cached", and the files have already been confirmed to exist, at once, from the meta-data and CMS database. Which leaves just the "apply", process, which is done to a fresh model which is "zeroed-out". Unlike the "posed model", in the save file, where other items have been removed and the scene is sort-of jumbled data, not a full ordered load-sequence.

    As far as I know DS does not read cahced DSON data for files that are missing, and it will always prompt if there are missing files that are needed to load the current file.

    JD_Mortal said:

    I know that the first time you load a model, it takes a bit longer. The next time, it loads a bit faster. (in most cases) {Talking about the base-models or scripted models with morphs, opened from product files. Partially due to "checking for shared files", and "file existance" and "database loading". Things that a "saved scene", does not have the luxury of being able to do, unless it is "cached" somewhere.}

    Have you tried to reload the saved file, a second time, to see if that may also be the case? (To see if it "caches", the data about file-existance. Maybe it was just that initial reload that has taken a long time.)

    Also, there is the whole bit about, "clearing the scene", which can also stall loading. (Even if nothing is in the scene, but there previously was. It's like its not actually empty, when it appears to be. I question the "Clipboard, and UNDO system", but that is another shot in the dark.)

    Also... Could you have adjusted other model settings, like sub-D levels, or adjusted materials, which the "new model", will not have done to it. Thus, loading a new model and then a pose, will surely load faster. Also, a "scene", is not just loading the models, but also may be loading render-settings and various other saved assets, cameras, groups, etc... Stuff that you don't actually see on the screen, but all have to be unloaded of old values and reloaded with new values.

    When you load any model DS first reads in the base asset, then adjusts its settings to match those in the loaded file if different.

  • Are you sure they are poses and not Wearables presets?

    When I apply them, it results in the character striking a different pose and having a new item conformed to it. So maybe it combines both?

  • Are you sure they are poses and not Wearables presets?

    When I apply them, it results in the character striking a different pose and having a new item conformed to it. So maybe it combines both?

    A wearables preset can apply a pose - it's used for things like having the feet correctly posed for the heels, or hands gripping held items - so I think theya re probably Wearables.

Sign In or Register to comment.