13 réponses à ce sujet

[Lance Botelle]

Hi All,

I hope I am missing something really simple here, as I do not want years of work to have gone down the drain.

I was closing NWN2 toolset and I had a Windows BSOD memory dump. So, I shutdown windows and restarted the toolset to reload my campaign folder. Only it will not load. There is a very brief flicker, but no data loads at all. I tried loading a backup folder, and I get exception errors, something about "blueprints" out of range.

I cannot even load the module as a "Game" now either.

I have tried with single modules and other peoples and they load fine.

Please advise.

Lance.

Modifié par Lance Botelle, 09 août 2013 - 05:12 .

[diophant]

Check if there is a temp_... folder in your modules directory, and delete it. Sometimes after a toolset crash, the toolset tries to load some stuff from there instead of from your module, and the weirdest stuff can happen.

[Lance Botelle]

Hi diophant,

There is no temp directory in my modules folder.

I am struggling to get this to work, and its getting rather scary now.

Lance.

[kamal_]

Upload the contents of your modules/campaign folder to dropbox, and post a link here.

[Lance Botelle]

Hi All,

My backup data works in a toolset on another computer, but does NOT work on the usual computer.

My current data does not work on either computer.

I get the following crash message on my current computer with the backup data:



Lance.

Modifié par Lance Botelle, 09 août 2013 - 04:58 .

[kamal_]

Lance Botelle wrote...

Hi All,

My backup data works in a toolset on another computer, but does NOT work on the usual computer.

I get the following crash message:



Lance.

EDIT: Hang on Ill try to work this image bit out

That's not too bad of an error. Path of Evil does that a lot when you open it in the toolset, even now. Some file somewhere is corrupt.

Click ok until the toolset opens things, and see what you've got.

[Lance Botelle]

kamal_ wrote...

Lance Botelle wrote...

Hi All,

My backup data works in a toolset on another computer, but does NOT work on the usual computer.

I get the following crash message:



Lance.

EDIT: Hang on Ill try to work this image bit out

That's not too bad of an error. Path of Evil does that a lot when you open it in the toolset, even now. Some file somewhere is corrupt.

Click ok until the toolset opens things, and see what you've got.

Hi Kamal,

I hit the OK button almost continuously ... and even held it in for a while, and it still did not clear and enter the module.

I am beginning to think my toolset may be corrupted as well as the current data.

Lance.

EDIT: OK, I sat there with my finger on OK for about a minute and now its continuing to load. UPDATE: Have another failed message now, something about OEIShared.IO Continuing with finger on button ...

FInally go tin, saved and reloaded and have another finger on button job about SYSTEM.IO this time. It's taking forever ... I may see if its my campaign folder that's corrupted and swap that over too.

Modifié par Lance Botelle, 09 août 2013 - 05:08 .

[Lance Botelle]

Hi All,

I have the backup working after copying the backup CAMPAIGN folder across as well as the current MODULE data. It seems that my campaign folder has corrupted somehow.

Phew ... At least I only lost what I did today.

Thanks for everybody's help and suggestions. It is very much appreciated at times like this.

Lance.

Modifié par Lance Botelle, 09 août 2013 - 05:13 .

[kamal_]

Now that you're breathing again, keep offsite backups with dropbox or the like.

[diophant]

It seems like a blueprint file is damaged, but hard to say whether it is a default blueprint, a campaign blueprint, or a module blueprint. You could try to further narrow it down by using your second computer, your current campaign folder and your backup module.

EDIT: oops, I was typing too slow, you already tried that

Modifié par diophant, 09 août 2013 - 05:21 .

[diophant]

In your campaign folder, check whether there is a blueprint file with suspicious size (most likely, 0 bytes). Blueprint files have extensions starting with U (e.g., UTC for creature blueprints). If you're lucky, you only loose one blueprint.

[Lance Botelle]

Hi Kamal,

  Yes, I do keep my backups both onsite (another HD) and offsite (on Dropbox), but I did not think that both the MODULE and the CAMAPIGN folders could have been corrupted, so I had only tried restoring the MODULE folder initially. After I restored both the campaign and the module, it worked again.

Hi Diophant,

I could not find any suspicious looking files, and it remains a mystery as to why both the campaign and module folders had corrupted (as the contents of both folders looked good to me still). My guess is that there is one or two critical files that got corrupted and stopped everything from working.

Everyone: There is an extra bit of good news: I think I managed to get the work I did today into the fixed module as well, by comparing file dates and recalling those conversations I was working on.

That was one of the scariest moments ever when working on the module ... and yes, as Kamal says, I have started breathing again now.

Lance.

Modifié par Lance Botelle, 09 août 2013 - 05:51 .

[Tchos]

My sympathies, as I recall something like that happening to me some time ago, too. I know I got it all working again, but I don't remember exactly how. I probably wrote about it and what had caused it at the time. That might have been the time I lost a day's worth of work due to restoring a backup.

[Lance Botelle]

Tchos wrote...

My sympathies, as I recall something like that happening to me some time ago, too. I know I got it all working again, but I don't remember exactly how. I probably wrote about it and what had caused it at the time. That might have been the time I lost a day's worth of work due to restoring a backup.

Hi Tchos,

Yes, it really was a frightening moment. Especially when I thought simply restarting the computer and toolset would fix it. Then, thinking restoring the module only would suffice. I have no idea what part was actually corrupted, as none of the files looked awry when doing a comparison with the backup. However, the campaign folder has a *lot* of files from other sources, which I did not check, and I suppose it could easily have been some of those somewhere.

The good news is that it is indeed fixed by the looks of things.

Thanks for commenting,
Lance.