Search the Community
Showing results for tags 'linux'.
Found 4 results
-
The nostalgia bug recently bit me and I thought it might be fun to play some KOTOR2, with mods of course! After a bit of tinkering I think I have a working mod set up running on Linux. I thought that my experience might be useful to someone else attempting to install mods on Linux or a maybe a Steam Deck. A fair warning though, I have not had time to play test yet beyond running around on Peragus so there could be issues that I haven't discovered or steps that I forgot that I did. I'll try to update if I run in to any issue but I'm not promising anything, I have a nasty habit of spending days modding a game only to never actually play it when I'm done! First install the native Linux version of KOTOR2:TSL from steam Next download the latest KOTORModSync (currently 1.0.2) https://github.com/th3w1zard1/KOTORModSync - linux-x64.zip - KOTOR.Modbuilds.Rev10.zip (Contains KOTOR2_Full.toml modlist we will be using) The install directly can be found at ~/.local/share/Steam/steamapps/common/Knights of the Old Republic II/ All regular game assets are in the subdirectory 'steamassets', this is where mods will be installed, not in the main game install directory Run the game once to make sure it runs properly, I'm using Arch Linux with Hyprland(Wayland compositor) so I needed to add 'SDL_VIDEODRIVER=x11 %command%' to my launch commands to get it to run properly. The kotor2.ini found in the steamassets directory is not used, delete it. The correct kotor2.ini is found at ~/.local/share/aspyr-media/kotor2/swkotor2.ini Create a symlink to it in the steamassets directory ln -s ~/.local/share/aspyr-media/kotor2/swkotor2.ini swkotor2.ini Backup you KOTOR2 directory in case you make a mistake: tar zcvf kotor2.tar.gz Knights\ of\ the\ Old\ Republic\ II You can restore with rm Knights\ of\ the\ Old\ Republic\ II tar zxvf kotor2.tar.gz Open KOTORModSync and load the installation file (KOTOR2_Full.toml) Create a directory to store mods in (I use ~/Games/KOTOR2Mods/) Go through the mod list and download each mod to you mod directory from the link. Make sure to download The Sith Lords Restored Content Mod as a zip from the google drive link and not the regular exe installer. There are also a few cases where if you download a mod form ModNexus instead of DeadlyStream the name of the zip file will not be correct and needs to be renamed. As of writing this there are 2 issues with this mod list, this first one is with 'Reflective Lightsaber Blades' (New_Lightsaber_Blade_Model_TSL). currently the included version of Holopatcher has issues reading info.rtf files with non UTF-8 encoding and a error window will pop up. This does not actually appear to affect the installation of the mod and can be ignored. This issue will be fixed in the next relese. The second issue is with 'Improved AI' and requires some work. For some reason the zip file you download contains the mod compressed into a self extracting 7z file. KOTORModSync does currently not appear to be able to extract self extracting 7z files on Linux. My Solution was to extract the mod manually, repack it as a 7z file and alter the install instructions (7z on linux can handle 7z SFX exe files just fine). unzip imporvedai.zip cd Improved\ AI/ 7z x Modified\ AI.exe 7z a ModifiedAI.7z Modified\ AI Move the new 7z file to you mod dir and change the mod install instructions to: 1. Extract <<modDirectory>>\ModifiedAI.7z 2. TSLPatcher <<modDirectory>>\ModifiedAI\Modified AI\Install AI Tweak.exe 1 Set your mod directories. Mod Location is the mod dir you created (~/Games/KOTOR2Mods/ for me) and Kotor Directory should be '~/.local/share/Steam/steamapps/common/Knights of the Old Republic II/steamassets/' - Run pre install validation, if there are any issues detected you will need to fix them. You can find a log file in the KOTORModSync directory that can help you troubleshoot issues. - Choose 'Mock case-insensitive filesystem' - Run 'Fix duplicate files/folders' - Click 'Start the install' and cross your fingers, hopefully you set up everything correctly and installing mods should complete successfully. This takes quite a while. - All files in steamassets need to be lowercase, in some cases files installed by the mod will have uppercase lettering. There is probably a better solution but I created the following script and ran it in each directory that contained files that needed to be renamed. Be VERY careful not to run it from any other directory: # !/bin/bash for file in *; do #Suppresses all errors as not to spam errors when file does not need to be renamed mv -v "$file" "$(echo $file | tr '[:upper:]' '[:lower:]')" 2>/dev/null done I was going to try and use Reshade shaders with vkBasalt but unfortunately that was to much for my poor laptop's integrated graphics but it did seem like vkBasalts SMAA anti-aliasing worked better the KOTOR2's build in AA so I stuck with it. To get vkBasalt to work with KOTOR2 on my set up I need to run it through gamescope. Install gamescope, I'm using gamescope-git from AUR but regular gamescope from extra my work for you. If you're trying to follow this guide on a steamdeck you should already be using gmescope. See https://wiki.archlinux.org/title/Gamescope Once you've installed gamescope add 'gamescope -h 1080 -H 1080 -f -- %command%' to your steam launch options and make sure you can launch the game Install vkBasalt fro AUR yay -S vkbasalt copy the default vkbasalt config file to your KOTOR2 dir cp /usr/share/vkBasalt/vkBasalt.conf.example .local/share/Steam/steamapps/common/Knights\ of\ the\ Old\ Republic\ II/vkBasalt.conf Enable SMAA and whatever else you want (I you are going to give reshade shaders a try then the best source of shaders seems to be here: https://github.com/gripped/vkBasalt-working-reshade-shaders) effects = cas:smaa Enable vkBasalt by adding 'ENABLE_VKBASALT=1 VKBASALT_LOG_FILE="vkBasalt.log"' to your steam launch options. My finally launch options look like this: SDL_VIDEODRIVER=x11 ENABLE_VKBASALT=1 VKBASALT_LOG_FILE="vkBasalt.log" gamescope -h 1080 -H 1080 -f -- %command% And that's it! I hope this will be of some use to somebody
-
Large work has gone into ensuring the patcher can mirror TSLPatcher 1:1. Some additional features have been added by request and some TSLPatcher bugs have been fixed. Source code can be found here: https://github.com/NickHugi/PyKotor/tree/master/pykotor/tslpatcher If you've ever wondered why TSLPatcher is throwing an error with your mod or why certain patches don't seem to be applied correctly with TSLPatcher, this is a great resource to finding the problem. If you don't understand or want to learn Python, large work has gone into documenting each function and public classes. Just read the docstrings. If you ever needed to install a TSLPatcher mod on Mac or Linux, the library will run natively (without wine) on most distros of Mac and Linux - and resolve case-sensitivity issues. The PyKotor library is the same library used for the HoloPatcher and the Holocron Toolset projects. - both are inherently cross-platform KOTOR tools. This post isn't made to be a plug to HoloPatcher or the toolset, but more a general resource for users and modders alike. -
After zero success with making a heavily modded Legacy PC version playable via Wine past a certain point, I was going to revert to Aspyr’s official Linux port because, for all its flaws, it might be the only stable working alternative. However, I found that TSLRCM’s installer (which runs without a hitch under Wine) does not understand how directories are arranged in TSL on Linux. On Linux, “/home/<username>/.local/share/Steam/steamapps/common/Knights of the Old Republic II” — which kinda corresponds to “C:\Program Files (x86)\Steam\steamapps\common\Knights of the Old Republic II” on Windows — does not directly contain the files and folders affected by TSLRCM’s installer. All of them are located in the “steamassets” subfolder instead. However, TSLRCM’s installer, which apparently takes care of locating the required folder by itself, does not recognize this difference and installs everything in the main “Knights of the Old Republic II” folder, as it would on Windows (where this would work fine, because dialog.tlk, Override, StreamVoice etc. are in their supposed places). Unfortunately, I have no idea on how to manually choose the folder for installing TSLRCM (and whether is it really possible), and the only other option I think of is some symbolic link hacking and manually moving a few files. I know I could use Steam Workshop to install TSLRCM but not only it’s one out of several dozen mods I’m going to install, it’s not even the first one — the first one is going to be ShiningRedHD’s Ultimate Character Overhaul. Workshop’s unsuitability for complex TSL mod builds is well-known. Is there a way to force TSLRCM’s installer to unpack files into the folder I need, instead of the folder it chooses automatically? -
This is a brief list of the graphical issues I found on KotOR 1 using Linux (Kubuntu 21.10) with Proton 7.0-1, I am using an Intel UHD 630 graphics card with the newest drivers available. This list is for anyone who wants to know wich issues they're facing by using an OS that the game wasn't meant for. Keep in mind that KotOR is almost 20 years old and having minor graphical problems is not a big deal. 1.Stealth mode doesn't make the player invisible (doesn't affect gameplay) It looks like an energy shield. On earlier proton versions the character looked entirely black, so this is an improvement. 2.Camera effects don't work properly (might affect the game's style, but not gameplay) The droids on first person view should have a camera effect to them. HK should have a red effect and T3 a blue effect. It also happens to the cameras used on terminals. On earlier versions the screen turned completely black, impacting the gameplay. It also affected the swoop races, making them unplayable. 3.Textures are overly saturated In too dark or too bright places, or turning the brightness too high or low will make the textures ovely saturated, it doesn't affect anything, but it looks weird. It happens on any Proton version. 4.HK-47 eyes don't glow 5.Framerate might be lower than on Windows, but it's not a big issue. KotOR is optimized poorly for modern machines, it doesn't matter how good your PC is, there's always going to be frame dips. Compared to Windows, Linux has more frame dips, again, it's not unplayable. 6.Game saves have a black icon instead of a screenshot. For some reason, on linux this game doesn't do a proper screenshot to show the player what they were doing. Some Windows games running under Proton are surprisingly stable and work well enough for Linux users, with the Proton update things got even better (not only on KotOR, but on a lot of other games). Steam Play on Linux (debian-based distros) is a viable alternative for Windows. Most of the issues can be fixed by disabling pixel shading in the graphic settings.
