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

ThornsM wrote:There's 200GB spare. With the Client extension it still crashes the same, but has added lag, just tried that.
I've always got the autosave switched off in the toolset, a crash during an autosave makes quite a mess of the module.

I had it run fine on a Windows 7 installation yep, but no longer have access to that OS. On Windows 10, regardless of compatibility modes, it just keeps on crashing though.

Type /mpredict


As for windows 10, look for DirectX9 Redistributable packs.

It seems to have stabilised after the removal of the motherboard utility "Asus AI suite 3". I've normally avoided installing such optional things, not sure why I succumbed to it this time.

With that gone, the game has run without error for 8 hours, without the presence of the client extension or separate dx9 drivers.

The only oddity left is an erratic issue with the toolset. When scaling an object it often does not update the on-screen size of the object. One has to scale it multiple times, hoping it will update each time. The scaling is applied correctly if you close the area and open it again, though that is hardly convenient.
At least it isn't crashing, so I'll humour this one foible.

I do run NWN2 on Win 10 64 bit with client extension without much issues. There are some crashes here and there, but not more like on any other OS I used so far.

ThornsM wrote:It seems to have stabilised after the removal of the motherboard utility "Asus AI suite 3". I've normally avoided installing such optional things, not sure why I succumbed to it this time.

With that gone, the game has run without error for 8 hours, without the presence of the client extension or separate dx9 drivers.

The only oddity left is an erratic issue with the toolset. When scaling an object it often does not update the on-screen size of the object. One has to scale it multiple times, hoping it will update each time. The scaling is applied correctly if you close the area and open it again, though that is hardly convenient.
At least it isn't crashing, so I'll humour this one foible.

Yes I found the same issue with the toolset.. it's still not acting right. Where there should be an immediate change in size, it seems to just not recognize you changed it or something? Anyone else having this issue?

LISA100595 wrote:

ThornsM wrote:It seems to have stabilised after the removal of the motherboard utility "Asus AI suite 3". I've normally avoided installing such optional things, not sure why I succumbed to it this time.

With that gone, the game has run without error for 8 hours, without the presence of the client extension or separate dx9 drivers.

The only oddity left is an erratic issue with the toolset. When scaling an object it often does not update the on-screen size of the object. One has to scale it multiple times, hoping it will update each time. The scaling is applied correctly if you close the area and open it again, though that is hardly convenient.
At least it isn't crashing, so I'll humour this one foible.

Yes I found the same issue with the toolset.. it's still not acting right. Where there should be an immediate change in size, it seems to just not recognize you changed it or something? Anyone else having this issue?

I have found the same issue affecting the toolset on a completely separate Windows 10 installation, so may well be a more common issue.
Also, if an object is resisting scaling or colouring changes in this manner, I've found that setting it to placeable/environmernt object and back again forces the display to update correctly.

ThornsM wrote:

LISA100595 wrote:

ThornsM wrote:It seems to have stabilised after the removal of the motherboard utility "Asus AI suite 3". I've normally avoided installing such optional things, not sure why I succumbed to it this time.

With that gone, the game has run without error for 8 hours, without the presence of the client extension or separate dx9 drivers.

The only oddity left is an erratic issue with the toolset. When scaling an object it often does not update the on-screen size of the object. One has to scale it multiple times, hoping it will update each time. The scaling is applied correctly if you close the area and open it again, though that is hardly convenient.
At least it isn't crashing, so I'll humour this one foible.

Yes I found the same issue with the toolset.. it's still not acting right. Where there should be an immediate change in size, it seems to just not recognize you changed it or something? Anyone else having this issue?

I have found the same issue affecting the toolset on a completely separate Windows 10 installation, so may well be a more common issue.
Also, if an object is resisting scaling or colouring changes in this manner, I've found that setting it to placeable/environmernt object and back again forces the display to update correctly.

Ah good call on that. Will be fine when only working on a small number of placeables. Long Term or Larger Scale project.. not so much however.

Ok so today I was fed up with trying to rescale objects in the toolset and deleted NWN2 (renamed my documents nwn2 to OLD first so it wouldn't overwrite). Then reinstalled using my 3 original Disks.

After that I took the program file x86 copy (fully patched) i had on my old drive and pasted it over the top of my fresh installation.

This worked very well, I am having no more issue with the toolset or the game now... for now. lol

I'll let you know if there are any issues in the future.