STAR WARS™ Knights of the Old Republic™ II: The Sith Lords™

STAR WARS™ Knights of the Old Republic™ II: The Sith Lords™

117 ratings
Fixing innability to move after the combat on 120Hz+ monitors
By Derpcrawler
Are you experiencing bug that causes your game to essentially break after each combat sequence? Is you character not responding to movement controls? Are you playing on higher refresh monitor (120Hz+)? Then I might have a fix for you.
9
7
7
7
7
7
8
7
7
5
5
9
6
5
5
5
5
5
5
5
5
5
5
   
Award
Favorite
Favorited
Unfavorite
The bug
Guide Update 2024:

This guide was written back in 2015, when neither Nvidia, nor AMD had exposed settings for limiting framerate without engaging Vsync or locking refresh rates to 60Hz, so RivaTuner was most convenient way to achieve framerate lock.

In 2024 both AMD and Nvidia have new apps and driver settings where you can limit framerates on game-by-game basis. The whole idea of this guide is to limit framerate to something that won't break the game during battles. For me it was around 72FPS.


TL;DR Limit framerate the most convinient way to around 70-75FPS. Be it RivaTuner or native AMD/Nvidia apps. If you decide to go with RivaTuner and MSI Afterburner, this guide is still very helpful.


Are you experiencing bug that causes your game to essentially break after each combat sequence? Is you character not responding to movement controls? Are you playing on higher refresh monitor (120Hz+)? Then I might have a fix for you.

After encountering this bug myself and researching it on the internet, the only apparent solution was to toggle Vsync ON in settings. That did nothing for me and game kept breaking after each combat sequence, since it kept running at 144FPS even with Vsync.


Cause of the bug
After thinking about whole thing for almost two hours I realized, that probably just as many other older titles, game has it's physics and some mechanics attached directly to the framerate. That's why it would explain that people "fixed" this issue turning on Vsync. Only issue is, this "fix" would work only for people who use old ~60Hz monitors, since Vsync would force game to refresh at 60FPS.

For people with modern gaming monitors Vsync wouldn't work due to the fact that game even with Vsync would refresh at 120/144FPS causing engine to bug out. The exact breaking point appears to be around 90FPS.
The Fix
In order to fix this issue you need to limit your framerate.

There is couple of methods of doing so, but I will discuss the easiet one.

You need to install RivaTuner Statistics Server. If you have overclocking utilities for your GPU such as MSI Afterburner, RivaTuner comes included by default.

Steam has "EVGA Precision X" tool, which also includes RivaTurner Server as part of it package. You can download it from Steam here: https://steamhost.cn/app/268850/

Open RTSS, then follow 3 easy steps:
1. Press "+" or "Add" button in the bottom left corner of the window
2. Locate KOTOR2 executable in your Steam folder and add it.
3. Find option called "Frame Limit". Next set it either 60FPS limit or 72FPS limit in game. Limit should depend on your monitor refresh rate and should be half of that to eliminate stutter. So if you have 144Hz monitor, select 72FPS limit.


After you do it, you should be done and no longer experience any movement issues after combar in KOTOR2.
40 Comments
Hobo 11 Jan @ 9:34am 
I just limited to 80 fps on NVIDIA panel left refresh at 175 all chillin now
Derpcrawler  [author] 1 Jan @ 5:28am 
Uninstall Linux. But seriously, did you really think Driver/Kernel level overclocking tools designed for Windows work on Linux? Your best bet, is that Linux drivers are as good as Windows and have ways to enforce frame rate caps similar to Nvidia control panel on Windows. I know Steamdeck has frame limiter, so you might be able to look into how it's implemented and if it's some common Linux package.
War Criminal Phlox 31 Dec, 2024 @ 5:59pm 
I'm using linux mint 22 and EVGA won't open, any way to fix that?
seekr 14 Apr, 2024 @ 11:43pm 
Btw you can do this same on the NVIDIA control panel. But yeah limiting the fps to 72 helped me also, thx.
Raphael stronso 2 Mar, 2024 @ 6:20am 
Ty, RTSS saved me. I normally can't cap fps because of my amd GPU.
SLOP_DOG 30 Sep, 2023 @ 5:02am 
riva worked tyvm
KOMO 2 Jun, 2023 @ 2:31am 
If you have an AMD GPU this is the only possible fix, at least for me. I tried pretty much everything, Radeon Chill doesn't work for KOTOR2, you can opt for AMD FRTC, that one works but it's a global setting, so it's annoying to switch every time. Enabling/disabling VSYNC: didn't work. Before any of you geniuses mention, yes, the option of @60HZ is selected but it still caps at 144, I don't know why. And yes, in the .ini file it's 60 as well, it just doesn't do anything. Any other game graphic options that AMD application has, I tried them all, every combination that have worked for some others in the past, none of them did the trick. Then I realized I already have RTSS because of MSI Afterburner, and gave it a shot, ta-da! it's the only thing that worked for me. I was going to prepare a Steam guide for that, then I saw this one. If you have an AMD GPU, and you're tired of seeing guides that say "bro just go to NVIDIA Control Panel, 3D settings, frame limit to 60" this one is for you.
Bookhead 10 Jan, 2022 @ 8:35am 
Kind of funny how they added all these options for 120+ hz when it breaks the game. Why didn't they fix that in the huge update?

Also sad to know there is no *real* fix for this problem. (as in being able to play at 90+ fps refresh rate in game)
GrayFox 9 Jan, 2022 @ 3:36pm 
Hi,
I've managed to fix this on my rig - rtx 3070 with 144hz 1440p monitor- simply go into nvidia control panel and select KOTOR 2 , and then enable v sync from there AND cap the max frame rate at either 60 or 80. No more problems!
Pingger Shikkoken 8 Sep, 2021 @ 10:15am 
The easiest: go to Graphics Settings > Resolution > Select resolution with '@ 60 Hz', then enable V-Sync.
The second easiest one is: open swkotor2.ini, find both occurences of "RefreshRate" change value behind '=' to 60