Leaderboard
Popular Content
Showing content with the highest reputation on 05/13/2023 in all areas
-
1 point
Version 3.1.0
1,667 downloads
This modding toolset is a work in progress and I carry no responsibility to any damage done to your game files or lost work that may occur. Some antiviruses will flag a false positive and prevent you from opening the application. If this happens you will need to configure your antivirus to allow the program to run. Holocron Toolset is a collection of modding tools packaged in a single application aimed at streamlining modding development for KotOR/TSL, drawing inspiration from Kotor Tool and the NWN Aurora Toolset. There are editors available for nearly every file type used by the game. Also included with it is a 3D module editor and a "Map Builder" which the user can use to create new maps by rearranging existing models already used in the game. Discord for suggestions + bug reports: https://discord.com/invite/3ME278a9tQ If you are running Windows 7 or 8 and get a missing DLL error when opening the program you will need to download the Visual C++ Redist from Microsoft. Toolset source File parsing source -
1 point
Version 3.10.3
2,474 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 pointWhy yes, I did update a 10 year old mod! Thanks for noticing!
-
1 point
Version v1.0.3
2,200 downloads
MDLedit is a (de)compiler for KOTOR and KOTOR2 model files. Which version should I download? There are two packages on the download page. They differ in whether the program uses Visual Styles or not. The difference is purely visual, they are completely equivalent in terms of functionality. The version in the mdledit_v0.0.0xp.zip package will work on Windows XP or newer as well as on MacOS through Wine, but it will look like crap. The version in the mdledit_v0.0.0.zip package will look better, but will only work on Windows Vista and up. How do I set it up? Open the .zip archive, extract the .exe and run it. If you want MDLedit to keep track of your option between sessions, create a blank mdledit.ini file in the same folder as your .exe. How do I use it? The program comes with a help documentation window accessible from the About menu, read that to learn how to use it. If something is not mentioned there please let me know in the relevant thread (link to be added) and I will explain the functionality and add the explanation to the help window for the next version. MDLedit was designed to be used with KOTORmax and the new version of KotORBlender by ndix UR. Using the ascii model files that it produces with NWmax will cause data to be ignored in the best case and a crash in the worst. The program crashed/froze/reported a weird error! Describe your issue in the relevant thread and I will look into it. Attaching a .zip archive with the files that MDLedit was processing when the problem appeared is also very welcome. Thanks A big thank you goes out to ndix UR, without whom MDLedit would have maybe half the functionality it has now. I would also like to thank the testers, who also made a lot of great suggestions that made MDLedit that much better: – DarthParametric – JCarter426 – Quanon – VarsityPuppet – FairStrides The program was built on the knowledge about the MDL format, which is the result of the work of many modders, including CChargin, Magnusll, JdNoa, ndix UR, DarthSapiens, VarsityPuppet, FairStrides, and others! Thank you for your efforts! Lastly I'd like to thank the KOTOR modding community, which makes taking the time to make such a tool worth it. -
1 point
-
1 pointSith Holocron asked me to repost my old 2013 tutorial on this subject from LucasForums here, which you may have seen before, either in its original form or in the helpful video forms made by Xuul (if you have difficulty understanding any of the steps here, I recommend seeking those videos out). This method was originally discovered and posted for KotOR II, but works for KotOR I as well. Here is the guide, with some minor changes: --- The ability to run the KotOR games in custom resolutions has existed for many years now. Personally, I have patched KotOR I and II to run in a 1920x1080 widescreen resolution (and KotOR II now supports higher resolutions by default after the Aspyr patch), and many other people have done the same, with various resolutions. However, despite these patches, no matter what resolution the game is patched to run in, the games' .bik movies do not run in the patched resolution. They merely upscale to fit the width of the screen. For KotOR II, which was the original subject of this guide, the vanilla non-HQ movies play in an awful 640x272 and upscale from there, maintaining the 640x272 aspect ratio of ~2.353:1 until they are the width of the screen, with ugly black bars on the top and bottom of the movies. In late 2012, in this LucasForums thread, I pieced together the method to getting KotOR II to run the .bik movies in different resolutions -- in my case, 1920x1080. This thread will explain that method, applied to both games, and should allow anyone to force the games to run the movies in the same resolution that their game is patched to. WARNING: This modification requires the hex editing of KotOR I/II's executable. Mistakes could cause it to stop working, requiring you to redownload the file if you do not know how to fix the problem yourself. With Steam, this is an easy thing to do; on a physical copy of the game, it would require a full reinstallation. Remember to back up any and all files that you will be altering in case something goes wrong. Things you'll need: The KotOR I/II no-CD patch -- If you've already patched your game to run in a custom resolution, then you've already gotten the no-CD patch, because the normal executable isn't editable. I can't link to the no-CD patches since they are technically illegal, but they are easily found via Google. This should not be required for the GOG versions of the games. In the case of KotOR II, you should also grab the KotOR II HQ movies patch -- this is included by default with the Steam and GOG versions, so most people shouldn't need to worry about this. If you are playing with a physical copy, then you'll need to find a mirror of the patch online somewhere. There are 6 parts in total. RAD Video Tools -- this program is used to output the HQ movies to your desired resolution. **** The latest update of RAD Video Tools no longer works with kotor movies. Users will need to download version RADTools_1200e located here HxD Hex Editor -- You will need a hex editor to edit the games' executables. Any will work, but HxD is the one I used, and it's free. Download here. Now, the instructions. ----------------------------------------------------------------------------------------------------- Step 1: First, make sure you've backed up everything that you'll be editing. I suggest creating a folder entitled "Backup" inside your KotOR I/II directory, in which you can put the game's executable and any other important files (such as the original movie files), although the executable is really the only one that is at risk of being screwed up by a mistake. If you have the Steam version, you can just use the "verify integrity of game cache" function to redownload the original version(s) of any broken file(s). Step 2: Create a folder entitled something like "Outputted Movies" and put it somewhere like your desktop. It doesn't really matter where; the desktop is probably the best place. You'll be deleting it once you're finished, as it will no longer be needed. Step 3: KotOR II users should install the official KotOR II HQ movies patch. This will overwrite many of the files in your \Movies directory with higher quality ones. Remember that this is not necessary on the Steam version. Step 4: Get the no-CD patch for your game (I can't link here as stated above, so use Google) and, if necessary, patch your game to run in whatever resolution you want. Instructions on how to do that can be found online and will not be given here so as to reduce the size of this post. I'm sure most people reading this have already done this step eons ago, anyways. Step 5: If you haven't already, download and install the RAD Video Tools linked above. Step 6a: Now, the fun stuff begins. You'll need to use RAD Video Tools to convert all of KotOR I/II's .bik movies to your desired resolution. Depending on the power of your computer, this can take a significant amount of time. It might be best to just do this step overnight, as the processing takes a while and is very resource-intensive, slowing your PC while in progress. If you are on an old/weak PC, this process could take too long to be worthwhile for you. I can't estimate how long it will take, as it will vary wildly based on the power of your PC. To convert the files, open RAD Video Tools and navigate to your KotOR I/II installation directory, and then open the Movies subfolder. Select all of the .bik movies. Step 6b: Now that you've selected all of the files, click "Bink it!" in the lower left corner of the RAD Video Tools window. A new window should open wherein you can select the output settings. Under "Browse," select the desktop folder we created earlier called "Outputted Movies." All of the converted movies will now be outputted there. Under "Input video settings," enter your desired resolutions. I, for example, put 1920 in the width boxes and 1080 in the height boxes. KotOR I users should make sure that the "Compress audio" option is checked and that lossiness is set to 0, otherwise the files will be rendered without sound (thanks milestails for noting this); KotOR II users can uncheck compress audio. Click "Bink" on the right-hand side. Step 7: Now you play the waiting game. Wait for the movies to be converted. Step 8: Once the movies have been outputted to your desktop folder (or wherever else), copy and paste them to your KotOR I/II's Movies folder (e.g. C:\Program Files (x86)\Steam\steamapps\common\Knights of the Old Republic II\Movies). Select yes when asked to overwrite. You can also backup the originals beforehand, if you want. Once all the files are in place, you can delete the "Outputted Movies" folder from your desktop; it has served its purpose. Step 9: Install HxD (or any hex editor, really) and open the game's executable (swkotor.exe or swkotor2.exe), located in your KotOR I/II installation directory. Here comes the only complex part of these instructions. You will need to find the following hex values (in HxD, make sure to change the search datatype from Text-string to Hex-values) and edit them to match your desired resolution. Change the bolded resolution pairs to your desired widescreen resolution. Remember to flip the order of the hexadecimal values. For example, 1920 is 0x780 in hexadecimal. I would flip the order (ignoring the x) and enter 1920 as "8007." 1080 is 0x438, and thus, it would be entered as "3804." For KotOR II: TSL, the hex values you must edit are: For KotOR I, the hex values you must edit are (thanks to Kainzorus Prime for finding these hex values online): Note: If the game minimizes during cinematics, this may be fixed by setting the game's executable to run in compatibility mode for Windows XP with Service Pack 3. If you are having trouble finding the coordinates, it may be because the UniWS patcher already edited the hex coordinates for you. You can verify this by searching for what you plan on changing the coordinates to (instead of the original pre-patch values); if you find a match, that means the editing has already been done by the patcher. Step 10: Most people have probably already done this, but if you haven't, it's vital: open the file swkotor.ini/swkotor2.ini with Notepad (or any text editor) in your KotOR I/II directory and change the width and height under [Graphics Options] (and [Display Options] for KotOR II) to whatever your custom resolution is. ----------------------------------------------------------------------------------------------------- That's it! Assuming everything worked correctly, your KotOR I/II movies should now play full-screen, with no ugly black bars on the top and bottom. Enjoy the fixed movies, and PM me if you have any questions or anything that could be added to this guide. I will update this thread in the future to correct any mistakes or to add any additional information.