PlayableShow Details
Unknown
LIBGL_KOPPER_DRI2=1 MESA_LOADER_DRIVER_OVERRIDE=zink MANGOHUD_CONFIG="fps_limit=72,no_display" mangohud %command%
Set the option Soft Shadows=0
Models are stuck as LOD versions on latest version of Mesa in Fedora 42. Launch options to prevent this are: LIBGL_KOPPER_DRI2=1 MESA_LOADER_DRIVER_OVERRIDE=zink
Could not focus fullscreen window on Proton-GE10-3
Proton versions above 7 will have infrequent memory access violation crashes. Fix this by using Proton 7 (GE and regular work fine).
After the latest Mesa update on Fedora 42, the models kept loading in as the LOD models. I tried Proton-GE 10-3 to fix it and it was unable to be played. Upon forcing zink the LOD on models worked as expected.
Shortly after resolving this issue I found a consistent crash on my system at an area early on in Kashyyyk that would crash when loading a new area from that area. Switching to Proton 7 fixed this issue.
Mangohud is used solely to limit the FPS to 72 (1/2 of 144) so the game can run at half my refresh rate and not experience the glitch that makes you unable to move during combat. Limiting your FPS anywhere between 60 and 75 seems to prevent this from happening, whether it is through V-Sync or Mangohud, it does not matter.
LIBGL_KOPPER_DRI2=1 MESA_LOADER_DRIVER_OVERRIDE=zink MANGOHUD_CONFIG="fps_limit=72,no_display" mangohud %command%
set the option Soft Shadows=0
LOD Models always loaded without using zink
Could not focus fullscreen window on Proton-GE10-3
After the latest Mesa update on Fedora 42, the models kept loading in as the LOD models. I tried Proton-GE 10-3 to fix it and it was unable to be played. Upon forcing zink the LOD on models worked as expected.
Works flawlessly, no configuration needed
Runs perfectly without any tweaks. Didn't need to downgrade Proton or install any patches (e.g. for resolution or fixes). Just launched and played. Had one early crash in 4 hours, but couldn’t reproduce it afterward.
I had to turn off soft shadows in the graphics settings for environmental textures to load.
The game would sometimes minimise after cutscenes/video
Before trying GE Proton, there was no cursor.
After some cutscenes, the game would minimize for some reason. Not that big a deal overall.
Crashed after a specific cutscene, fixed by turning down graphics to their lowest / switching to Experimental.
I was actually able to fullscreen and everything without any mods / patches, despite some other reports I have read.
Launch options suggested by other posts caused the game to not launch at all. Proton 6 worked for me.
Moved it down to 3 Watts. If I noticed any stuttering I would change to 4. Moving it back to 3 when I noticed the framerate with go higher than the 30 fps I locked it to in Heroic Games Launcher.
When I used the force feat "Knight Speed" I noticed some artifacts, nothing game breaking but I couldn't remember if that is what it looked like on Xbox where I originally played it many moons ago. If I were to guess if you turn off FSR in the games profile it might help.
mangohud %command%
The transition between cutscenes and the game are longer in fullscreen. Also the game sometimes crashes in those transitions (in both windowed and fullscreen, but fullscreen more often).
Mousewheel scroll speed had to be adjusted, as it otherwise skipped options when scrolling (noticed something similar in Gothic 2).
Very frequent crashes. Near the end of the game, I could not brute force through a consistent crash and had to resort to finishing the game on Windows 🤮🤮🤮🤮
Gamescope could maybe fix frequent crashing. But I don't use it, and when I was getting desparate near the end of the game, I couldn't launch the game with gamescope, but that might have been me misconfiguring it somehow.
Proton 7 seems to work the best on my machine without producing many artifacts and good performance. My game is also patched.
gamemoderun %command%
Stealth field effect/texture for character is broken or missing, some other minor artifacts throughout the game but not game-breaking.
Must add "AllowWindowedMode=1" and make sure "Fullscreen=0" in swkotor.ini
Controllers are not natively supported on the PC version of the game, but you can make your own KOTOR profile or download community profiles in steam if you want to use a gamepad. I play with M&K
You can actually patch this game with many of the display/resolution fixes if you follow this tutorial. https://www.youtube.com/watch?v=DSizFARnwyM&t=120s But you must patch the game in Windows first, as some of the patching tools that modify the game's executable will not work properly under Wine. But once you patch the game, you can simply port over the patched game files over to Linux (The executable, Override folder, and Movies folder) and it will work just the same as it does in Windows! Overall the expirence is great once you get it set up. There are definately occasional bugs and artifcats, but its perfectly playable.
swkotor.ini: under [Graphics Options] FullScreen=0 AllowWindowedMode=1
Game wouldn't work in fullscreen, had to use config files to use windowed mode
If VSync isn't on or the game isn't capped at the refresh rate of the monitor you will not be able to move after combat
gamescope -w 1920 -h 1080 -r 60 -f %command%
Works out of the box with Photon experimental and setting the Launch Options as I have added them below "gamescope -w 1920 -h 1080 -r 60 -f %command%"
Other than the fullscreen issue works great
Escaping the fullscreen window would cause the game window to go blank
Escaping from fullscreen leaves the game with a black screen. It's possible to come back by trying to close the window (game will ask for confirmation, and the screen will return to normal).
Despite the fullscreen problem, the game runned smoothly with version 7.0-6.
Game requires tinkering to launch it and even after it you can get softlocked, by CTD's like me on Tatooine (over 12h of game)
gamescope -w 1920 -h 1080 -r 60 -f %command%
Using fullscreen mode makes game unplayable since any FMV will cause the game to Alt-Tab and this causes the game to create infinite loop of maximizing and minimalazing
Game will after few minutes of playing drop FPS to sub 30
Game runned smoothly excluding slow down, but when reached Tatooine the game would crash after less than a minute of playing after leaving Anchorhead
The latest Proton (9.0-2 as of this writing) will not allow you to play the game. Instead you will need to switch to an older version of Proton.
v8.0-5 will run the game but with the potential to drop you out onto the desktop during screen resolution changes (e.g. game -> in-game video). This is not a crash-to-desktop. So, if that happens you can simply use your window manager's application switching methods to get back into the game to continue.
The experience appears to be smoother with v7.0-6 where this does not appear to happen (or at least by far not that often).
There are no other limitations (e.g. any in-game options to be avoided). Everything the game has not greyed out by itself can be used.
Advanced (tinkering option)
Using GameScope/GameMode. This is entirely optional.
You can add the following as launch option if you want. This will also center the in-game videos on screen.
gamescope -w 1600 -h 1200 -W 1600 -H 1200 -f --mouse-sensitivity 1.8 --force-grab-cursor -- gamemoderun %command%
Resolutions may need to be adjusted in case they do not work for you. If you prefer a borderless window, use "-b" instead of "-f".
For further information on the command line options used, check `gamescope --help` in Terminal.
If neither "gamescope" or "gamemoderun" is not available, check with your distribution's package manager to install them (package names on Fedora "gamescope" and "gamemode" respectively).
Some crashes, especially if changing screen resolution
Have to switch to Proton version 8, and then it seems to run perfect.
It's playable, but needs a few tweaks for modern player.
Whenever I was changing the location, even who game was muted from the audio panel, it would still unmute itself.
In swkotor.ini changed/added FullScreen=0 AllowWindowedMode=1 Otherwise fullscreen on alt-tab or notifications made the game constantly black screen.
Text in menu is not visible
Tried pretty much everything but the text is not visible, it's as if the textures aren't loading.
On my Steam Deck the game works just fine. Not on my desktop though, that's a whole different story.
I tried all versions going back to Proton 3.x up to the latest Proton Experimental and ProtonGE. I also attemted using GalliumNine and WineD3D but no matter what, the text in the main menu is not visible. It shows for about 1-2 seconds and then disappears.
Not sure what causes this as the game runs fine on my Steam Deck. I did also try different configurations of the game, vsync on/off, hardware mouse on/off, anisotropic filtering, msaa etc etc. No change.
Game runs, but is unplayable.
Does not work out of the box. Game runs, but only a small portion of the visuals are visible. Unable to see or interact with menu. Unable to close window without clicking on "stop" in steam.
Only tweak was community layout for controls - "Original Xbox Controls"
The game out of the box runs but doesn't support widescreen, supporting widescreen requires quite a bit of tweaking
The main issue I faced, when modding the game for 1080p, I wasn't able to tab back into the game if tabbed out, the solution eventually was to run the game windowed, turn on virtual desktop and make the game fullscreen with window manager keybind, in my case kde plasma.
Slowdowns here and there, might happen on windows as well, it's been a while since I tried the game there
I was able to have a pretty good experience using uniws, fade-widescreen fix, hud correction and ws models for kotor. If you don't mind the look of the vanilla game, it is playable, but at a minimum you will want to install K1 community path, the installer for mods such as said patch is available natively on linux, so it's not too bad.
Game works just like it does on Windows(it barely launches and has awful memory leak issues)
This game is very broken, save often in many slots
It works out of the box for me in every way I expect this game to run. Which is to say, only with Vsync on, and with the monitor refresh rate set to 60. Otherwise you get the movement glitch after combat. You also will run into memory leaks, save the game often and in different slots(the game has many ways of corrupting saves if you're reckless, regardless of OS)
Change control setting to community "Galactic Basic"
Low FPS (~30) in Levels with water/transparency effects (Manaan,...)
The game likes to crash. Especially when loading new levels.
I played trough the game with the following mods installed:
- Kotor Community Patch
- UniWS
- Bodies Stray
- Security Spikes Fix
- KotOR 1 Remastered
- Selphadur's Kotor Texture Redux
- Complete Character Overhaul -REDUX- (Ultimate HD Pack)
- Better Skyboxes
Whenever a new Level is loaded (which is often), there is something like a 20% chance of the game crashing. Therefore saving before each door is necessary.
I kept a modded and a unmodded version of the game, beacause sometimes (about once per hour) the modded version of the game was unable to load a level, so i deleted the modded version (except the saves), and replaced the files with the vanilla version. This trick got me trough all doors.
Sometimes it was the other way around: The unmodded version would crash, but the modded version would not.
TL;DR: The game is fully playable but only with mods, crashes and a lot of patience. So the average gamer would propably be really annoyed, even though most of the crashes are presumably the games fault.
3 watts, 30fps lock, highest resolution due to a bug
Audio sometimes cut out during conversations
Windowed causes mouse issues
There is a gameplay bug if you move your character while quicksaving
ENABLE_VKBASALT=1 gamescope -w 1920 -h 1080 -W 1920 -H 1080 -r 60 -f %command%
As others have mentioned, anti-aliasing breaks some cutscenes like the one with Carth at the beginning. On Windows they work fine but frame-buffer effects do not work instead (the mentioned Carth cutscene should have a blue-ish static effect applied to it, but it's missing on Windows).
So, to remedy some of the jaggies that stem from not using any AA, I recommend enabling vkbasalt with SMAA. It's not going to be as good as native AA, but it will clean up most of the jaggies. Downsampling from 4k to 1080p made little visual difference (if any) so don't even bother.
For some reason, MangoHUD refused to work no matter what I did.
Mods work just fine. hires-patcher.bat doesn't execute properly though, so I had to run
wine hires_patcher.exe 1920 1080 no swkotor.exe
from the terminal instead.
It will work out of the box, I would recommend following the "Make your KOTOR playthrough more enjoyable" guide and installing the community patches and widescreen support.
Disable anti aliasing, otherwise some textures could be missing.
Used a custom executable to utilize the full 16:10 screen
Changed to 40fps
Happens coming out of sleep, can be fixed by restarting game
Every once in a while, the very right side will flicker a small garbled mess
If you click through the fmv cutscenes, the game will sometimes hang on the loading screen.
Works perfectly out of the box
Windowed mode fix is no longer needed with Proton 7.0-5
Removed load last save button
Followed another user’s recommendation of disabling AA after encountering the cut scene bug. I have played over 70 hours in this game so far and have only had a few minor hiccups that were fixed by exiting and starting the game again.
Won't run :(
Changed the values in the file, won't work. Tried to install the community patch, doesn't work either. Funny enough, it works like a charm on my old laptop.
Tried experimental and GE, as well as several older ones, if anyone knows how to run this on steam deck please let me know!
Works fine with the exception of the restriction to 4:3 aspect ratio.
Works only in 4:3 apect ratio.
When I put the Deck to sleep mode, and started playing again some constant crackling started.
Came across some minor texture flickering and some in-game cutscenes weren't playing at all.
I experienced some of the issues listed above, other than that game works properly. These bugs went away as soon as I restarted the game.
limited tdp to 9 watts
occasionaly game would only show hal screen on launch and need restart
