It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hey guys,

welcome to KOTOR 2 / STAR WARS™ Knights of the Old Republic™ II: The Sith Lords™ (+ Restored Content mode)

Many people are experiencing a bug, where the main character is unable to move after a combat/fight.
Unfortunately, many people included me.
You will inevitably encounter this bug for the first time if you fight against the mine droids in the first lvl on PERAGUS, altough the version we are using is the fully patched (+ „fixed“) version on GoG (or Steam).

In this particular representation, this bug is exclusevly in KOTOR 2.
STAR WARS™ KOTOR 1 may also experienced some freeze glitches, but those stucked situations were triggered by different softwarecode that is not working together and most importantly, does not encounter you after every battle situation in the game.

WHAT IS CAUSING THE PROBLEM?

The „stuck after combat“ bug is caused, because the game engine starts malfunctioning if it as to deal with a combination of high fps and high refresh rate of the used monitor.
KOTOR 2 was released in 2004 where 60Hz and around 80fps have been default and the game engine refuses to deal with hardware of the current generation. Higher refreshrates are slowly becoming affordable and the created fps in a game like KOTOR 2 will be massive in 2021.

There are already some guides online that have helped some people with this bug, but certainly I was one of the few people where it did not work out with my hardware configuration. I use a PG279Q with G-Sync and 144 Hz, an i7-5820K and a GTX 1080.
I firmly believe that those people, who still haven’t been able to fix the „stuck after combat“ bug are most likely to use a similar monitor and hardware configration (or better).

SOLUTION FOR THE PROBLEM

First things first, I did a switcheroo and unplugged my main monitor and used an LG with 1920x1080p and 60Hz instead.
Started KOTOR 2, loaded my savestate and it worked :)
The character was able to walk again after a fight sequence was triggered.
So if you use a 60Hz panel yourself, there is a strong chance that you could be able to play KOTOR 2 properly without this bug.
When V-Sync is enabled, your graphics card will stop pushing out as many frames as it can and starts to sync the frames with the native Hertz (Hz) of your monitor panel.

Start KOTOR 2 from local Library -> Options -> Graphics -> Resolution -> set Resolution to your native monitor resolution but with 60 Hz
Then again -> Options -> Graphics -> More Options -> enable V-Sync -> Restart the game

Unfortunately, when I plugged in my main monitor again, and the bug was back again. So up to this point, the solution still didn’t come to full fruitition, if I wanted to play on my main monitor.
If you are still experiencing this bug too, lets go on:

Rightclick your NVIDIA settings in your taskbar -> NVIDIA Control Panel -> Display -> Refresh Rate -> 60 Hz -> Confirm
After that, again in your NVIDIA Control Panel -> Configure G-SYNC -> Disable G-Sync completely -> Confirm

After that, KOTOR 2 finally ran smoothly (as smoothly as "softlocked" 60fps and 60Hz can feel) and the bug was never to be seen up until this point.
G-Sync or FreeSync (if you use a panel that supports AMDs hardware) synces the frames that are rendered by the gpu with the refreshrate of the partnered panel that results in a feeling of a smooth gaming experience.
The problem is, this works mostly for games that are created during a time where this technology became popular (which is around 2014). That causes in an "old" game like KOTOR 2 to problems like this.
Keep in mind to enable G-SYNC or FreeSync again when you are finished with your KOTOR 2 session.
Hope this works for you you guys, have a great day. :)
Post edited December 22, 2020 by felyyy