After DS4.12 crash...grey blocks

Steel Rat

Reloading the same scene that crashed, sometimes only part of a figure (like their head) will show as a grey block.

In my last one that just happened, it looks like it was the hair on one figure that got blocked. Obviously everything is where it should be, since it was just before the DS crash. Fortunately I can re-load the hair onto the figure, but I can see how other similar problems can trash a scene you spent hours, or days, perfecting.

What causes this out of the blue?

 

nemesis10

Steel Rat said:

Reloading the same scene that crashed, sometimes only part of a figure (like their head) will show as a grey block.

In my last one that just happened, it looks like it was the hair on one figure that got blocked. Obviously everything is where it should be, since it was just before the DS crash. Fortunately I can re-load the hair onto the figure, but I can see how other similar problems can trash a scene you spent hours, or days, perfecting.

What causes this out of the blue?

 

I think that when you see those blocks, there is an interruption in the files in the data folder.  In the Poser world, it would be like a corruption that interfered wit the Geometry folder.

JD_Mortal

Daz can't identify the object, for whatever reason. The placeholder for an object is that funky grey box, which is roughly the L,W,H of the object which it can't identify.

Could be an issue with the database or with the saved file, which is similar to the database info. (Object-path, object-name, object settings, etc...)

If it has trouble reading the file, for some reason, or the data is actually corrupted for some reason... Daz won't try to guess what the unknown object should be. However, displaying that box can assist with you guessing what that object should be.

This happens to me when the database loses things like the core-models, and all my genisis models turn into grey gumby people. (Not a common issue, but one which I had a few times.) On that same level, I have had a few corrupted files display this issue, for various reasons. (Manual editing gone wrong. Renamed or updated objects that no-longer matched the names in the saved sceenes. A rare data-corruption, caused by a bad morph that tried to hijack the core-models with unneeded values which Daz couldn't read correctly. Etc...)

If this becomes more prevalant, try reloading your metadata or restoring the database. But, shut Daz down after doing that, before you try to use the files and save them. So you are SURE the data is 100% seen and loaded by Daz, after updating those things. Daz may sometimes retain old data, or fail to load new data, right after a large clean-out. Restarting Daz will force it to forget anyting stuck in memory and force it to read the data from the database at that point. Normally, it will just look like you have no items at all, or you may see a bunch of unidentified items in the smart-content display.

One little trick, if you happen to get a corrupted save-file... Don't just fix it and re-save it. Save it as something NEW. Otherwise you may end-up causing the next loading to have more issues, on some other item that it may not be able to read, and result in a total loss of the whole sceene. The issue may have also only been a glitch too... In which case, retaining the original file may be wise. Even if you have to manually move it to a new location, so you don't try to use it by accident, but may later need it as a backup, in the event of the loss of a later save getting corrupted.

Steel Rat

It was one item in the scene. Uninstalling and re-installing didn't fix it, until I deleted the item from the scene and re-loaded it.

So DS is either corrupting objects when it crashes (which is odd, since a render shouldn't be opening any objects for writing), or it's corrupting db entries, which is still odd for just a render.