6 réponses à ce sujet

[Mad.Hatter]

Hello,

I have a small (50mb) test module that I am hoping to set up as a DM'd campaign.  I have set it up correctly to where clients can connect to me on the LAN and externally through Gamespy. I've set it up to run with NWNX4 with Skywing's bugfixes and a SQLite database which functions and writes properly (light and fast given my 4-8 player needs).

I'm experiencing the following oddities:
1.) I tried to set NWNX4 to run as a service but the .ini refused to load a module into nwn2server, meaning the server was unreachable on the LAN or through Gamespy. Trying to open the NWNX4 GUI resulted in a second instance of nwn2server opening and not reaching the server list. As a result, I removed NWNX4 as a process.

2.) After running for 10-25 minutes (tested this several times), the server suddenly hardlocks and has to be manually powered down. alt-ctrl-del doesn't bring up the task manager and input devices are 100% unresponsive. I thought that perhaps I was getting stuck in an infinite loop or something but I tested the same exact module with the same exact settings (in fact, even the same install folder copied over) on a Vista computer and it's been running for 7 straight hours without any problems. During those 10-25 minutes, players and DMs can log on and play normally without any performance issues. I tried setting core affinity to 0 for nwn2server with no change.

Any ideas? The computer runs Windows XP SP3 fully updated without any kind of antivirus programs or firewalls. It uses an AMD 4 dual-core processor and 2.5gb of RAM.

[Mad.Hatter]

^AMD 64 X2 Dual Core 4200+ 2.21ghz processor.

[Mad.Hatter]

Just ran another test. The server was up for a record 46 minutes. I kept Task Manager open the whole time to see what was happening as I fired off my various scripts and played around a bit while connected from another computer. The processor peaked at 15% usage. It was at 4% when it locked up and my pagefile and physical memory loads were very light.

[c i p h e r]

Might be the dual core processor. I've heard NWN2 has a problem with AMDs in particular. Try setting process affinity (in task manager IIRC) - assign a single CPU to handle the NWN2 server process. The game is not multi-threaded so you won't lose anything by doing this.

[Mad.Hatter]

Thanks for the reply, cipher! However, "I tried setting core affinity to 0 for nwn2server with no change."

[Mad.Hatter]

This is embarrassing to admit but let me give the solution should anyone find this thread via Google or somesuch:



I forgot to remove the # from the nwnx4.ini command line configuration which prevented nwn2server from properly selecting the module. As a result, when nwnx4 ran as a service it couldn't load the module. I had to copy my module and custom content to the install folder once I had everything running properly.



Running as a service solved the crashing issues. The server has now been up for nearly 6 hours straight without any issue.

[kevL]

sweet.