Author Topic: Crashing Upon Entering Area  (Read 1328 times)

Legion XXI

  • Fraternity of Shadows
  • Dark Power
  • ******
  • Posts: 1724
  • Domn Clancy
Crashing Upon Entering Area
« on: April 04, 2012, 01:56:45 AM »
  So I was running along the Southern Farmlands, and accidentally wandered over the the (sp?) "Barovia - Balinok Mountains" Map, and immediately crashed about one step in.  I tried to re-log a few times and I would crash as the area got into the 90-100% loaded range.  Am I missing something special required for this map, and is there any way to fix it without re downloading the CEP?  (which is where I assume the texture for this map came from)

DM Nocturne

  • Sanguis Noctis
  • Dark Power
  • ******
  • Posts: 3262
  • Vampires don't do dishes
Re: Crashing Upon Entering Area
« Reply #1 on: April 04, 2012, 02:17:47 AM »
Yeah this issue is pretty common. I get repeated crashes myself.

The workaround is to lower your graphics settings to the lowest value (including the texture pack). Once you leave that area, you can return them to normal.

Bluebomber4evr

  • Head DM, Developer and Ravenloft Trivia Guru/Community Council
  • Administrator
  • Dark Power
  • *
  • Posts: 20622
    • http://www.nwnravenloft.com
Re: Crashing Upon Entering Area
« Reply #2 on: April 04, 2012, 12:49:31 PM »
Yeah, you have to do what Nocturne is describing. It's a bug with the tileset, and the person who created it is no longer making stuff for NWN.

Oh and the Mountain tileset is not from the CEP. It's in our tileset hak.

Bluebomber4evr: The Justice, not you, since 2002

Aahz

  • Dark Power
  • ******
  • Posts: 1127
  • People don't like to be meddled with.
Re: Crashing Upon Entering Area
« Reply #3 on: April 04, 2012, 01:16:30 PM »
Just turning off the grass fixed this problem for me.
"It never ceases to amaze me how bent out of shape adult people can get in a discussion on the best way to play make believe."

BarleyBeer

  • Guest
Re: Crashing Upon Entering Area
« Reply #4 on: April 04, 2012, 01:21:12 PM »
Just turning off the grass fixed this problem for me.

For me, as well.