Baldur's Gate : The Sword Coast Chronicles : NWN2 Persistent World

I recently bought a new computer, which is supposed to be much faster, but the Toolset runs reeeaaally sluggishly on it. Anything in the area preview window is pretty much just static. You try to pan the camera or tilt it and things won't change for 5-10 seconds.

Is this a Windows 10 issue? Configuration? I'm pretty sure I'm doing something wrong, I just don't know what that is or where I can fix it. Defaults clearly aren't doing it. :/


Things I've tried so far:
- Running as administrator
- Compatibility modes (XP SP3, Vista SP2, 7)
- Verified that .NET Framework 3.5 SP1 is installed and up-to-date
- Using the latest DirectX
- Installing DirectX 9.0c
- Running on a single CPU core

Some combination of running on XP SP3 compatibility mode, running as administrator, and enabling "Disable display scaling on high DPI settings" seems to have done the trick~!

I have no idea, sorry.
I would suggest trying to start the toolset in admin mode though, see if that helps?

Any more information on the exact specifications of your PC? GPU, CPU, RAM, etc.

Running in XPSP3 compatibility, DX9.0c and .NET 3.5 redists may solve it.

Favriel wrote:Any more information on the exact specifications of your PC? GPU, CPU, RAM, etc.

Sorry!

GPU - AMD RX 480
CPU - AMD FX-8370
RAM - 16GB

I tried this on a machine that has never used the toolset before.

On first attempting to run the toolset on Win 10 x64 you get this prompt.



After you have finished that, try this link and follow instructions.

https://www.microsoft.com/en-gb/downloa ... 31a02=True

Once this procedure was followed, the toolset runs like a dream on Windows 10 x64 system with i3 6100 integrated graphics.

If it still doesn't work, try looking up the toolset .exe in installation folder and have a play around with display scaling tick box in the compatibility section of properties.

It's fixed!! Checking the box "Disable display scaling on high DPI settings" made it work!! Thank you so much to everyone who posted. I promise I'll make some great stuff for you all!

A little late on this but.. I also have the toolset set on higher priority.. I think just above average.. Could set it high too.. but I would advise against setting it to "Realtime"..

As soon as I checked "Disable display scaling on high DPI settings" everything started running perfectly. Not sure if it was that alone or if it also needed XP SP3 compatibility mode and Administrator privileges. (Though I'm pretty sure it needs Administrator privileges.)

Glad I could help. More builders in the community as a whole is a good thing.

You don't need to do anything with compatibility mode or setting priorities, it won't matter.

You could perhaps now work on the Heart of Winter module for Lockonnow.

nlyh wrote:You don't need to do anything with compatibility mode

I'm unsure if W10 has a better detection for it at runtime, but the kernel32 shim change is necessary if certain circumstances are present such as the CSIDL_PERSONAL virtual folder not being present (GPO or user modified). The default action for opening the folder looks for this directory and doesn't appear to have exception handling involved, crashing the toolset. Past that I don't know what else might be necessary.