An update on the situation: good(ish) news!
Added 2022-02-12 10:54:03 +0000 UTCHello! I've got news for you, and they're important. To summarise them: they're good. Very good. But as always, there are… caveats. I will explain everything, and try to present it in a structure. We'll start with the good stuff, then the bad stuff, and once again get back to the good things. Let's go.
So. The good thing. I did receive my data this morning, and spent last several hours digging through it. It was possible to save a bit more than I was promised: about 90% of the files did survive, and the lost ones are mostly huge files (like standalone HDRI maps which I don't really need that much, and can easily restore if needed). I guess, it has something to do with how files are stored on SSD. This new disk is significantly slower than the previous one, though, and it does affect the rendering speed, but not too much.
The bad thing, however, is that a lot of stuff in the data that was possible to extract is corrupted. I only checked a couple hundred assets out of thousands, but ~50% of them have a dent of sorts, and those are just the ones I can check manually. Could be more.
But — and that's the good thing — my beloved Blake managed to survive in a pristine condition. My beautiful girl is just as beautiful as always, and I almost shed a tear of joy when I saw his face again. It meant that everything will be fine.
Unfortunately, not everyone was as lucky as Blake. In fact, almost none were. Aside from Blake, only Melinda, Suya, and Liam stayed intact (Suya does have a problem with her dick asset, but it's a separate thing, and can be restored easily). Everyone else has a problem of sorts. Some lost textures — like Rebecca, some lost geometry — like Samuel (he was a bunch of grey cubes). As their parent, I was distressed by all that.
However, the good thing is that I can fix the textures, and geometry by simply reinstalling the packages their original models came with. In fact, I already did so with most of them, and they look as they were supposed to.
Too bad that's not always possible. I noticed that some of my characters started looking rather… differently. Like, their shapes, their face features visibly changed, and sometimes pretty drastically. The only theory that I have is that I lost some important morph set that I've been using for them, and it affects thing. Daz, unfortunately, isn't giving me any information about it, and I'm still trying to pinpoint the culprit. All I know is that Dominique, Bree, Pepper, Trish, and Gillian are now all looking significantly different. Notice that they're all female models. This narrows down the list of possible morphs… a little. But I don't know if they'll be back to their normal form after I found the missing morphs.
The good news, however, is that none of those characters appear in the last scene of v0.15, which means that I can actually continue working. This is my number one priority now. I need to finish it so I could start restoring everything thoroughly.
As it stands, the development of Shattered officially continues. And I can't be any happier about this fact. Thank you very much for staying with me, and stay tuned for the progress report tomorrow. It's been a rough week to say the least, but we almost pulled through. Almost. But right now I'm an optimist.
Comments
Yeah, 2TB on the cloud wouldn't really work. In your place, I'd probably buy an extra HDD/external HDD and would make a copy of everything every 1 or 2 months. It's what I do for big files. Kind of clumsy, but it works :-D
Merz
2022-02-22 18:46:38 +0000 UTCThank you :) Unfortunately, my Mega limit is just 400 Gb, and it's almost entirely filled with the game builds. My Daz library was 3 Tb (now it's closer to 2), so an with my uploading speed it would be impossible to store it all in the cloud anyway. Especially since with Daz you never know which files you actually need, and which ones you don't.
Yeda Games
2022-02-20 08:12:18 +0000 UTCGood that you managed to restore these important bits. Did you try asking for help on Daz3D forums? They've got some pretty knowledgeable people there. Also, for the future, one suggestion would be to keep critical files stored on the cloud. I personally prefer Mega. You could use something like Cobian to copy the files daily to your cloud folder, and the cloud provider software (like MEGAsync) would automatically upload your files to the cloud. Best of luck with the project going forward :-)
Merz
2022-02-20 05:55:34 +0000 UTCI did that, and found nothing. Unfortunately, the slider morphs are installed «on top» of the regular content, and if they're not present, they just disappear from the file. I'm fairly certain that I already restored all of the morphs I used to have, but it didn't do anything to fix the models.
Yeda Games
2022-02-13 17:50:27 +0000 UTCThanks! Hopefully I'll be able to finish it early next week!
Yeda Games
2022-02-13 10:47:31 +0000 UTCCongrats on the restored files. When should we expect full 0.15?
A A
2022-02-13 08:49:09 +0000 UTCYou could try searching it for 'missing' or 'not found' I guess. One thing that computers are very good at is searching through large amounts of text. If you're lucky that might help identify which ones are the problem quicker.
Wild Bill
2022-02-13 02:30:04 +0000 UTCDaz log is mostly useless, it's just thousands of lines of rendering information (which is basically just «layer 3234 finished»). However, I did encounter file corruption before, and it was breaking them in various ways. For example, I had a face expression morph that was breaking eyelid geometry. It worked, but the eyes were closing «backwards». It was pretty freaky. I imagine those broken morphs are working like that. I just need to find the corrupted ones.
Yeda Games
2022-02-12 12:54:16 +0000 UTCIf the files open, but look weird as opposed to not opening at all, then it definitely sounds like the file itself is OK but there is a problem with an asset that it depends on. I know nothing about Daz specifically but a fair bit about computers in general. That Daz doesn't tell you what the problem is is really bad though, have you looked for a log file that might contain more information?
Wild Bill
2022-02-12 12:50:33 +0000 UTC