NWNX2, Letoscript, and Windows 7! HELP! Scripts posted!

[WardenWolf]

I'm building a new machine for the game world 12 Dark Secrets. I have everything set up exactly as it is on the old server. We use Letoscript to modify characters ingame. This machine is practicing some bizarre voodoo against me, and I need help getting to the bottom of it. The machine is a quad-core Phenom II 3.4 ghz with 8 gigs of RAM running Windows 7 64-bit.

1. When I try to use NWNX to load the server with a module that has the Letoscript tie-ins, the server crashes. If I try it on a regular module, it works just fine.

2. Since I have read of problems with using madchook.dll on 64-bit systems, I tried it on an XP Virtual Machine with 1.5 gigs of allocated memory. It still crashes.

3. When I try to run the server with NWNX2 over a mapped network drive on MY Windows 7 64-bit machine, using the very same configuration files, plugins, etc, it works FINE. Natively. On 64-bit.

4. I tried it on the new machine with only 4 gigs of RAM, and it still crashes.

Can someone PLEASE help? I have installed virtually everything I have on my machine on the server. They're both AMD Phenom-series CPUs (mine's a Phenom quad 2.6 ghz, server is a Phenom II quad 3.4 ghz), both AMD-based Gigabyte motherboards, etc. All drivers are the same.

[Zebranky]

http://www.nwnx.org/phpBB2/viewtopic.php?t=1136 may help.
_________________
Win32 SVN builds: http://www.mercuric.net/nwn/nwnx/

<Fluffy-Kooshy> NWNx plugin is to this as nuclear warheads are to getting rid of fire ants.

<ThriWork> whenever I hear nwn extender, I think what does NWN need a penis extender for?

[WardenWolf]

Nope. Still doesn't work on the server but works fine on my PC. It's the server that's crashing. Not NWNX.

[Zebranky]

Do you mean the server machine, or just the NWN server? The latter is expected from any NWNX-related crashes -- all NWNX plugins are actually running under the nwserver process, so errors will crash nwserver, not NWNX.

Can you post any scripts that might be related to the crash, particularly Leto initialization scripts, if such things exist? (I don't know -- I've never actually used nwnx_leto.) Someone more experienced with it might spot an issue. Otherwise there are bigger guns we can bring in, such as attaching a debugger.
_________________
Win32 SVN builds: http://www.mercuric.net/nwn/nwnx/

<Fluffy-Kooshy> NWNx plugin is to this as nuclear warheads are to getting rid of fire ants.

<ThriWork> whenever I hear nwn extender, I think what does NWN need a penis extender for?

[WardenWolf]

Just the NWN server, nwserver.exe. There's no scripts. Any time I try to load a module with Leto tie-ins with NWNX2 running on that machine, it crashes.

[Nabla]

I don't know nwnx-leto plugin, but the following details may help finding the cause.

If you lauch the server without nwnx2 did it crash?
If it doesn't work, try to test alone all nwnx2 plugin. For removing a nwnx2 plugin, you move it outside of nwn directory.
Then more detail on when the server crash and the message that it gave may help.

What version of nwn, nwnx2, and plugin are you using?

Like say before, a nwnx2 plugin may make crash nwn server.

I am not a specialist but a possibility in think is that for some reason that i don't know the offset are different or other funny think that make that memory is different in the two machine.

[Fireboar]

Just to check... you are using Leto 24 and not Leto 26, right? And does the module in question still crash nwserver even without NWNX?

[Zebranky]

[WardenWolf]

There's scripts in the module to tie in, yes. We have a device in the module that adjusts player's stats, and it uses nwnx_leto. I dare not touch it, as it's a very complex and sensitive part of the game. I'm using Leto version 24. Nwserver.exe does NOT crash when I load the module without NWNX2. However, invariably it crashes when I try to use it with NWNX2. It's an instant crash as soon as the module finishes loading. Instead of going, "Running, login at will", it crashes. It ONLY crashes on that machine, and it ONLY crashes when loading a module with Leto tie-ins. It does not crash on my machine running Windows 7. At this point, I have NO idea what's going on here. It doesn't even work in an XP Virtualbox container on that machine, yet it works over a network share to my machine.

[WardenWolf]

Here are the 4 main scripts we use:

qd_inc_lsfunks

[Fireboar]

What other NWNX plugins are you using? Isolate the cause of the crash. You can do this by creating a "plugin-unused" directory and moving plugins there to figure out which one(s) is/are causing the crash. I suggest starting with just vanilla NWNX, then adding plugins one by one. Once you've found one it crashes with, try all plugins except that one to confirm that it really is only that one plugin, if not repeat the process.

If you're sure it's Letoscript, you can just disable nwnx_leto in this way and see if it still crashes.

[WardenWolf]

We're ONLY using nwnx_leto. That's all we use. And it only crashes when we load the leto plugin. I disabled the leto plugin and it works. But, of course, we need it for the stats editing.

[Lokey]

[WardenWolf]

The problem is that it also crashes in a Windows XP 32-bit VM. And a 32-bit Linux VM. And it works fine on my Windows 7 64-bit machine over a network share from the server; just not running directly on the server machine. I'm using the last-released version of madchook that comes with NWNX, the 2005 version. If anyone has access to a newer version of madchook, I'd love to have it.

We have Max Hitpoints enabled on the server now, but the Max Hitpoints function is to bring older characters up to snuff, by effectively reformatting them up to max hitpoints without having to relevel. They're paying for convenience.

I need some scripting help here. I'm an expert NWN scripter, but Leto and external tie-ins aren't something I've dealt with before. I inherited this. If anyone could show me how to possibly get this working again with better code, I would be eternally grateful.

[Fireboar]

Help us out here. Any time you see NWNX!LETO!something, add a PrintString before and after to find out what's being sent and where the point of crash is. Debug lines are your friends.