7 réponses à ce sujet

[Retpircs Wols]

From time to time, I get errors with the toolset, usually while saving.  I know I should have written down the exact syntax, but I did not.  

Additionally, I will sometimes get an error of "cannot find ..." where the ... will be whatever resource I attempt to open (area, blueprint, whatever).  After that happens, even if I do not save, my mod becomes 0 kb and everything is gone.  Has happened more than once.  Does anyone know what causes this?

--Windows 7, recently redistributed Direct x 9.0c, ample power (i7 processor) and 8 MB system ram (8 more dedicated video).

Thank you for your time and assistance.

[Artemis Absinthe]

I guess missing resources in your override/campaign/hak folder.

here some advices :

1) If you're building a module with custom contents and then remove them from your override folder, hak or campaign folder, the toolset won't be able to open it again and could corrupt the module.

2) first thing, you should disable the autosave setting, because it's a well known fact it could cause problems.

3) When you open the toolset, a temp folder is created in your module folder (temp0, temp1, temp2, etc). When you close the toolset the temp folders are deleted, so, before you start to build you should save the module with a new name. I usually save as directory, so I can have more control over the contents, instead of just "save" as .mod.

4) ...or, maybe it's just bugged. You can try with a new installation.


The exact syntax of the error could have helped, yes

Modifié par Artemis Absinthe, 08 mars 2013 - 03:48 .

[kamal_]

Step zero: always work in directory mode, not module mode. This will prevent toolset crashes from erasing the module.

Step one: regular backups, like daily or weekly.

[ColorsFade]

With regards to backups, I recommend using some kind of source control (http://tortoisehg.bitbucket.org/). If you ever lose anything, you can get it back with the click of a button. I will commit/push changes several times during a session. Having a history like this allows you to go back to any previous commit and restore it. 

It' also very handy for working in outdoor areas. If you want to change something (like terrain) or make big sweeping changes, and end up not liking those changes, you can go back to a previous commit and restore from there. 

As suggested, turn off autosave and get used to pressing CTRL-S. I save way more often than auto-save ever could. 

[drechner]

Iveforgotmypassword wrote...

Step -1.. Turn off auto save and never trust the character appearance wizard he can do bad spells !

These are words of truth! Especially when NWN2 was first released it would cause data corruption and crashes like crazy. I think it's gotten better, but it can still happen.

[Retpircs Wols]

thank you for all the ideas. I will try to uninstall and re-install to see if it is bugged.

I did think of something, though: I had run the toolset once from the admin account (I was playing with the mod while waiting for some maintenance to complete). If I saved while running the toolset as admin, then opened the mod again from a standard user account, would that cause issues?

[kamal_]

Retpircs Wols wrote...

thank you for all the ideas. I will try to uninstall and re-install to see if it is bugged.

I did think of something, though: I had run the toolset once from the admin account (I was playing with the mod while waiting for some maintenance to complete). If I saved while running the toolset as admin, then opened the mod again from a standard user account, would that cause issues?

Make a copy of all your stuff before uninstalling, the game will delete everything when uninstalling.