[SOLVED] .DUF corrupted? Hangs Daz Studio 4.9.3.166 on load
I was working on a scene and saved it when I was finished as usual. When I came to load it later, it won't come up. DS hangs (shows as Not Responding) with the latest message -- if it helps at all -- being "Loaded file: FBMPortly.dsf" (the figure in the scene is Genesis 3 Male). I tested with the current beta, and got the same result. It looks like the log file is throwing up some issues, though I don't really understand what it's getting at or how to fix it. I clipped it down to just the relevant parts; file attached just in case.
Anybody know if there's a way I can recover this scene, or am I going to have to reconstruct everything? I have an old version that still opens with just the character, but not with the set, props and lighting that I spent forever setting up. Other scenes seem to work fine, it's just this one that's having issues. I'm on Windows 7 if that's relevant.
-A
Comments
Do the Portly morph and the right thigh side-to-side still workmas expected? Those are the things throwin errors at the end - the actual portly morph and the morph that adjust the shape as the thigh is posed.
Yeah, there doesn't seem to be any issue with using them otherwise, and this scene was fine until recently. I'm not sure what package they're from, but maybe a reinstall of the necessary files might help? I just don't want to have lost all that work if I can avoid it.
-A
Files do sometimes, very rarely I think, become corrupt - which is why incremental saves are a good diea, to make it easier to roll back. However, that usaully shows as the file refusing to load and the log sjowing an error involving a missing closing } or ] which you don't have. Could you upload the .duf file?
Sure thing, I've attached it below. Let's hope it can be recovered :)
-A
Well, the good news is that it isn't obviously corrupt - having unzipped it it's all in plain text and the parentheses seem to match. The Portly morph is one of Daz', probably from the Body Morphs set.
The scene opens, as far as I can given that I don't have all the content, correctly for me. That could indicate that the issue is in one of the items I don't have but the errors in the log you give above were related to morphs that I do have, and that seem to have loaded here. It may be worth first trying to clear the DSON Cache from Edit>Prefrences and then trying to install the content used if that fails to help.
Thanks for your help Richard, I'll give those things a try. I've noticed DS occasionally gets stuff 'stuck' in a cache, so that may well be the issue. (Previously it was building and saving bad shaders, which was a bit of a task to fix.)
I'm glad to know the scene isn't corrupt and it's just Studio being a bit wonky :) Probably 98% of my content overall is from Daz itself, and everything in this scene definitely is. The only thing that I can think of, having taken another look in the log file there's a bunch of lines as follows: "WARNING: libpng warning: iCCP: known incorrect sRGB profile", is that it might be something to do with having used LIE for some textures; again this could be a cache issue, I suppose.
I'll keep at it and see if there's any progress. Thank you once again for looking into it.
-A
Okay, did the following:
I'm at a loss for what else to do, short of rebuilding the scene -- which is a massive pain, to be sure, but not impossible.
Any further suggestions would be welcome. There's so many different things in use here that I'm not sure what could be causing the problem. I've attached everything logged from today in case there's something important I overlooked. (It occurs in re: the LIE textures, they took a really long time -- in the order of 2 or 3 minutes at a time -- to process when I applied them. I guess there's a chance that DS could just be processing them again and thus taking so long to load the scene that it seems like it's not working.)
-A
Edit: It looks like I'd guessed correctly at the end of my post. The scene was just taking a really, really long time to load (>10 minutes), probably because of the LIE textures, to the point where it looked like Studio had hung.
So it did load correctly in the end? Yes, LIE can have a considerable impact on speed when the textures are created/modified - you may want to look at http://www.daz3d.com/lie-baker (or just manually copy the LIE tiff from the temp folder and adjust the references in the Surfaces pane).