9 réponses à ce sujet

[Youkai]

I have been working on a persistent world for some time now and it is nearing completion. Today I was going to do some more detail work on it and I found that it will no longer load.
When I open the module directory the toolset will quickly list the areas as usual but then they immediately disappear and the module goes back to being listed as "temp." I looked at the files inside the directory and everything seems to be okay. I do have backups but I would really not like to lose the work I have done on the module this month.
Has anyone here experienced a similar issue? 

[Ugly_Duck]

Just an assumption:
Don't "Run Module" from the toolset drop-down menu. This gets more and more unreliable as the mod grows in size. Are you doing this, or running it from the Game's menu?

The module I'm working on right now is about 3.00 GB & it refuses to load from the Toolset Menu.

[Morbane]

Youkai, there is no sure way to know which of your files got corrupt - it would usually be the last thing you were working on before the problem started (areas do this alot)

[M. Rieder]

Try copying everything from the module directory except the last area you were working on and then try opening that new directory and see what happens. That may reveal if the problem is the last area you were on. is autosave disabled? I haven't had an area go bad on me since I disabled it and I've worked on more than a score of areas since then.

Modifié par M. Rieder, 27 septembre 2011 - 01:16 .

[DFDark]

Well I had the same problem and I partly resolved it by importing files to backup module. But what aggravates me is that now it still can't load certain resources (although I have them in directory). I would replace them but I just don't know which files should I replace. The only thing I got is is this error, which only tells me that loading function failed.

img97.imageshack.us/img97/6048/mresources.jpg
 
Is it possible to get to know which files is it loading?

Modifié par DFDark, 27 septembre 2011 - 07:16 .

[Shallina]

Good practice :
Do a back up every day, when a module get corrupted, start again from the back up.

It's possible to get some work back preopely :

Open the corrupt module, export in a .erf all stuff related to your last work.

Import it in the back up module. If you didn't import the corruption, then you lost nothing.

And nevers forget to always keept a safe back up.

Win 7 64 bit is a life saver, I didn't have a single problem with NWN2  since I use it.

Modifié par Shallina, 27 septembre 2011 - 08:11 .

[DFDark]

Well I had first one, but It was not W7 fault, but rather power outage.

So I solved my problem. The Error was referencing to corrupted files. So I used process monitor to find the corrupted files and deleted them.

[Morbane]

I *think* the process monitor can be started in win7 by hitting ctrl / alt / del all at once and then a menu will come up - select "Start Task Manager" and in there the monitor can be activated. But dont quote me on that

[M. Rieder]

Shallina wrote...


Win 7 64 bit is a life saver, I didn't have a single problem with NWN2  since I use it.

Toolest and everything?  No messed up graphics?  Did you have to install DirectX9.0c?

[DFDark]

Well I have W7 for almost 2 years and it's in my opinion better than xp. Haven't had a single problem with W7 and NWN2