Hello I have an installation problem with the toolset.
I don’t know how to set “custom.2da” or “edited.2DA” so the toolset could access them.
Where Do I need to have them installed in order for their content to be visible inside the toolset (not the game, they work from the override, campaign folders, and hak files for the game.
I have all my edited 2da files in a campaign, hak or UI Custom folder, and, apart from the UI Custom ones, they show in the toolset just fine. So, your 2das in the Override or campaign folders should be showing fine too. i.e. The toolset accesses the same files that the game does if using campaign folder structure (or override).
IMPORTANT: Choose only a single location for these edited files, for if you have one in your override and one in a hak and one in your campaign folder (all the same name), then you may not be editing the one you think.
Furthermore, if you edit a 2da file within the toolset (say that is sitting in your campaign folder) and choose to save it, then it writes the copy to your override folder (leaving the campaign version unchanged). Then you have to cut and paste it from the override folder to write over your original campaign 2da version to see the updated version in the toolset.
It doesn’t work with all the 2DA. There is somethign else to do for a 2DA to always work with the toolset, even if it’s not from the “normal location” beceause they aren’t all picked from here.
i did it once, but I can’t remember, and didn’t wrote down what I did for it.
If it’s the same behavior as for tlk files, then you’ll have to load them from the installation override folder.
True for some, but not enought for all of them. Some requires more.
For the ones that require a higher priority (that the toolset uses), put them in a hak.
Which one are you trying to edit?
There are a couple I have found that require placement in the custom UI folder (*):
( * ) You cannot access the edited version from the toolset though.
These are in a priority hak:
All others I have edited are in my campaign folder.
The one I try to get working in the toolset is raciasubtype, I have an old version which isn’t the “default” one working everywhere on one computer, but what ever I do with a fresh install it dosn"t show in the “toolset”.
Everything works clean anf fine in game with whatever setting.
I just did a test with an edited version of that 2da and it works fine from the override …
Did you remember to close and re-open the toolset after making the change?
Is the file corrupted … Did you want to share for others to test?
I don’t know where is the one I use for the toolset in one of my installation. on a clean install it dddn’t work from the override.
I ll try again.
I am talking about your edited one.
The one you are trying to place.
This …
Ibnn one of myt installation it’s always an edited ones that showw inthe toolset what ever I do.
On a clean install iyt just does"nt load in the toolset.
What are you trying to do…?
Are you saying that:
I could not understand your last response - can you edit it or retype it to make it clearer.
If it is the first option (which is what I think you mean), then you have the file somewhere, yes? If it is the second option, then you need to locate it within the areas I previously mentioned and delete it.
i.e. You do not require access to the original 2da file.
EDIT: The only other thing I can think of is if you have not patched your new install fully and that is having an affect on it.
Here is a list of all the patch files you need to fully reinstall (subject to language):-
LINK: Official NWN2 Patches -- Neverwinter Nights 2 Vault
(There may be other links to other files required.)
I’d like my new one to show. Not the default one, not the previous version. I need to run test on my NWN2 fresh install".
The file I am talking about then, is this “new” one that you refer to: Your edited file.
Do the following …
NOTE: The spelling MUST be the same: racialsubtypes, and so check your spelling.
DO NOT ALTER OR MOVE ANY OTHER GAME FILES.
the only thing I didn 't try is t place in hak.
It’s always the old edited one that shows. I will run tests on my laptop tomorow.
You have not told me if you placed your new edited file in the override …
If you did this, then that one will show, UNLESS … You have an older version (with the same name) floating around inside another folder somewhere, like a hak.
BUT, you say it is a NEW installation, which implies to me that you do not have any haks associated with the module you are loading if it is a new module within a new installation.
If, however, you are still loading an old module, then have you checked the haks associated with it? The 2da files come with the haks with a module, and no amount of reinstall will change what is in a module.
I didn’t see in the hak.
I tried in an empty module.
With an empty module, the ovveride one nevers shows. I old version always show. It’s not the “default version”
I tried a bit with my clean new install on my laptop nd here it’s always the "default’ version that shows in the toolset, (didn’t try the edited version in a hak).
It’s alittle mistery I’d like to solve. I completly bypassed the problem by using GFFeditor to the set new subrace. It works perfectly in game., I am fully able to read it with script and so on. it’s just the toolset is really relectend to load some of the “.2da” some of them only works if they are put in the “installation folder” for the toolset.
Have you rebooted your computer since reinstalling the new version?
If you are trying from a fresh toolset install, and there is no module loaded, then you should be seeing the default .2da. If you are not seeing the default 2da (but an old version you claim to have), then you have either:-
This is not required for the 2da in question, nor have I ever yet had a situation where this is called for as it can break your installation. Is this what you have done?
I found it !!!
The trouble comes from dialog.tlk.
The toolset read the dialog.tlk from the installation folder, not the “document folder”.
No custom name referenced in dialog.Tlk makes the list not filled in the toolset.
