Saved Scenes Reopening on a grey void

Is anyone else getting this?  I'll go back into a saved scene to work on it some more, only to find it opens as a grey void.  I'll go to open the same scene again, and I'm asked if I'd like to save the current scene - erm, no.  Sometimes I have to open the file 2 or 3 times to get the scene to open properly.  It doesn't seem to matter whether I click on the scene icon in my content folder or select it from recent scenes dropdown menu.  It always opens in the end, but it slows down my workflow sumfin' chronic!  Daz version 4:22, OS is Windows 10 64-bit.  Sun-sign Leo with Cancer rising.  

Comments

  • SofaCitizenSofaCitizen Posts: 1,889

    Not seen this myself but that's a bit worrying. Are the objects you expect showing up in the scene tab? Have you tried changing to a scene camera (if it has one), flipping the view mode from one thing to another or maybe changing to any scene camera just to see if the viewport needs a kick or something? Failing that is there anything that seems to be relevant in the log?

  • SofaCitizen said:

    Not seen this myself but that's a bit worrying. Are the objects you expect showing up in the scene tab? Have you tried changing to a scene camera (if it has one), flipping the view mode from one thing to another or maybe changing to any scene camera just to see if the viewport needs a kick or something? Failing that is there anything that seems to be relevant in the log?

    Completely forgot I'd posted this, so apologies for the late reply!  Yes, I'll switch from one camera to another, or onto perspective view, and everything is the same grey void as before.  At least once I can get the scene to finally open everything is there.  I haven't checked the log as I'm not very tech savvy and wouldn't know what I was looking at.  It's an intermittent problem that goes through phases of plaguing me every now and then, but this morning I've attempted to open one particular file about 6 times!   

  • Back in early September I posted this discussion, but then screwed up by forgetting to check on it.  @Sofacitizen was kind enough to respond, but I left it dangling too long.  Here's the text from that original post, which I return to because it's happening again:

    Is anyone else getting this?  I'll go back into a saved scene to work on it some more, only to find it opens as a grey void.  I'll go to open the same scene again, and I'm asked if I'd like to save the current scene - erm, no.  Sometimes I have to open the file 2 or 3 times to get the scene to open properly.  It doesn't seem to matter whether I click on the scene icon in my content folder or select it from recent scenes dropdown menu.  It always opens in the end, but it slows down my workflow sumfin' chronic!  Daz version 4:22, OS is Windows 10 64-bit. 

    So now it can take 5 or 6 tries to get a scene to open properly, if ever!

  • SofaCitizenSofaCitizen Posts: 1,889

    Oh, I can't remember what I said last time but I assume it wasn't helpful :( Did I suggest updating your drivers maybe?

    I can't say I have experienced this myself, although I don't re-open old scenes that often. However, I have tried a few and I do get the "do you want to save" so I think that part is perhaps not necessarily related to the "grey void" issue. It's probably Daz maybe writing some meta-data to the scene e.g. last-opened date or version maybe.

  • felisfelis Posts: 4,327

    I am not aware I have experienced that.

    If you open an old scene and it fails, what does the log then say, Help > Troubleshooting > View Log?

  • frank0314frank0314 Posts: 14,054
    edited November 14

    Please don't start new threads that you already had one on. You can get to old threads and posts through your profile. The new thread has been merged with the old.

    Post edited by Richard Haseltine on
  • crosswindcrosswind Posts: 6,966

    Copy the scene file to another disk and try again... A folk ever encountered the similar issue then finally found out the hard disk was damaged (maybe bad sectors...)

    And also open the scene file (duf) with Notepad++ to see if there's anything wrong within the file ~~

  • frank0314 said:

    Please don't start new threads that you already had one on. You can get to old threads and posts through your profile. The new thread has been merged with the old.

    Sorry, Headmaster!  :D 

  • crosswind said:

    Copy the scene file to another disk and try again... A folk ever encountered the similar issue then finally found out the hard disk was damaged (maybe bad sectors...)

    And also open the scene file (duf) with Notepad++ to see if there's anything wrong within the file ~~

    Thank you, Crosswind, I like the idea of copying to another disc.  Now, I'm not very technical, so what kind of thing might I be looking for that might raise a red flag in either the log or the scene filke? 

  • crosswindcrosswind Posts: 6,966
    edited November 15

    johnbuckeridge said:

    crosswind said:

    Copy the scene file to another disk and try again... A folk ever encountered the similar issue then finally found out the hard disk was damaged (maybe bad sectors...)

    And also open the scene file (duf) with Notepad++ to see if there's anything wrong within the file ~~

    Thank you, Crosswind, I like the idea of copying to another disc.  Now, I'm not very technical, so what kind of thing might I be looking for that might raise a red flag in either the log or the scene filke? 

    Ah.. that depends.

    As for DS log, usually we check the messages in between Determining missing assets... and Viewport redraw unlocked. Especially pls pay attention to the messages starting with [ERROR] and [WARNING], [INFO] means Good. You may attach your full DS log in here. We can help with checking.
    If you want to do so: 1) Relaunch DS, go to Help > Troubleshooting > View Log File..., Ctrl + A, Delete, Ctrl + S. 2) Close the log. Load your Scene; 3) In File Browser, go to: %appdata%\DAZ 3D\Studio4  Attach the file: Log.txt.

    As for Scene File (DUF), it may require more knowledge... but in general, we usually 1stly quick review the coding sections (by scrolling / Pg down) to see if there's any messy / gibberish codes, any incompletion of coding blocks, etc. Then TBH chasing down to each coding blocks will be even more difficult. Hopefully that'll be not your case.

    You also can attach your Scene File in here if you don't mind, We may help with testing.

    Post edited by crosswind on
  • crosswind said:

    johnbuckeridge said:

    crosswind said:

    Copy the scene file to another disk and try again... A folk ever encountered the similar issue then finally found out the hard disk was damaged (maybe bad sectors...)

    And also open the scene file (duf) with Notepad++ to see if there's anything wrong within the file ~~

    Thank you, Crosswind, I like the idea of copying to another disc.  Now, I'm not very technical, so what kind of thing might I be looking for that might raise a red flag in either the log or the scene filke? 

    Ah.. that depends.

    As for DS log, usually we check the messages in between Determining missing assets... and Viewport redraw unlocked. Especially pls pay attention to the messages starting with [ERROR] and [WARNING], [INFO] means Good. You may attach your full DS log in here. We can help with checking.
    If you want to do so: 1) Relaunch DS, go to Help > Troubleshooting > View Log File..., Ctrl + A, Delete, Ctrl + S. 2) Close the log. Load your Scene; 3) In File Browser, go to: %appdata%\DAZ 3D\Studio4  Attach the file: Log.txt.

    As for Scene File (DUF), it may require more knowledge... but in general, we usually 1stly quick review the coding sections (by scrolling / Pg down) to see if there's any messy / gibberish codes, any incompletion of coding blocks, etc. Then TBH chasing down to each coding blocks will be even more difficult. Hopefully that'll be not your case.

    You also can attach your Scene File in here if you don't mind, We may help with testing.

    Many thanks again.  :) 

Sign In or Register to comment.