It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I'm wondering how to get the Client Extension to work properly... after a bit of tinkering with it I've had some success but the experience still leaves much to be desired. In particular, I'm referring to this extension:

http://nwvault.ign.com/View.php?view=Nwn2other.Detail&id=231

I downloaded the latest version (1.0.0.23), unpacked it and, following the instructions in the supplied text file, ran the NWLauncher.exe executable. It failed with an error, something along the lines of "Failed to start Neverwinter Nights 2 (error 2XX)" I forgot the exact error code but it was 200-something.

After having to look inside the NWLauncher.exe file to find the instructions regarding how to fix what was up (!) I realized that most likely the GOG installer did not create the proper registry entry for it (or at least did not update the previously available one which was left over, I think, from the GamersGate installation of NWN2 that I've used before).

I updated the registry path entry manually (as was mentioned inside that launcher executable), setting it to the correct path, and reran NWLauncher.exe, after which it actually started and showed, in addition to the main game screen, three extra windows with custom stuff described in the manual. The game itself worked fine (and, I believe, stuttered less, as advertised), but the custom area map screen did not work and the console window showed some related errors (something along the lines of "can't find the module area database", or something like that). The area map was totally black.

The game itself, as far as I could tell, worked alright until I tried to quit it, at which point it crashed to desktop instead of closing properly.

What exactly am I doing wrong and what else is necessary for this to fully function normally? As far as I understand, the GOG edition is patched to the correct version (v1.23), so theoretically it should work fine. :\

Thanks in advance for your help!

- Agetian
Post edited January 27, 2013 by Agetian
No posts in this topic were marked as the solution yet. If you can help, add your reply
Sadly, still haven't found a true solution to this problem. Playing as is (with the CTD in the end) seems to be fine though. If anyone knows how to properly fix/set it up I'd be happy to know.

- Agetian