The Dreaded DM Client Crash Issue

[Legacy_Tesslyn]

               Hi, i've been battling all day with this issue..

I have come to the conclusion that it cannot be the Pallete as I have tried stripping all custom module blueprints from the module and it also occurs when trying to DM the starter module that comes with the latest version of CEP.

I beleive that it is some kind of local bug issue, but it has occured on both of my computers. A full, clean reinstall of NWN and CEP did not have any effect.

When I used to DM the same module I had intermittant DM connectivity.

How do I fix this? Searching online just leads to dozens of instances of the pallete being blamed, and it doesn't seem to be the issue in this case. Something CEP related I imagine..
               
               

               
            

[Legacy_Thayan]

               You could maybe narrow it down by checking if the same issue happens by loginng in via the DM Client on a non-CEP module. And are you just launching the module via the DM Client, or are you launching it via NWN Server and logging in that way?
               
               

               
            

[Legacy_Tesslyn]

               NWN Server and logging in. I don't think you can launch modules as a DM?

Anyway read something about XP compatibility and just managed my first successful login in ages on my server machine after setting client and server to XP compatability. Need to test a remote login now.
               
               

               
            

[Legacy_Azador]

               Depends on the OS you are running. The NWserver program tends to act cranky with windows 7/vista, and needs to be run in XP compatibility mode + administrator mode, otherwise it'll cause repeated DM crashes.
               
               

               
            

[Legacy_NWN DM]

               You would also be wise if you can, to assign it an affinity to a CPU other than 0 or 1 if you have a quad core.