http://i489.photobucket.com/albums/rr256/ericthered1090/WTF.jpg

So that area was, for the most, part fully landscaped, just not textured. I opened it up today and that was all gone. It seems as though a lot of cells which I edited but didn't place any meshes into got corrupted. Anyone got any ideas on what happened, or if it's recoverable, or if it's going to get worse?

I've had that problem while working on TR claims, though not as severe as this. As far as I know it's a CS bug that pops up on occasion. I've never heard of a solution for it though. How far from 0,0 was the land? The reason I ask is it seems to be more common in certain areas.


KF

My file is corrupted. It deleted all the interior cells I did for my project.

I just checked and my backup had the interiors *whew* but that means all the work I've done over the last two weeks is gone. Unless. Can I merge the two files? Or will that cause duplicates to be created?

I merged the files, and it just looks like I lost one big interior, and a little landscaping. But this turned out OK. However, Kiteflyer, do you think this could be caused by the distance from 0,0? I know mine is pretty far, furthest cell is (156,-26). And I get the jitter, but I'd never had this data loss from it before.

You could try to merge them, but make backups first. I don't think it will cause duplicates, but I'm not sure. As long as you have backups I don't see how it could hurt to try.



KF

Edit: You type too fast

I don't think it is because of distance from 0,0. There seem to be certain areas that go wonky. My Tr claim wasn't near that far away from 0,0 and I had to re-do the file 4 times because of this bug. The people doing the claims next to mine didn't have any problems. I'm glad you got it to merge and didn't have to do all that work over. I almost dropped my TR claim because of similar problems.

I wish I had an answer for it, but I don't know any more than the others who have tried to figure it out. My best advice would be to make backups everytime you work on it. That way you won't lose more than one session's work. I now backup everything I work on.

That's what I thought, so I tried it, I'm pretty bummed about losing that interior though. I put a fair amount of work into it. But I have enough screenshots of it that I can recreate it whenever I build up the stamina. I still have the old backups just in case something in the merged file explodes!

But do you think it could be caused by the 0,0 Distance Phenomena?

Nah I had that bug in the middle of Seyda Neen, and have never had this same bug in any far away places I've been working on.

One thing you could try is checking up that puckapfile, but considering you were already opening the thing, I'm afraid it consists the latest changes now.

If you decide to fix the hole thing (if it's more worthy to you keeping the interior) try soften around the empty parts, that usually fixes the land back together for me.

I'm kind of confused Chaka ZG. Are you saying that it might have been possible to draw out the old data from the corrupt file? The backup is still unchanged, I only opened it to merge it with the newest (corrupt) version, I never saved over it.

I was planning on just smoothing out the landscape until I realized it had deleted my interiors...

I don't think it's the distance either. It seems to be some weird bug that only pops up at the worst possible time. I've only encountered it once in my modding career. The really weird thing is that I took the exact same file that was causing all the trouble and worked on it on another computer and everything went smooth as glass. As I said, it's really weird.



KF

Very weird. I'll keep that old file then. Maybe I'll be able to save that interior sometime. Thanks guys, that bug can kiss my nether regions.

There's that file I recently discovered and it's use. if yo urename the pukcab file into something.esp it will magically turn into an esp file, which should contain the last stable version of your last work. But like I said, it saves on it's own, so it might contain the thing you already merged, instead of what you actually need.

Oh, I see. Let me check that out...

Argh, you're right. It's already changed. But I will keep that in mind if anything like this ever happens again. Thanks Chaka!