Leaderboard
Popular Content
Showing content with the highest reputation on 03/18/2022 in all areas
-
2 points
Version 2.0.1
897 downloads
The Harbinger is a victim of double-sabotage, by both a group of cult assassins and one crazed protocol droid, who did their jobs a little too well. There are missing pieces of the ship's hull geometry, UV errors, lightmapping issues, and broken animations all throughout the ship. Let's fix them up! Installation: Download the 7z file and extract to your override folder, found in the same directory as your main game executable. For Steam installations, this would be "Steam\steamapps\common\Knights of the Old Republic II\override". 7z files can be extracted with Archive Utility on macOS, or with programs like PeaZip on Windows and Linux. This mod also includes an optional 16x upscale of the cracked window texture, which can be found in the "Additional" subfolder. Simply take the .tpc out into the main mod folder to activate it, if you wish. Also, be sure to uninstall version 1.0, "Harbinger Bridge Repairs", if you previously installed it. This mod is made for and tested on PC, so if you are attempting to install this for a different platform, you will have to let me know how it works for you. Uninstallation: Remove the folder "Ultimate_Harbinger_Model_Repairs_v2.0.1" from your override. Included Files: Compatibility: Users should expect full compatibility with any other mods, so long as they do not modify/replace the above files. For this mod I have fixed up 56 of the shipd's total of 57 submodules, so it will not likely be compatible with mods that replace any of the area models for the ship. The mod is therefore not compatible with "Harbinger Hull Fixes" by DarthParametric, though it fixes the same issues, as well as a great many more. This mod may be compatible with other lighting mods such as "A Darker Peragus REDUX" by Malkior, and "...A Darker Peragus" by Canderis. The four lightmaps included in this mod are all custom-made and named, so there should be no file name conflicts, it is simply a matter of how they look in-game against those mods' lightmaps. This mod is fully compatible with visual improvement mods such as Kexikus' "TSL Backdrop Improvements", and most any texture mods. It also includes an optional upscaled version of the cracked window texture that I recommend, which you can find in the "Additional" subfolder. Acknowledgments: Huge thank-you to Symmetric, Purifier, Ndix UR, and seedhartha for making importing to Blender simple using KotORBlender, Cortisol for making my life easier with the Holocron Toolset, and ndix UR for making image compression convenient with tga2tpc. This modification is not supported by Obsidian Entertainment, Lucasarts, Disney or any licensers/sponsors thereof. Use of this modification is at your own risk and neither the aforementioned companies nor the author may be held responsible for any damages caused to your computer via this modification's usage. -
1 point
Version 1.1.0
8,167 downloads
Full Description: The mysterious arrival of the Republic hammerhead warship is one of the most ambitious and engaging cutscenes in TSL. Unfortunately, ambitious cutscenes can be a harbinger for more than just a man with severe psoriasis -- players may experience issues ranging from cutscenes stuttering and looping, loading screens before and after loading a new module mid-cutscene, breaking animations, to game windows minimizing and skipping the cutscene entirely, permanent black screen, and even game crashes. Thus this mod's mission was twofold: 1) Provide a range of general improvements and fixes that everyone will benefit from regardless of cutscene performance, as well as 2) Create a more stable version of the cutscene that generally performs well on any device. I am happy to report that results have been exciting: 1) General improvements - Atton now always faces the correct direction when speaking to you - Kreia actually shows up meditating in the morgue when you hear her speak, rather than standing right behind Atton - Kreia no longer visibly stands behind Atton in certain earlier shots of him speaking - The Peragus mining facility asteroid is no longer right outside the Harbinger window before it actually enters the asteroid field 2) Performance improvements All in-game portions of the cutscene are now rendered in the same module -- your game will no longer be trying to load an entirely new module twice over, all while trying to play pre-rendered cutscenes. This means that your game's mid-cutscene workload has been drastically reduced, and so issues known to occur specifically with the Harbinger Arrival cutscene are much less frequent. I have also scripted in "guardrails" for many minor glitches that can occur mid-cutscene. Note that this is not a 100% guarantee players who were having issues before never will again; TSL is nearly old enough to be legally considered an adult in the US, and its pre-rendered scenes are just not optimized for many modern machines. However, this mod was tested on a non-gaming laptop now a few years old, with the game running from an external hard disk drive, on a modern operating system, in full-screen mode, with several different visual mods installed. This meant that attempting to run the original Harbinger cutscene 10 times translated to the cutscene failing to play without major issue 10 times. After switching to the new version, any types of issues, major or minor, were encountered less than 1 out of 10 times. Hopefully, even a potato from your local grocery store can now successfully play the Harbinger Arrival cutscene, so long as it can generally play most TSL cutscenes successfully. Harbinger Enhancement_compressed.mp4 For reference when it comes to performance, this footage was recorded on an old laptop, with the game running on a modern operating system from a hard disk drive, with multiple other programs running in the background, and the following mods installed that can be seen in the video: - Ultimate Peragus Models Repair 1.2 (responsible for restoring proper lighting to the Harbinger, showing the administration level proper behind Atton, and other model fixes) - Harbinger Bridge Repairs (responsible for fixing several geometry errors, two visible during cutscene) - KotOR 2 Remastered (AI Upscaled) Cutscenes 1.0.0 by Naelavok (responsible for the upscaled pre-rendered scenes) - TSL Backdrop Improvements by Kexikus (responsible for the much-improved skybox seen from both the catwalk and the Harbinger bridge) - Improved Peragus Asteroid Fields 1.2 by Vasilii Zaytsev (responsible for the static 3d asteroids surrounding Peragus II) - Peragus Large Monitor Adjustment by Sith Holocron (responsible for that excellent HD computer monitor before Atton) - Kotor 2 Unlimited Worlds Texture Mod (responsible for the nicer-looking textures throughout the level, from the catwalk to the asteroids) - Ultimate Character Overhaul REDUX (responsible for the HD character textures) TLDR: This mod 1) stabilizes the Harbinger cutscene so that your game is much less likely to experience issues 2) places Kreia in her usual meditation spot in the morgue for her dialogue, and 3) fixes a number of minor issues with the cutscene. Installation: Download and run the installer, or else follow manual installation instructions. For Steam installations of TSLRCM, direct the installer to "Steam\steamapps\workshop\content\208580\485537937", and not the main game folder with the executable. 7z files can be extracted with Archive Utility on macOS, or with programs like PeaZip for windows and Linux. The installer is a .exe file, which can be run natively on Windows, or with programs like Wine for macOS and Linux. For an existing game, use a save file before going to the asteroid exterior. Save files made any later will not be affected. Uninstallation: Take 104per.mod out of the provided backup folder and place it in your modules folder at the location you installed to, and select replace when prompted. Take a_con_atton_end.ncs out of the provided backup folder and place it in your override folder at the location you installed to, and select replace when prompted. You can safely delete 104per.lyt and 104per.vis from your override folder. The files 104pera.mdl/.mdx/.wok come from Ultimate Peragus Models Repair, you can keep or delete these at your discretion. Additional Tips For Improving Game Performance: If you are having trouble running pre-rendered scenes in general, you can try the following: -- Go into your graphics settings, and under advanced options, disable frame buffering. If that does not work, try lowering or disabling all options. If the pre-rendered cutscene plays afterwards, you can up your graphics settings afterwards for normal gameplay. -- Try running the game in windowed mode, rather than fullscreen. Close your game and open "swkotor2.ini", found in the same folder as your main game executable (for a Steam game, that's "Steam\steamapps\common\Knights of the Old Republic II"). Under both "Display Options" and "Graphics Options", change "FullScreen=1" to "FullScreen=0". Restart your game. -- Uninstall/disable any non-essential mods that may relate to the cutscene or the area it takes place in. Peragus in particular also suffers from memory overflow if you play the game too long in one sitting. This can cause dialogue to start skipping, or for issues with game cutscenes. This can usually be avoided by: -- Quitting and restarting the game once in a while: doing it once before heading out to the asteroid surface, and again right before attempting to leave the Harbinger engine deck (the third and final level with the spooky lights) is usually enough to avoid problems. -- Avoiding skipping dialogue yourself, which can sometimes lead to memory overflow. If you do skip a lot of dialogue, quitting and restarting the game will fix the issue. Compatibility: Users should expect full compatibility with any other mods, so long as they make no modifications to the scripting or dialogue of the Harbinger's Arrival cutscene. For instance, if you are installing N-DReW's Mini Mod Collection for TSL, be sure not to add the included 104atton.dlg or 104kreia.dlg to your override, or remove it if you already have, as that would create a major incompatibility. This mod is for players using TSLRCM version 1.8.3 or higher. You may view this mod's changes.ini inside the "tslpatchdata" folder for a complete list of every altered module element. Feel free to check out "KotOR 2 Remastered (AI Upscaled) Cutscenes" by Naelavok for higher-resolution cutscenes, if you have not already. There are some other great mods out there that improve the visual quality of the cutscene. "Peragus Large Monitor Adjustment" by Sith Holocron, "KotOR 2 Unlimited World Texture Mod" by facemeltingsolo, "TSL Backdrop Improvements by Kexikus", and "Ultimate Peragus Models Repair" by yours truly are all compatible with this mod. "A Darker Peragus REDUX" by Malkior and "... A Darker Peragus" by Canderis are also compatible. Acknowledgments: Big thanks to Cortisol for the Holocron Toolset and Fred Tetra for KotOR Tool for making file extraction, module editing, and .mod file building easy, Fair Strides for the DLG Editor, JdNoa and Dashus for simple script decompiling with DeNCS, Blue for the KotOR Scripting Tool, Symmetric, Purifier, Ndix UR, and seedhartha for making importing to Blender simple using KotORBlender, and to Stoffe and Fair Strides for easy .mod extraction with ERFEdit, and for making inter-mod compatibility infinitely more feasible with TSLPatcher. Have a bug to report? Please click on "Get Support" and give a detailed description of the issue you are experiencing. This modification is not supported by Obsidian Entertainment, Lucasarts, Disney or any licensers/sponsors thereof. Use of this modification is at your own risk and neither the aforementioned companies nor the author may be held responsible for any damages caused to your computer via this modification's usage. -
1 point
Version 3.10.3
2,477 downloads
This add-on is a fork of KotorBlender, upgraded to support newer versions of Blender. KotorBlender is in turn based on NeverBlender, forked from version 1.23a. ## Features - Import & export MDL models, including walkmeshes - Import & export LYT files - Import & export PTH files ## Installation 1. Clone this repository or download the latest release of KotorBlender from Deadly Stream 2. If you have cloned the repository, create a ZIP archive containing the **io_scene_kotor** directory 3. From Edit → Preferences → Add-ons in Blender, install the add-on from the ZIP archive and enable it by ticking a box next to "Import-Export: KotorBlender" 4. Alternatively, if you want to contribute to KotorBlender, you may want to create a symbolic link to the local repository in the Blender add-ons directory, typically located at `C:/Users/{user}/AppData/Roaming/Blender Foundation/Blender/{version}/scripts/addons`. 1. `mklink /D io_scene_kotor {repo}/io_scene_kotor` ## Usage ### Data Preparation Extract models, textures, walkmeshes, LYT and PTH files into a working directory, using a tool of your choice, e.g. reone toolkit. Recommended directory structure: - *data* — extract all BIF archives here without subdirectories - *texturepacks* - *swpc_tex_tpa* — extract swpc_tex_tpa ERF archive here If you plan to edit textures, batch-convert TPC to TGA / TXI files using **reone toolkit**, although TPC textures are also supported by KotorBlender. ### Model Import and Export 1. Import via File → Import → KotOR Model (.mdl) 2. Select top-level MDL root object to be exported 3. Export via File → Export → KotOR Model (.mdl) ### Editing Animations To edit list of model animations and corresponding events, select MDL root object and navigate to Object → KotOR Animations. KotorBlender supports both object and armature-based edits. To create an armature from objects, navigate to KotOR Animations → Armature and press Rebuild Armature and Apply Object Keyframes. Before exporting a model, make sure to copy armature keyframes back to objects by pressing Unapply Object Keyframes. ### Lightmapping 1. Select objects for which you want lightmaps to be recreated, or unselect all objects to recreate all lightmaps 2. Press KotOR → Lightmaps → Bake (auto) UV mapping: 1. Select objects having the same lightmap texture and enter Edit mode 2. For every object, ensure that `UVMap_lm` UV layer is active 3. Select all faces and unwrap UVs via UV → Lightmap Pack, increase Margin to avoid face overlapping Fine-tuning: 1. Increase lightmap image size via UV Editing → Image → Resize 2. Tweak ambient color via Scene → World → Surface → Color 3. Manually toggle rendering of objects in Outliner and press KotOR → Lightmaps → Bake (manual) 4. In Scene → Render, set Device to GPU Compute to improve performance, set Render Engine to Cycles if not already 5. In Scene → Render → Sampling → Render increase Max Samples to improve quality ### Minimap Rendering 1. Press KotOR → Minimap → Render (auto) 2. Open "Render Result" image in Image Editor and save it as "lbl_map{modulename}.tga" 3. Open "MinimapCoords" text in Text Editor and copy-paste generated properties into module .ARE file using any GFF editor Fine-tuning: 1. Tweak background color via Scene → World → Surface → Color 2. Manually toggle rendering of objects in Outliner and press KotOR → Minimap → Render (manual) ### Connecting Rooms 1. Select a room walkmesh 2. Enter Edit mode and select two vertices adjacent to another room 3. Determine 0-based index of the other room into the LYT file 4. Enter Vertex Paint mode and set brush color to (0.0, G, 0.0), where G = (200 + room index) / 255 5. Ensure that brush blending mode is set to Mix, and brush strength is set to 1.0 6. Paint over the selected vertices ### Editing Paths 1. Extract PTH file from the module's RIM file, e.g. "modules/danm13_s.rim" (Kotor Tool, reone toolkit, etc.) 2. Import PTH into Blender via File → Import → KotOR Path (.pth) 3. Create/move path points, or modify path connections via Object Properties 4. Export PTH via File → Export → KotOR Path (.pth) ## Compatibility Known to work with Blender versions ranging from 3.3 to 4.0. ## License GPL 3.0 or later -
1 pointHi everyone! I’m currently working on completing my MBA at Mississippi State and one of our final projects is consulting a client to solve a business problem. My team is tasked with consulting for MAGCOR Industries and we have prepared a short 5-10 minute survey to gather marketing data to help with the project. We would appreciate any and all feedback. Thank you! https://msstate.co1.qualtrics.com/jfe/form/SV_7PSibA2t8auee9g
-
1 point
-
1 pointScript Condidionals Hello There, When I was making my Tatooine Job Office (http://www.lucasforums.com/showthread.php?t=206577) I wanted to find how to only make certain conversation options available after certain conditions had been met. Now I couldn't find a dedicated tutorial anywhere so I had to ask. So I thought I'd make it easier by writing this tutorial. This is my first tutorial so go easy on me Things you will need: KOTOR Tool Things you should read: http://www.lucasforums.com/showthread.php?t=143412 http://www.lucasforums.com/showthread.php?t=143681 http://www.lucasforums.com/showthread.php?t=143390 Right Script Conditionals. What can they do? Script conditionals can be used when you want something (usually a dialog option) to only be displayed once a certain condition has been met. Some of the common conditions used are: Global Variables Local Variables Item in PC Inventory Certain Classes There are many other conditions but as long as the condition returns either TRUE or FALSE then it will work. Lets start Scripting! First of all if you have only coded a little bit in KOTOR before then this will look completely different. int StartingConditional() { int iResult; iResult = ((GetGlobalBoolean( "your_global_bool" ) == TRUE) ); return iResult; } Right lets break this down. int StartingConditional() This starting line is different than most scripts in KOTOR for one reason. In most scripts you do not require an outcome as they usually make something happen. We however want an outcome so the dialogue (or whatever) knows what to do / display. Most scripts start with: void main() Void is used when no output is required and means nothing or to get rid of. Int is a variable type meaning that it has to be filled by something. The StartingConditional() part tells the game that it is to be used as a Starting Conditional Script. The next bit int iResult; Here you are declaring the variable "iResult". You will use this variable to store the outcome and tell the game what to do. If you've never used variables before get used to it because they are VITAL to scripting. Then next bit iResult = ((GetGlobalBoolean( "your_global_bool" ) == TRUE) ); This is the most important part of your script. It determines what must happen for the conversation option to become available and then puts it into the "iResult" variable. In this example it gets whether a global bool is TRUE and then outputs TRUE into "iResult"but there are other options such as object oW1 = GetObjectByTag("black_market_pad"); iResult = GetIsObjectValid(oW1); This checks for the existance of "black_market_pad" in the PC's inventory and puts TRUE in the "iResult" variable. The last bit return iResult; This simply tells the script YES or NO / TRUE or FALSE. If the script sees TRUE it will display the dialog option. Then you must simply compile the script and put the resulting file in the same place as your dialog. (For information on compiling scripts see one of the top links) To put it into the acttual dialog find the line you want to hide until the condition has been met and in the box that says "Script that determines availablilty" put the name of your script file (minus the extension) Thats it. Hope this helped. If you have any questions at all I will do my best to answer them. Thanks TB12