I've just started playing the second module of the Bastard of Kosigan series, and I'm having problems loading a saved game. I try to load it and it gets stuck on the screen saying "Unpacking Module". I've never had this happen before, even with other user-made modules, so I'm not sure what to do.

It seems pretty random, too. Saves that used to load no longer do.

This is only happening with saves in this module, as far as I can tell.

Just a thought: have you removed any modules from your setup that were included in during your save game session?

Does anything eventually happen (like a crash) or does it stay there indefinitely? Have you looked at your NWN logs files? That wouldn't even matter, actually, NWN is pretty weird in that regard. Each save game basically contains the module in a sense -- I have some saved games from modules I deleted that I can still play.

As far as I can tell, it would stay there indefinitely if I didn't ctrl-alt-del and close it with Task Manager. I haven't checked the logs, though, so I'll try that next.

Here's what I found from the log files:
The "logs" folder has two txt files: nwclientError1.txt and nwclientLog1.txt

The first one is blank. The second one has this:
[Mon Feb 16 22:01:58]Server Starting Up: 10 Second Heartbeat logging has been disabled
[Mon Feb 16 22:01:58]---- Server Options ----
Max Players: 6
Char Levels: (1-40)
Player Password: NO
DM Login Enabled: YES
Server Admin Login Enabled: YES
Post Game To Internet: YES
Game Type: Action
Difficulty: 3
PVP Setting: FULL
Vault: LOCAL
Only One Party: NO
Enforce Legal Characters: NO
Item Level Restrictions: NO
Player pausing: ENABLED
Auto Save: Enabled
Saving Characters in Saved Game
---- End Server Options ----
[Mon Feb 16 22:01:58] Player [] () Joined as Server Admin 1
[Mon Feb 16 22:01:58] Player () Joined as Player 1
[Mon Feb 16 22:01:58] Loading Module: 000737 - bok82\The Bastard of Kosigan
[Mon Feb 16 22:02:15] Loading Module: 000757 - bok83\The Bastard of Kosigan

There's also a file called AR_ERROR.LOG in the main game folder. That file has this:
Names Differ: rwc_dirt_001 rwc_dirt_01

bok82 was a save that wasn't working before, but worked this time. bok83 was a save I made after loading bok82 to test things. When I tried to load bok83, it froze. I don't know what this stuff means, but I hope it helps.

This is the only part that matters, the rest is all good.

It looks like there might be a blueprint issue -- something in your game is identified (at a toolset level) as "rwc_dirt_001" when it's expected to be "rwc_dirt_01" (or vice versa) as far as I can tell.

I would post on this the main Bioware boards -- I know a lot about game mechanics and programming/scripting but not so much about the really base level stuff. Most (all?) of the people who can help you on this issue will be over there.

I've already posted a thread on the Bioware boards, and I included that information about the log files. The only reply I've gotten about the log files was that it might help if I preloaded the haks. Can you tell me anything about that?

See if this helps?

http://www.harvestmoonconsortium.com/forums/viewtopic.php?f=56&t=2050

That error is pretty minor, assuming its the only one that pops up. The game engine can usually choke through a few such errors, including broken transitions/missing maps, etc... and still generally run fine, once the module loads that is.

There's a lot going on when a module is loading however, like loading core resources, checking for overrides and loading them, them loading haks and module resources. Not to mention any scripted events that fire upon joining. All of this, combined with an error or three could cause issues.

Preloading haks can be a big help. When you've loaded another save, then switched to a current one and its worked, that's essentially what you changed. The haks loaded for the first version are still in memory when you reload the later version.

While you still might have occasional issues, preloading haks should help and has no detrimental effects when playing these modules. Just remember to disable the preloading if you visit a PW or start playing other modules.

Well, it looks like I've found the source of the problem. It looks like it was the Customize Character Override Hak that was screwing things up. That hak has worked perfectly fine with almost everything so far. All the premium modules, several user modules, even the first episode of the Kosigan series. It didn't work for some reason in parts 2 through 4 of the Aielund Saga, but it never crashed the game. And I have no idea why it's having problems with a dirt blueprint of all things.

Any ideas how I might get these two things to work together? Would preloading the haks help?

Yes, preloading the haks should ensure that they take precidence over the overrides. Though, its possible that something else in the overrides is simply conflicting with one or more resources in the modules too. If preloading fails, try replacing the override folder with a clean 1.69 version. You can just rename the current override folder to something else.

Here's a link to a clean 1.69 override folder: http://neverwintervault.org/project/nwn1/other/patch/169-override-patch-files

Correct me if I'm wrong, but using the clean override folder you talked about would mean I couldn't use Customize Character Override, right? That wouldn't be much help to me. I don't need any help getting the module working anymore - I know I can get the module working by just deleting all of the files for Customize Character Override. The only thing I'm looking for help with is trying to get the module and Customize Character Override to work together. It looks like only preloading the haks has any hope of doing that, so I guess that's what I'll try next.

Yup, preloading should be the best option in this case.

Looks like I spoke too soon. The problem is back now, despite the Customize Character Override files being gone. Now the error is "Names Differ: rwc_dirt_003 rwc_dirt_03" instead of "Names Differ: rwc_dirt_001 rwc_dirt_01". Removing those files fixed everything last night, but now it's as bad as ever.

I'm pretty convinced that it's a problem with the module, and that no amount of preloading haks or anything will fix it, because it's something basic and fundamental. If anyone here would be willing to download the module and give it a try yourself, I'd appreciate it. You can get it here:
http://neverwintervault.org/project/nwn1/module/bastard-kosigan-english-version