Leaderboard

God damn. That's a late response.

I think it's because he didn't get the trigger for the HK factory quest. I just did a playthrough where I didn't get the cutscene where HK-47 tortures the HK-50 and all that happened when I finished the Ravager was I was in the Ebon Hawk and it was in hyperspace. That's probably one trigger for this glitch.

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

As you might know, fog is not working or at least not working properly in Aspyr's 2016 Steam patch for KotOR 2: TSL. An official fix for this issue doesn't seem to be in sight but luckily HappyFunTimes101 wrote a fix himself. To show the issue with the 2016 patch, here's a comparison between the Steam and the GOG version: As you can see, the fog is really screwed up in the latest Steam version while all other versions (4CD, DVD, gog, Steam legacy) look the same as the "gog picture". In other areas, the issue is not as visible when the fog is completely missing in the Steam version, but if you compare the two versions it's easy to see. And finally, here's what it looks like with HappyFunTImes101's fix applied: One more comparison, taken from the Ravager where the fog is not present at all in the Steam version: Additionally HappyFunTimes101 provides a completely new speed blur effect to get rid of that headache causing blur in the vanilla game while keeping some visual effect: It's a little hard to see on a still frame but if you compare the last two pictures, you can see that the edges of the screen are warped while running with Force Speed active. I really like that new effect, but it's optional when installing the fog fix, so it's up to you to decide whether you want it or not. Which brings me to the important part: How to install the fix First of all, here's the Read-Me. But I'll provide easier to follow instructions, originally taken from a reddit post by TonyKaku but slightly edited: Go here and download the contents of the Release folder. Copy them in your main KotOR 2 directory. If you don't want the changed speed effect, go to KotOR 2 directory \ shaders_override and delete fp_speedblur.txt. Start the game You should now have two folders called shaders_original and shadow_override in your KOTOR folder. Go into the shaders_original folder and open the first file with a program like Notepad++ locate the line that says "MOV result.color, r0" (second to last line usually) right above that line paste the content of the quote under "Fog Issue" that starts with PARAM p =.... Your file should look like this. Repeat this step for every text file in the folder that has the MOV result.color, r0 line (these are all files starting with fp). That can take some time and there might be ways to automate the process but explaining it might take so long that you're probably just better off doing the whole thing manually. After you pasted this into every file that has the MOV result.color, r0 line near the end, copy all text files into the shader_override folder. Launch the game, the fog should now be fixed This fix is definitely a big step forward for the usability of the Steam patch, which I always avoided due to issues like these. It's up to you to decide if it's easier to fix the fog in the Steam version or to get widescreen support in a different version but it's definitely a good thing to have this patch available. Maybe this fix can even be expanded to include the missing saber hilt textures (if that's even a shader issue). A big thanks to TonyKaku for posting this on the kotor reddit or I wouldn't have found it. To the moderators: I wasn't sure if that qualifies as a tutorial, so I posted it in the general section. If it is, please just move it or maybe just pin it so that the information doesn't get lost. Thank you Edit: I tried to apply the speed effect change to the older TSL version and to K1, but it's not as easy as I hoped it would be. The shader identified as the speed shader in shader_ident.txt just doesn't exist in these versions of K1/TSL so it can't be overwritten that way either. I assume it would be possible by editing the OpenGL32.dll file but I just don't know how to do that.

I like this one as a replacement for I_Mask_006, more than the fighter pilot type mask with the hoses above. (Though I do like that mask ...)

Another breath mask option: There's a lot of fixing required for some of these due to backface culling issues.