What's this CLEARING THE SCENE ?

FauvistFauvist Posts: 2,289

You spend 8 hours on DAZ Studio and you want to go to bed so you QUIT DAZ Studio and you get this message CLEARING THE SCENE.  Then you have to sit there and wait for DAZ Studio to CLEAR THE SCENE.  Why?  It's a total waste of time.  We never had to CLEAR THE SCENE before.  Why now?  When anyone clicks QUIT on software it's suppose to QUIT.  That's what QUIT means.  But it doesn't quit.  And you sit there.  Watching the slowest QUIT in computer history.

Comments

  • nemesis10nemesis10 Posts: 3,883

    So, and this is true of everything programs especially on a Mac, when you do something, a lot of things happen. For example, you may save temporary files, swap hard disk space for memory, keep information for undoing. When you quit, the program returns that disk space, clears caches, writes important information to your directory, relinquishes memory. Otherwise, everything else you did after quitting would access to less and less memory and hard disk space.  This is why force quitting is bad.

  • HavosHavos Posts: 5,614

    Fauvist said:

    You spend 8 hours on DAZ Studio and you want to go to bed so you QUIT DAZ Studio and you get this message CLEARING THE SCENE.  Then you have to sit there and wait for DAZ Studio to CLEAR THE SCENE.  Why?  It's a total waste of time.  We never had to CLEAR THE SCENE before.  Why now?  When anyone clicks QUIT on software it's suppose to QUIT.  That's what QUIT means.  But it doesn't quit.  And you sit there.  Watching the slowest QUIT in computer history.

    This has been the case for years, so I am confused that you are only seeing it now. If your scene has very little in it, it will close quickly, but large scenes will take an age. The app seems to delete each item individually then recovers the resources for them before quitting, which I agree makes no sense whatsoever. Some variables like screen layout are saved as the app dies, so in theory you are not supposed just kill the app using the Task Manger (or MAC equivalent). However that is the only way to shut it down quickly, as it effectively does the same as an app crash. 

  • I think it's relatively new on DS for PC's. Well, I'll qualify this, I've only seen it since going from 4.21 to 4.24.

    When DS shuts down, like every program that behaves in a mildly civilised way, it has to clear the memory it has used, update registry settings and everything else involved in closing a program.

    If you have a big scene, this takes time in 4.24, and you can see the process. In 4.21 or earlier the same process happened, but only after the DS window disappeared. If you looked in 'Task Manager' you could see DS still there, with a slowly diminishing memory allocation for the program. This, with a huge scene, could take up to 5 minutes before it was all gone. And only then could you open another copy of DS. So... what has changed with 4.24 and maybe as early as 4.22, is that the process is faster, but visible, in that the DS window remains visible until the memory is finally cleared. Before this the window was hidden from view while it happened.

    Hope it explains it a bit.

    Regards,

    Richard.

     

  • CybersoxCybersox Posts: 9,459

    I've been getting that message for years and I use Windows.  I think it has a lot to do with how many products you have installed in your active libraries and, at some point, DS seems to get a bit kerfluffled trying to do whatever it's trying to do and it will take forever to shut down.  Worse case scenario, assuming that you actually saved everything while working you can just force a close using the task manager or simply power the computer down..

  • Peter WadePeter Wade Posts: 1,677

    Daz always used to say that using task manager to stop the program could cause problems, maybe corrupting the CMS database. I often shut my computer down after quiting Daz Studio which might explain why I've had items dissappering from custom categories. I use custom categories to organise content but sometimes I find custom category folders with nothing in them.

  • DS has always done this, it is relatively recently that it has kept the main window open for most of the process (before that it closed the window and people then had issues with, for example, installing an updated version and getting a white UI because the style files were bad).

Sign In or Register to comment.