Is this a DS bug or just something that happens to me...

Three days ago I was working on a scene. I wanted to add an environment. It was a prop. I double clicked on it and it said it was going to clear my scene. I went Oh! Not what I wanted it to do. But I thought what can you do. It said it was clearing the scene. I waited and waited and waited. I tried to cancel. Knew I wouldn't be able to. DS went white and Windows said the app wasn't responding. Did I want to wait. I said OK. Then after a little bit, I decided to open the task manager and see if there was any activity. But DS wasn't listed in the running apps. So then I told Windows to close DS.
Today I finished a scene and wanted to create a new scene. I opened the file menu and clicked on new. DS said it was clearing the scene. But it just sat there. Same thing. I went to the task manager. But DS wasn't running even though the workspace was still open on my pc. I had to tell Windows to close the app.
And just now it happened again. I tried to create a new scene. It started to delete the old scene content. There was a partial progress bar. But then it seemed to freeze. I went to the task manager and no DS is listed but the app workspace is still open on my PC.
If I just delete an asset myself, it works fine. But if DS has to clear the scene, DS seems to crash even though the desktop is still open. I mean, if DS is still running, shouldn't it be listed in the task manager?
Comments
If you load e.g. G8 into the scene (which may take some time), and then delete it from the scene, it happens almost instantly, but if you then clear the scene (File > New), it may take almost just as long as it took to load G8. So just deleting an object doesn't mean it's actually fully cleared.
Clearing even small scenes can take a long time depending on different factors, so DS hasn't necessarily crashed even if it may look like it (that's true with different other operations too).
What I do is have two shortcuts for separate instances of DS. I can shut one down and start work on a new scene in the second instance without having to wait for DS to do God-knows-what to clean up after itself.
OK. Thanks. I didn't realize that. Yes. It was a Genesis 8 figure that I had loaded. Guess I'll just have to wait longer. Or maybe I'll try the second instance, so I won't have to wait.
...usually when I get the message about the scene being cleared it usually means the item I slecvted from the content tab is set up as a full complete scene rather than an asset. The way around that is to Merge rather than load the item.
ETA:
OK something is seriously borked. I opened the programme to test the above. When I loaded in an item suddenly my viewport went all to heck as the floor grid disappeared and I was only left with a line along the X axis and one along the Z axis. Never seen anything like this, not sure what caused it to happen, and I can find no way to fix it.. Closing the programme without saving did nothing.
sometimes I give up and restart Windows
...not sure that will help in this case.
That happens when the Backdrop color is the same as the color of the floor grid (128 128 128 - which is one of the grey preset colors in the Color Dialog). The center cross has a different color, therefore you can see it. Setting "Type" to "None" on the combo box on the Environment tab should fix it.
...thanks I'll give that a try. Still don't know how or why it changed that setting as I simply loaded in a prop I've used many times, and *boom*, it happened.
If it doesn't fix it you can also set the default color under Window > Style > Customize Style...
..the second one worked. Again Thanks.
Still don't know why laoding a prop would have changed that setting.
No, that sounds strange. I've had it happen myself a couple of times but that was when I had changed the Backdrop color myself and forgot about it.
...OK with that little incident taken care of..
I opened Daz loaded one of my characters then went to the "scenes" folder picked one of the sets in it, loaded it and it I received the same messages the OP did with teh scene replacing the character in the viewport. I then closed that, reloaded the character, then right clicked on the set's Icon that pulled up a menu of option clicked on Merge Into Scene and it loaded leaving the character there. . Most of the time this just happens with sets loaded form the Scenes folder. however it can also occur with as that is in one of the other content folders like Environments or Props/Architecture. This is why I first save what I am working on as a scene subset so what I created doesn't get wiped out if that happens. That way I can just merge it back in afterwards.
BTW< what were you trying to load that took so long as I get those white screens from, time to time (old system with a decade old 6 core Xeon and 24 GB of memory) If I load something that is fairly "heavy" like for example the full Urban Sprawl 3 which requires a lot of resources, I'll get a white screen on the viewport display with "not responding" warning that clears after the scene is loaded. Trying to abort an operation like that can lock up the programme.
I tried it again last night and I just waited a little longer and Daz cleared the scene and then it became active again so I could use the program again. I don't remember which prop environment I tried to load. It was one of the first ones in my library. I don't believe it asked me if I was sure I wanted to replace the things in my scene with the new stuff. It just did it.I'll try to make sure I right click and choose merge into scene going forward.