In the main menu, is all ok, smooth and all, but when i try to start the prelude campaign, it start to getting all choppy and slow. I can't even create my own char because is too slow: i click in an option and i takes like a two or three seconds of delay.

Anyone help?

I have the same problem.

Specs: Intel i5-2520M, 4 Gb DDR3, Intel HD 3000 graphics, Windows 10

All graphical options are set as low as they go.

Description: main menu works fine, campaign selection works fine, then when I enter character creation screen it freezes and I estimate that the fps falls from 60 to about 0.5. The cursor is unaffected, but all inputs have a 2-5 second delay. The game will launch and I can get to the start area, and it seems that my inputs register but the screen pushes out a frame every 1-3 seconds.

As far as 3D acceleration goes, I can comfortably play GTA: San Andreas on this system.

Menus are fine, but gameplay lags if anything interesting (ie., combat, graphical effects) is going on.

Edit: NWN1

I've been having the same problem. I was able to play normally a few months ago, but now the entire experience is choppy. Like Henkkles said, the cursor moves normally while the game itself has random jittering and delays. Since nothing has changed with my computer, I'm assuming it's a problem with GOG Galaxy.

is everyone in this thread-- the three replies above-- are all of you running in WinXP compatibility mode?

Thank you. That does appear to have helped a bunch; but there's still lag.

Same here, its unplayable for me... laging and choppy. On win 10.

to those having trouble running nwn 1 on win10, i suggest maybe these posts:

www.gog.com/forum/neverwinter_nights_series/nwn1_andor_nwn2_windows_10
neverwintervault.org/forums/neverwinter-nights-1/nwn1-tech-qs/windows-10-updates-slows-nwn

I also make the following suggestions:
1) Win10 is a crappy crappy bug ridden piece of shit software. MS designed it to F people up with random updates and spyware. Dump this piece of shit. Use windows 7 or windows xp for NWN 1. Runs beautifully.
2) Use Directx 9.0c. Do not use any other directx or any other later version. Dx9.0c was the most compatible and smoothest version for NWN1.
3) Use winxp compatibility mode.

Overall, i did not find NWN1 less fun than other games which came after it. I tried Smite, Champions of Regnum (very good realm team pvp game), other high gfx mmorpgs etc -- they all laregly sucked compared to NWN1.

NWN1's versatility and sheer fun factor kmassively outweighed the "nice" gfx of later games. None of the later games showed they had learned anything from nwn. Instead, nwn had already solved team pvp balance. Even today NWN team pvp is way ahead in terms of fun and balance than LoL, Dota, Hearthstone or Smite or any other moba.

So yea, I decided to return to NWN1. Sacrifice WIndows 10 for nwn1? Would do it in a heartbeat. Also remember, you do not need high end gfx to run nwn1, so basically just buy a cheap 2nd hand laptopw ith a basic gaming card or intel HD 2nd generation gfx-- will probably run NWN1 easily on WinXP or Win7.

(i think Win10 can run NWN1 smoothly, just needs fiddling).

First thing I always try with older games is WinXP SP2 mode.

Steps so far:

1) Compatibility:
1a) WinXP Service Pack 2 mode - Seemed to make a big difference
1b) Administrative mode
1c) Disable full-screen optimizations - Seemed to make it closer to a reasonable frame rate
1d) Set High DPI Scaling to System (Enhanced) - Unsure if there's a difference; at the least, did not hurt
2) Install latest NVIDIA drivers
3) Intel's driver update utility just cycled through "download -> install -> ask for restart -> download -> ...", so was not useful in my case, unfortunately.
4) NVIDIA control panel:
4a) Set high-performance mode for nwmain.exe - No apparent difference, but it might help someone else.
4b) Set OpenGL graphics to use graphics card for nwmain.exe - No apparent difference, but it might help someone else.
5) Disable GeForce Experience In-Game Overlay - This seemed to make some noticeable difference
6) It may also help to turn off Windows 10's Game Bar, but mine was already off.

At this point, my frame rate is acceptable. The test scene is my wizard, panther familiar, Tomi Undergallows, and a Summon Monster II (boar) at the gates of the Peninsula District during the prison outbreak in OC1.

Also, if you want to play on Windows XP, I would recommend against buying a laptop. Instead, buy VMWare Workstation Player. Or use the free version.

New post, because > 5 min, I guess. Also, want to make sure people see this.

As per this thread:
https://www.gog.com/forum/neverwinter_nights_series/how_do_i_set_default_cpu_affinity_to_all

1) Set "Client CPU Affinity=-2" in nwnplayer.ini
2) Set sound to use "Miles Fast 2D Positional Audio" in the advanced sound settings

With all changes, game now plays smoothly, with no apparent lag.

1a) done
1b) done
1c) ?
1d) ?
2) -
3) no updates
4) -
5) -
6) done

No effect whatsoever.

1) done
2) done

No apparent effect.

When I opened task manager, I noticed that Neverwinter Nights was not using more than 0.7% of the processor, but fiddling with affinity and the like only made it crash.

I installed it clean on a clean copy of Windows 10.

Changed nothing at all.

Smooth as silk.

But I don't have an Intel GPU, I have a NVidia GPU.

It seems that Intel GPU and NWN don't play nice together.

I encountered this problem earlier today. It not only affected NWN, but my whole computer started lagging, even after the game was shut down. I solved the problem and was able to resume play, as well as to repair my computer issue, by clicking the "show hidden icons" arrow at the bottom right of my screen, right-clicking on the GoG Galaxy client that was running in the background, and clicking "Exit", to shut the thing down.

It should also be noted that I cannot run NWN from the GoG Galaxy client. When I try, it disconnects my HDTV that I use as a monitor from my computer, and I have to do a force reboot of the computer. I have to start NWN from the .exe directly in the game folder.

Many of the problems with this game appear to be being caused by the GoG Galaxy client software.