Last DS upgrade: a hare and a snail

JerifeJerife Posts: 250

Is it only me or have some of you noticed that after last actualization DS opens really quick?

And it never seems to get completely closed???

I sometimes have to kill the process ending task in Task Manager in order to be able to open the program anew. This does not seem to affect the saved and closed instance

And I have lost the wonderful posibilitiy of having two instances of the program opened, me posing on one while the other rendered atomatically being in below normal priority. Now you can't have two oppenned.

Please Daz tell me this is temporary and not the state of the art

Comments

  • fastbike1fastbike1 Posts: 3,801
    edited August 1

    I don't have have issus with Studio closing. Then again I rarely feel the need to open Studio shortly after closing it. Personally, I don't understnad the need for multiple instances of Studio.

    YMMV.

    Post edited by fastbike1 on
  • L'AdairL'Adair Posts: 9,144
    Jerife said:

    Is it only me or have some of you noticed that after last actualization DS opens really quick?

    And it never seems to get completely closed???

    I sometimes have to kill the process ending task in Task Manager in order to be able to open the program anew. This does not seem to affect the saved and closed instance

    And I have lost the wonderful posibilitiy of having two instances of the program opened, me posing on one while the other rendered atomatically being in below normal priority. Now you can't have two oppenned.

    Please Daz tell me this is temporary and not the state of the art

    @Jerife, It's not temporary.

    There is a way around it, though, talked about in the beta thread.

    However, the new function is limited to the build, (release, public, private.) So you can have the beta open at the same time you have the release open. I actually use the latest beta for most things, then open a previous build release if I need a second instance of Daz Studio open. This is handy for creating subscenes to be merged with the larger scene I'm working on, whether it's to add a character and pose him/her, or simulate hair or clothing without unnecessary object in the scene.

    It turns out, DS has always taken a long time to shut down, behind the scenes. We just didn't know it because the program could be restarted before completely shutting down. Apparently that was causing some real problems. It is also possible to cause issues, we've been told, by ending the DS shutdown process with Task Manager. Although I have not yet personally had that cause an issue that I'm aware of.

  • Serene NightSerene Night Posts: 15,476

    When you close ds, the software is still open for sometime hogging memory. I tend to have to force quit to make sure it is really stopped, if you run the task manager you can see it lingering long after the app closes.

  • NylonGirlNylonGirl Posts: 265

    It is my understanding that when it's shutting down, you just have to wait till it finishes deallocating the memory it was using and it finally shuts down completely; and that if you load a new blank scene just before shutting down, the shutdown part will happen much faster. But you'll still have to wait for the deallocation of memory to load the new blank scene.

  • Richard HaseltineRichard Haseltine Posts: 62,996

    If DS is active in Task Manager it'ss till clearing memory, don#t force quit or you may corrupt soem of its configuration files. If it is sitting there doing nothing it may be a conflict with a third-party plug-in not allowing the shut-down to complete, in which case you may have to force quit but might want to try disabling third-party plug-ins, then reenabling them one-by-one - thiss cript will do the disabling for you http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/plugins/plugins_load_config/start

  • duckbombduckbomb Posts: 318

    If DS is active in Task Manager it'ss till clearing memory, don#t force quit or you may corrupt soem of its configuration files. If it is sitting there doing nothing it may be a conflict with a third-party plug-in not allowing the shut-down to complete, in which case you may have to force quit but might want to try disabling third-party plug-ins, then reenabling them one-by-one - thiss cript will do the disabling for you http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/plugins/plugins_load_config/start

    Is this true?  I literally force quit it about 10 times a day as I move between comic panels and files representing different render passes...  I've never corrupted anything, but now I'm concerned I'm high risk.  It's a shame, though, because just sitting around and waiting for it to close the way it's supposed to takes ages.

    Whats the worst that would happen, if you were to corrupt a config file?  I would just need to install DS again, maybe?  I'm honestly asking, because the risk may be worth it in the end, but maybe not lol

  • Richard HaseltineRichard Haseltine Posts: 62,996
    duckbomb said:

    If DS is active in Task Manager it'ss till clearing memory, don#t force quit or you may corrupt soem of its configuration files. If it is sitting there doing nothing it may be a conflict with a third-party plug-in not allowing the shut-down to complete, in which case you may have to force quit but might want to try disabling third-party plug-ins, then reenabling them one-by-one - thiss cript will do the disabling for you http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/plugins/plugins_load_config/start

    Is this true?  I literally force quit it about 10 times a day as I move between comic panels and files representing different render passes...  I've never corrupted anything, but now I'm concerned I'm high risk.  It's a shame, though, because just sitting around and waiting for it to close the way it's supposed to takes ages.

    Whats the worst that would happen, if you were to corrupt a config file?  I would just need to install DS again, maybe?  I'm honestly asking, because the risk may be worth it in the end, but maybe not lol

    Most likely it would affect the layout files, which can fairly easily be reloaded/reset (though if you didn't save a custom layout you would lose any adjustments). I thinmk there are risks for other preference settings, and force quitting can leave PostgreSQL running if the shutdown signal has not beens ent (which in turn carries a risk of database corruption if it has to be force quit). I don't know what the odds are - it probably depends on what, if anything, is happening at the moment you terminate the process - but I would urge you to try to figure out the reason for the delay, and if DS is being active to let it complete its tasks.

  • scorpioscorpio Posts: 7,334
    duckbomb said:

    If DS is active in Task Manager it'ss till clearing memory, don#t force quit or you may corrupt soem of its configuration files. If it is sitting there doing nothing it may be a conflict with a third-party plug-in not allowing the shut-down to complete, in which case you may have to force quit but might want to try disabling third-party plug-ins, then reenabling them one-by-one - thiss cript will do the disabling for you http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/plugins/plugins_load_config/start

    Is this true?  I literally force quit it about 10 times a day as I move between comic panels and files representing different render passes...  I've never corrupted anything, but now I'm concerned I'm high risk.  It's a shame, though, because just sitting around and waiting for it to close the way it's supposed to takes ages.

    Whats the worst that would happen, if you were to corrupt a config file?  I would just need to install DS again, maybe?  I'm honestly asking, because the risk may be worth it in the end, but maybe not lol

    Same hear, if they fixed the memory leak I wouldn't have to keep shutting it down, beggining to wonder if the Poser isn't going to be a better bet in future. DS is really hampering my workflow

Sign In or Register to comment.