Hi all,

Just like in the topic subjet, game works flawlessly until a smoke or some water is in the view range, screen rotation comes very laggy as well. I have like 15 FPS... I launch this game with XP SP2 compatibility mode. Does anyone have the same issue? My config:

i5-4590
8GB RAM
Asus Radeon R9 270
Xonar DS

Thanks

I have a very similar issue.

Last time I played was 10 years ago but I just dug this out again assuming it would be crazy fast on a modern system, and for the most part it is, except when I'm in the larger outdoor areas: it suddenly gets quite chuggy.

Turn off shiny water.

That helped with lags when water is in view range, thanks.

Still having issues with smoke?

i have the sae problem and yes with smoke too

Be sure catalyst is allowing NWN to use its settings. If catalyst is overriding settings then it may cause issues.

You may need to set processor affinity, too. However, I havent had to do that with NWN for quite some time.
http://arelith.wikia.com/wiki/Dual_Core_Processor_and_NWN

P.s. after those attempts, see if reducing screen resolution helps. If not, then it may be time to ask support,too.

PC Gaming Wiki could be of use here - it has several apparent fixes for things like this.

That's about as useful as dancing to cause rain. NWN only runs on one Core no matter what you do.

In theory you might move NWN to your least used CPU if you are doing a bunch of other processing but even that doesn't make much sense. Core allocation built into the OS/CPU does this fine already.

Any issues with smoke/water are GPU related. Drivers/video settings.

It's an old fix. I don't know why, but if I didn't set core CPU affinity on my old core 2 on win xp, it would run very sluggishly. But like I said, I haven't had to do it in ages. Id imagine vista on self-regulated. (Or perhaps even a sp in xp)

Nonetheless, I agree. It seems to be a GPU issue. But I wanted to hit all bases.

P.s. rain dance work if done right.

Try this

https://www.gog.com/forum/neverwinter_nights_series/if_game_stuttering_and_slow

Older versions of Microsoft OS, like Vista and XP sometimes did a terrible job of allocation of cores. The OS would swap the application from core to core to core so that it would look in a performance window as though all the cores are being used equally. There is a run-time penalty for swapping between cores. This slows a single core application down. Setting affinity to a single core will stop the swapping. Just make sure that everything isn't set to use the same core.

Except that by default, NWN already locks affinity to your first CPU core.

All the instructions at that link do, is change it to lock to your second core. Which is utterly pointless.

They think Affinity 0 = off. It doesn't. I means lock to first core, 1 means lock to second core, 2 = third core....

It's just people not even understanding what they are doing, suggesting borderline random things.