processor affinity(s)

[Arclight]

Try disabling HyperThreading (HTT), probably in BIOS.

[goldorak]

Ok a little bit of internet search has uncovered a possibile solution

"Vertex Buffer Objects are an OpenGL method of storing vertex data in video memory. Enabling Vertex Buffer Objects (Disable Vertex Buffer Objects=0) can improve performance in certain situations, however it seems KOTOR 2 [and 1] has some issues with this method and you should set it =1 if you want to resolve slowdown issues in the game (e.g. on Dantooine). It may also help reduce the incidence of crashes in KOTOR 2. Note that this setting does not exist by default, so you should create it under this section and set it to =1."

Source : http://www.tweakguides.com/KOTOR2_7.html

To do this find the swkotor.ini file which you will find in the games installation folder, open the file with notepad or any other text editor and scroll until you find the graphics section and insert the following line Disable Vertex Buffer Objects=1. Save the file. Start the game.

This solution applies both to Kotor and Kotor2.

[SteamWake]

Already tried that... in fact the version from steam already has that edit in the .ini file. Which kind of supprised me.

Hrm... maybe I will edit it out and see.

[SteamWake]

Well here I was all excited because I tried disabling HTT like arclight said and played for a few minutes.

I 'stress tested' running between zones, warping back to the ebon hawk, etc.

Wooh Hoo !

Till I got into some combat, a total lock with looping sounds

So game runs better but now it hangs up... Sigh.. I guess I will have to admit I lost 10 bucks

[Arclight]

Oh for the love of...

Good news is you fixed the problem relating to using dual-core CPU (though it seems a problem with HTT itself; still working fine on my quad). This new problem may well be heat related; console ports tend to overheat the memory before the core heats up (ie cooling doesn't spin up).

Could try lowering graphics and/or setting the cooling higher manually with something like Rivatuner.



On HTT: there's no such thing as a Pentium 4 dual-core. It's actually a single-core CPU with HTT. HTT creates a second virtual core. Though turning it off might fix some compatibility issues, it (your PC) is probably faster in day-to-day use with it enabled.

[goldorak]

The last versions of pentium 4 before the core 2 era were dual core versions.

[Arclight]

You're refering to Pentium D.

Pentium 4 is strictly single-core.

[SteamWake]

Originally Posted by Arclight

Oh for the love of...

Good news is you fixed the problem relating to using dual-core CPU (though it seems a problem with HTT itself; still working fine on my quad). This new problem may well be heat related; console ports tend to overheat the memory before the core heats up (ie cooling doesn't spin up).

Could try lowering graphics and/or setting the cooling higher manually with something like Rivatuner.



On HTT: there's no such thing as a Pentium 4 dual-core. It's actually a single-core CPU with HTT. HTT creates a second virtual core. Though turning it off might fix some compatibility issues, it (your PC) is probably faster in day-to-day use with it enabled.

I seriously doubt its heat related as I run other much more demanding games for long periods of time with no issues. Ive left SH4 running for hours while I mow the lawn or something with no issues. Ive experienced overheat issues before and this isnt it. Before I disabled HTT the vast majority of combats would play through with the occasional freeze however in that case I can usually recover with the three finger salute. With HTT disabled it locks up hard and only the reset button will recover.

I already tried reducing the settings for kotor to their lowest with no change in behaviour.

Yes its set for native resolution.

[Arclight]

Well, the point is really Kotor being a console port. Like I said, they tend to over-stress the memory. But if you say you're certain, I believe you. To be honest I didn't think it was the problem anyway, merely a suggestion that should be considered.

(for example, I can run Fear maxed at 100+ FPS, but the card locks up from heat in about 30 sec, while I can run much more demanding stuff at ~30 FPS indefinetly, theoretically)



That said, I would still consider cranking the cooling up manually an option to pursue, if only to eliminate it as a solution. Got nothing else at the moment anyway.