4 réponses à ce sujet

[Gentry]

 Apologies if this is answered elsewhere, I searched but could not find anything.

After experiencing frustration using the toolset and saving files in module mod, I switched to saving as directory and had a lot less crashing. The problem is, when I went to bake an area and the toolset crashed.

When I reopen the toolset and open the directory now, it doesn't work. The files seem to load, and during the loading process even show up in the list (for instance, I can see my module scripts), but in a few seconds, when the loading is done, all the lists turn empty, and the module directory is not what the title bar says is open, the title bar says "temp0" (or "temp1", "temp2" etc., depending on how many times I try to open it). When I look in that temp directory, all it has are 3 files; "module" (lowercase) "MODULE" (uppercase) and "repute".

I am enjoying working on my module, but not so much the working for an afternoon and then losing everything. My question is how can I recover those files? I can open the folder and see all the .uti, .dlg, .nss, etc. and other files for my scripts, custom items and NPCs. I can accept that the area I was trying to bake may be trashed, but I have an earlier back up and not a lot has changed since then. Shouldn't I be able to access the scripts, items, NPCs, and conversations that are (theoretically) not corrupted? Thanks.

[_Knightmare_]

Try this, open up the toolset and create a brand new module. Go through to your Modules folder (via Windows) where you saw the "Temp0", "Temp1", etc. Open the folder for your module you are trying to build (the one that won't open in the toolset), copy/paste alll the files from your module folder into the "Temp0" (or whatever) folder. In the toolset, save the module. Close toolset, reopen toolset and try to open the newly pasted/created module.

You might leave out that one area that might be corrupted in your copy/paste.

[Gentry]

Thanks _Knightmare_, but that didn't work either. My guess is one of the Module files (the all uppercase or all lowercase) is probably like a sorta 2da, listing all the resources it knows about, and won't allow that.

What *did* work, was copying newer items that had been edited (scripts, armor, etc.) into an older backup. Of course, if it had been created since that backup it was no go, which is another thing that makes me think one of the modules documents must be like a docket for the toolset to take stock with. Is there any way to open those and edit them? And any pointers to info about working with the Toolset in directory mode, and what some of the advantages, besides less crashiness, might be, would be greatly appreciated.

[NWN DM]

What are your system specs?

By the way, if you see a "temp8yuhfui87q3r8" folder (or something similar), that would be a good place to look.

[_Knightmare_]

Hmm. When you first create a new module, and then look at its folder in Windows, there's like 3 files that are created with it, among them: MODULE.IFO, module.jrl. Try copying over all your stuff to a new folder as I described above except for those 2 files. That should "reset" the resources listing. Save new module in toolset, reload. See if that helps any.