NWN crashes on area load

[Shadowy Reality]

Repeatedly crashing in the lower area of the Fomorian caves (Underdark (Upper) - Rupture (The Red Pool)).

I have been here before without issues, however now I cannot seem to log in at all, as NWN crashes immediately. Which means I am stuck.

What can I do?

[Shadowy Reality]

Managed to log into the Surface but as soon as I try to return to Cities and Planes the area that loads is the Red Pool, which crashes me immediately.

[Irongron]

I have the same thing quite often on my dm avatar. Nothing at all helps so I need to switch avatar until all reset. As far as I can tell it is random, and unrelated to specific areas.

Definitely troubling to hear it happening to players too, but this isnt something for our forums. You need to get your crash dump file and report it to Beamdog, repeatedly if needs be.

Like a lot of players I find it massively frustrating to find things broken in EE that worked fine before, I still crash FAR more often than I did on 1.69. I do at least understand it though - tinkering with something as large and as complex as NwN is bound to throw up issues, and I'm profoundly happy to see the game is being worked on.

That being said I live in fear that NwN will cease development again before all these things are fixed, so it is really very important these bugs to Beamdog each and every time they happen.

[Shadowy Reality]

Fair enough, will wait until next reset and send the crash log to Beamdog.

[S-Senpai...]

I am having the exact same issue when I loaded into this area. I sent in a report to see if my character could somehow be wisked away to safety.

I guess I too shall have to wait for a reset.

[Irongron]

I am having the exact same issue when I loaded into this area. I sent in a report to see if my character could somehow be wisked away to safety.

I guess I too shall have to wait for a reset.

Same area? (Red Pool)

[S-Senpai...]

I am having the exact same issue when I loaded into this area. I sent in a report to see if my character could somehow be wisked away to safety.

I guess I too shall have to wait for a reset.

Same area? (Red Pool)

Yeah, exact same area. Crashed on transition into the map, and now crash every time I try to login.

[Shadowy Reality]

We were both in the same party, seems like it happened to both of us when we transitioned.

[Gungru]

Junk, also crashed loading into this area.

[Irongron]

Okay, that's more than a coincidence now.

I just checked and it seemed this area was updated yesterday. We'll undo changes there then reset the server. Hopefully that will free everyone crashing there.

[S-Senpai...]

Since the reverting and reset, I have been free. Thanks!

[ActionReplay]

Found the issue for this it has to do with a new Placeable.

[DM Symphony]

I have the same thing quite often on my dm avatar. Nothing at all helps so I need to switch avatar until all reset. As far as I can tell it is random, and unrelated to specific areas.

Definitely troubling to hear it happening to players too, but this isn't something for our forums. You need to get your crash dump file and report it to Beamdog, repeatedly if needs be.

Like a lot of players I find it massively frustrating to find things broken in EE that worked fine before, I still crash FAR more often than I did on 1.69. I do at least understand it though - tinkering with something as large and as complex as NwN is bound to throw up issues, and I'm profoundly happy to see the game is being worked on.

That being said I live in fear that NwN will cease development again before all these things are fixed, so it is really very important these bugs to Beamdog each and every time they happen.

As AR mentioned this has to do with a new placeable added in the haks.

I used to make a lot of weird stuff in 1.69, and continue to do so in EE, and while there were a lot of crashes for players due to the skinmesh leak I found last year, the -height system, and logging in and out of NWsync servers, all three of these issues have been fixed, and even with those issues, making broken models and shaders as experiments has always been my personal main source of crashes.

I was hired by Beamdog last year to look at crash reports, and since my predecessors in QA didn't do much of that, and since Bioware's NWN didn't have crash reports, I am probably the first and last person to widely analyze crashes and suggest fixes to either servers or coders (Beamdog) for Neverwinter Nights, and have caught lots of issues with the game coming from both Bioware and Beamdog code.

Looking at a crash dump file for this instantly shows me which asset is causing the problem, and what about that asset was illegal or causing unintended behavior.

Contrary to what Irongron has stated above, submitting duplicate bugs to Beamdog's bug repo is the worst possible thing you can do to have those bugs fixed. If you really want to spam bump a crash to get Beamdog's attention, and don't want to contact me personally on Discord or otherwise, posting extra comments in your single report is sufficient. This will make it easier to find with the extra activity, since a lot of issues get buried quickly, due to people spamming multiple reports for the same problem.

I recognize that you won't always know if a 2nd crash is the same crash or a new crash, but when you know it's the same, please do not double, triple, or quadruple post. If you have .dmp files, nobody at Beamdog will look at it, generally, except for me.

Beamdog has switched to a new bug reporting system (Service Desk, from Redmine), and this bug reporting system does not make it easy to find other issues from the same reporter, it doesn't make it easy to close issues as duplicates, and it doesn't make issues very visible to anyone except the reporter, so when choosing how to spend my time on the clock, because I can spend all of my time flagging duplicates, asking reporters for missing details (A lot of people submit a report that they crashed, saying what the pop says, without including the files it says to attach in their own message), realizing a report with few words is actually for a different game and they accidentally submitted it for NWN, etc. None of which fixes anyone's crashes or other problems.

If you can find me on Discord and immediately send me a .dmp after you crash, I will usually instantly tell you what crashed you, and why. This usually means that you don't have to report it, and you don't have to wait for someone to see it. I do not charge Beamdog for this, this is something I do to save everyone time, and call off any witch hunts about crashing for rumour reasons, focusing instead on the cold hard truth of memory logging.

If you crash and you don't get a dump, you probably have something going on in the game that Windows doesn't like, and Windows has murdered your game to keep it from doing more. This can happen when NWN tries to use files in folders that don't exist, it doesn't have access to, or if it takes too long to do something before checking back with Windows to tell Windows it isn't drowning trying to load your portraits or a big area.

If you have this problem, you can still ask me about it, tell me what happened, and there's a 98% chance I'll be able to stop it from happening further.