Loading...
> >

Close DAZ Studio Delay

marblemarble Posts: 7,500
in Daz Studio Discussion

I have become used to waiting for 30 seconds or so after closing DAZ Studio and before starting it again. I do this quite often because I think that starting afresh regularly seems to reset any odd quirks or slow responses in the viewport. The 30 seconds is the time it takes task manager (depending on the complexity of the scene) to show that the GPU VRAM has cleared. It can get frustrating waiting that 30 seconds but I have convinced myself that it is important but is it? Can anyone say definitively?

Comments

  • TheKDTheKD Posts: 2,696
    edited February 2020

    I always assumed it was doing cleanup stuff like getting rid of temp files and stuff. If I force quite photoshop, I know it leaves behind huge temp files. That's not a huge problem, because I know exactly where PS leaves the temp files. I don't know all the places I should be checking for DS temp files that might be left behind though, so I usually just let it to it's thing.

    Post edited by TheKD on
  • marblemarble Posts: 7,500
    TheKD said:

    I always assumed it was doing cleanup stuff like getting rid of temp files and stuff. If I force quite photoshop, I know it leaves behind huge temp files. That's not a huge problem, because I know exactly where PS leaves the temp files. I don't know all the places I should be checking for DS temp files that might be left behind though, so I usually just let it to it's thing.

    So you leave it a while before restarting too?

  • TheKDTheKD Posts: 2,696

    Yeah, I usually run downstairs to grab a drink or look at my stupid facebook page or something and wait for it to finish up whatever it's doing lol.

  • Saxa -- SDSaxa -- SD Posts: 872
    edited February 2020

    .

    Post edited by Saxa -- SD on
  • marblemarble Posts: 7,500
    edited February 2020
    TheKD said:

    Yeah, I usually run downstairs to grab a drink or look at my stupid facebook page or something and wait for it to finish up whatever it's doing lol.

    I do that kind of thing while waiting for renders but not for restarting DAZ Studio. I can liv with half a minute delays but if I'm just wasting my time for no reason I'd prefer not to.

    Just to confirm, I just started a render and then went to water my little postage stamp garden. Unfortunately, the render is only at 6% and I'm back. :( ... And I just noticed a toe through the floor so I had to fix that and start again. If I wasn't so old I'd be looking forward to the time when my renders might take seconds instead of 45 minutes for a simple indoor scene (GPU render at that).

    Post edited by marble on
  • ChoholeChohole Posts: 33,604

    I am told

    Manually killing the running process WILL cause issues; particularly with saving state of the session - application settings, menu configuration, action configuration, toolbar configuration, layout. It will also interfere with cleaning up temporary data, but some of that same work is performed durring startup too (to deal with fallout from potential crashes), so that is less of a concern.
     
  • marblemarble Posts: 7,500
    Chohole said:

    I am told

    Manually killing the running process WILL cause issues; particularly with saving state of the session - application settings, menu configuration, action configuration, toolbar configuration, layout. It will also interfere with cleaning up temporary data, but some of that same work is performed durring startup too (to deal with fallout from potential crashes), so that is less of a concern.
     

    Thanks. That's more or less what I was assuming.

  • mclaughmclaugh Posts: 221
    Chohole said:

    I am told

    Manually killing the running process WILL cause issues; particularly with saving state of the session - application settings, menu configuration, action configuration, toolbar configuration, layout. It will also interfere with cleaning up temporary data, but some of that same work is performed durring startup too (to deal with fallout from potential crashes), so that is less of a concern.
     

    Eh ... color me skeptical.

    I've routinely manually killed DS processes, going back to at least 4.3. (Heck, I've even manually killed postgreSQL processes—supposedly another no-no, to no ill effect.) To date, I've never encountered an issue with DS—be it configuration, CMS, menus, content, or otherwise—that could be traced to having done so. 

    COULD manually killing running processes cause issues? Sure; but so could leaving them running. WILL it cause issues? Maybe; maybe not.

  • marblemarble Posts: 7,500
    mclaugh said:
    Chohole said:

    I am told

    Manually killing the running process WILL cause issues; particularly with saving state of the session - application settings, menu configuration, action configuration, toolbar configuration, layout. It will also interfere with cleaning up temporary data, but some of that same work is performed durring startup too (to deal with fallout from potential crashes), so that is less of a concern.
     

    Eh ... color me skeptical.

    I've routinely manually killed DS processes, going back to at least 4.3. (Heck, I've even manually killed postgreSQL processes—supposedly another no-no, to no ill effect.) To date, I've never encountered an issue with DS—be it configuration, CMS, menus, content, or otherwise—that could be traced to having done so. 

    COULD manually killing running processes cause issues? Sure; but so could leaving them running. WILL it cause issues? Maybe; maybe not.

    I'm still inclined to err on the side of caution. Half a minute is a little annoying while sitting there tapping my fingers on the desk but it isn't much of a show-stopper.

Sign In or Register to comment.