Graphical Glitch

[theyesman]

So was really enjoying the start of the game, I leave for the Inn and this happens:

http://i55.tinypic.com/16287so.png

i7950 @ 3.07ghz
GTX295
6gig ram
win7 x64 ultimate

Others appear to have had this problem a long time ago from google, however I refuse to roll back my drivers as that will affect other games.

Anyone having similar problems?

[PFC_BROCCOLI]

I am having that exact same problem. The game works fine when inside areas, such as inside the inn or both wings of the optional swamp, but outside the inn/by the fort the same thing happens to me.

[theyesman]

I am having that exact same problem. The game works fine when inside areas, such as inside the inn or both wings of the optional swamp, but outside the inn/by the fort the same thing happens to me.

Seems like such a great game but from google there doesn't appear to be a fix :(

[theyesman]

FOUND A FIX!

'A workaround, that worked for me and others, is to enable debug mode and disable the sky (enable the console by pressing ` )

~ (You wont see a console open immediately, just type debugmode 1)
debugmode 1
sky 0
debugmode 0 (Unless you want to see every trigger, disable the debugmode again)'

[theyesman]

If that doesnt work try this:

Quote:
Change the Environment Variables to put the temp folders on a partition where there's a lot of space. Then start again from before you head to the Willow.

This solution worked for me.

The issue I was having was that the Weeping Willow area had to be unpacked before it could be loaded, and apparently it was unpacking to the default Windows TEMP or TMP folder (smells like more Vista compliance to me). On my machine there was not enough space there to unpack the area to that folder.

Some of you might be thinking, "That's great flemi, so what the hell is an environment variable?"

To these people, I give you this.

Procedure to change the location for the Windows TEMP and TMP directory:

Click Start ->
Settings ->
Control Panel ->
System ->
"Advanced" tab ->
Environment Variables

Under variables, there should be an entry for TEMP and an entry for TMP. They should be the same, and have a reference to the temp folder for the current user.

Select TEMP and click Edit

Now, on my machine my partition with the extra space is D:

So, I changed the "Variable Value" field to D:\\Temp. You will want to use what ever drive/partition has lots of free space here.

Repeat this process for the TMP variable just in case, then go to that drive and make a Temp folder there, just to be safe.

Hope this helps.

[calvin82]

To the OP : did you try to deactivate antialiasing? (Set it to 0 in options in-game, apply, accept, exit the game and relaunch.)

That solved the problem for me.

[dunniteowl]

I don't understand how rolling back one edition of a driver will "mess up" all your other games. Honestly, how great an improvement (if any) could be in those updates if they jack with some other games by leaving stuff out?

At the very worst, you might have to suffer through only having 4x AA instead of 8X. But hey, it's your computer and hardware. If rolling back a driver INTENDED for your particular card is unacceptable, then you'll have to just deal with the weird graphics if the other workaround doesn't fix it.

Rest assured, though, sometimes, rolling back an Nvidia Video Driver is a smart thing to do. They're not exactly known for the highest quality in their updates.

dunniteowl

[Darkpowder]

The issue is driver versions in Forceware

Versions i found with issues-

197.45 NVIDIA forceware is bugged with NWN2.

196.21 Forceware works fine, so stick with that

N.B. I haven't tried that part of the OC yet with my current drivers (258.96) so if someone can confirm that would be great.

[dunniteowl]

The issue is driver versions in Forceware

Versions i found with issues-

197.45 NVIDIA forceware is bugged with NWN2.

196.21 Forceware works fine, so stick with that

N.B. I haven't tried that part of the OC yet with my current drivers (258.96) so if someone can confirm that would be great.
As far as I have heard (*and I hear a lot) those latest drivers should be okay/fine. 196.21 and back and 197.57 (I believe it was) and up fixed the bugged issue not only with NWN2, but with those fan speed overheating issues that 197.34 (IIRC) caused.

dunniteowl

[Player87]

I was having a similar issue in which entering an outside area completely messed up the screen, what I did was lower the resolution untill I got a clear picture, then changed it back and now it works fine

[tylerbot2010]

FOUND A FIX!

'A workaround, that worked for me and others, is to enable debug mode and disable the sky (enable the console by pressing ` )

~ (You wont see a console open immediately, just type debugmode 1)
debugmode 1
sky 0
debugmode 0 (Unless you want to see every trigger, disable the debugmode again)'

===========================

This worked perfect for me