Leaderboard
Popular Content
Showing content with the highest reputation since 07/05/2020 in all areas
-
11 pointsJust out of the oven, freshly baked.
-
4 points
Version 1.0.0
11 downloads
This is a simple edit of the camera model for the workbench upgrade screen that alters some of the camera angles/positions to zoom in a bit closer to lightsabers, so you can get a better look at the models when running the game at higher resolutions. Obsidian already adjusted the UI to provide bigger previews of other upgradeable objects, so only the sabers are adjusted for this version. Since the model preview window is a little narrower than in widescreen modded K1, all three hilt types have been rotated 45° to maximise the available space. Mostly intended for those using modded weapons. A version for K1 is available here. Installation Instructions Simply drop the MDL/MDX in your Override folder. Known Issues Only tested at 1080p. Results may vary at other resolutions/aspect ratios. Modded weapons that are excessively large will likely go off-screen, but they probably do that already. Acknowledgements Thanks to @bead-v for MDLEdit and KOTORMax. -
4 pointsI just checked footstepsounds.2da, and 0 is listed as "Soft", whereas 2 is listed as "Droid". So, hopefully this confirms what Jc2 is saying; just change the "footstepsound" column of the N_mandalorian section from a "2" to "0" in Appearance.2da with the Kotortool, and that should fix it. (Unsure about the "Soundapptype", as that's a bit outside of my personal knowledge base) One thing I'd like to note is that the Kotortool has an idiosyncrasy where it won't save your changes to a column unless you click onto another one before saving. It's a bit complicated, but I'd be willing to help if need be.
-
3 pointsK2 Upscaled Maps by tunalex adds a nice polish to the game, especially if you have other graphic mods. Seems worth checking out, I certainly will next playthrough.
-
3 pointsI'm guessing its an appearance.2da edit, as both N_mandalorian02 and 03 both have footsteptype as 2 and soundapptype as 6 which is identical to the HK-47 foosteptype as 2 and soundapptype as 6. Perhaps change those two numbers to either what the PC normally has which if you check the P_mal_XXX anything you'll notice its listed as 0 and 0, or change it to any human NPC numbers. Since I haven't made this edit myself ever, I'm not 100% sure about it.
-
3 pointsObi-Wan's hilt from ANH. The true prototype hardware saber, cobbled together from random assorted crap. The balance pipe from a Rolls Royce jet engine for the emitter, a WWI rifle grenade for the upper body, a Graflex flashgun clamp with Texas Instruments calculator bubbles and a booster from a Browning machine gun for the middle/lower, plus an Armitage Shanks sink tap/faucet knob for the pommel. It's truly remarkable how well the individual pieces fit together given their diverse origins. K1 - https://www.darthparametric.com/files/kotor/k1/[K1]_Obi-Wan's_ANH_Lightsaber.7z TSL - https://www.darthparametric.com/files/kotor/tsl/[TSL]_Obi-Wan's_ANH_Lightsaber.7z
-
3 points@La Ingobernable It worked! Thanks! The fruits of my labor
-
3 points@jc2 OH JESUS OH GOD @La Ingobernable I'm afraid I'm stuck on how to save my changes to appearance.2da. I can save it as a new appearance.2da file, but I can't seem to overwrite the existing one.
-
2 pointsHello! I'd like to ask your opinion about this item's restriction. Currently it's restricted to Light Side but not to Jedi. The description speaks specifically of being an item created to celebrate Guun Han Saresh's acceptance into the Order. Do you think it would make more sense if only light sided Jedi could wear it? Thanks.
-
2 pointsI think that's a great idea for consistency's sake. I mean, it does make sense after all. Perhaps adding Jedi Defense to Feat Required field on the item's template/UTI would be the best approach for that.
-
2 points
Version 1.0.0
15 downloads
This is a simple edit of the camera model for the workbench upgrade screen that alters some of the camera angles/positions to zoom in a bit closer to certain weapon types, most notably lightsabers, so you can get a better look at the models when running the game at higher resolutions. Mostly intended for those using modded weapons. Installation Instructions Simply drop the MDL/MDX in your Override folder. Known Issues Requires ndix UR's KOTOR High Resolution Menus mod to work as intended. Only tested at 1080p. Results may vary at other resolutions/aspect ratios. Modded weapons that are excessively large will likely go off-screen, but they probably do that already. Acknowledgements Thanks to @bead-v for MDLEdit and KOTORMax. Thanks to @ndix UR for the High Res Menus mod. -
2 pointsThat part is relatively straightforward to do in principle at least, since Max can make use of lightmaps via a DirectX shader: The real problem would be the impracticality of setting it up for every single level, since that would involve hundreds of materials. The only way it would work is if bead-v (or someone else) could alter KMax to add a mode where it automatically loads materials up with that shader rather than just using the default material settings. But overall, while an interesting thought exercise, as Kex alludes to it isn't a particularly practical endeavour.
-
2 pointsHonestly, I think it would be much easier to load the modules in Max and then render from there with an orthographic camera. Granted, you don't get the exact ingame lighting so that would have to be set up to look good but you get around the facing issue where not everything is rendered ingame depending on where your character looks. And stitching perspective renders taken from different places is a real pain as nothing matches up. The biggest issue with either of these methods is something else though. The modules in both games were stripped of all geometry that cannot be seen during normal gameplay or in other words: They're not meant to be seen from above and you'd get gaps and missing roofs and whatnot everywhere. I assume that the original maps were rendered before the unnecessary geometry was cut or something like that, but for a good looking map that would have to be restored at least in parts. Either way, I like the idea even though I don't know how feasible it actually is.
-
2 pointsWell as I was searching through the skinning tutorials and there seemed to be none on how to make a good looking texture with gimp, there was a lot on photoshop but not gimp so I decided to share my knowledge of it with the community. __________ Basics Basics part 1: Selecting an area To make good skins you would need to select a precise area to make it look nice. To do this you click on the drop down menu at the bottom. Usually this has 100% in it as a default. Set this to anything you wish. you should be able to distinctly see the area you wish to select now. Now to select the area you click on this icon and then click on each "bend point" on the area you want. A bend point is wherever the texture bends away from a straight line. Basics part 2: Re-coloring To change the color of a Jedi Robe some beginners use the paintbrush tool. In some cases this might work, but not if you want to make the robes look natural. For a natural look you first select the area you want to change by using the free select tool, if you want to modify the whole texture's color at once you go into "Edit" and then "Select all". Next you go into the "Colors" tab at the top of the page and click on desaturate. Note only do the desaturate step if you want to compleatly change the color, if you don't and you just want a hint of the color in the already existing texture you skip that step. To change the color you go into the "colors" tab again and click on "Color Balance". A menu like this should open. In that menu you drag the bars around till you get the shade you want. This part should be pretty self explanatory as the bars are clearly labeled. If green was your desire, your outcome should be something like this: If you want a more direct color you go into the "color" tab again and go to colorize. This can give you a quick and effective color but might not retain as much detail. Basics part 3- Repair When you select an area and re-color it sometimes you see a tiny bit you wanted that color. To fix this you use the blur function adjust the size to around .15 then zoom in to 800% and take the re-colored pixal section and hold down the blur and "push them" on top of the other area. Advanced This section is for people who know the basic functions of gimp and successfully make a descent re-skin Advanced Part 1- Overlay Overlay is basically changing the way the new layers interact with each other when you paste in another texture. In the "layers, channels, paths" toolbar: There is a dropdown menu here: in there there will be a bunch of options you select and they make the picture somewhat transparent and molds it to the texture. Click on them all till you get the look you want. Note you must have pasted a new layer into it and NOT merged it down. Advanced Part 2- Enhance filter Up in the "filters" toolbar menu there is a section called enhance go into it and select sharpen. Drag the bar in the menu till you get a good look, it really adds to the overall appearance. I will add some more tips when I find them but here they are for now. Enjoy~
-
2 pointsHello everyone! Over the last little bit we've been requesting permission from all of the authors whose content is in the K1CP to host binaries on GitHub. Well, we've finally got permission from the last few people, so be on the lookout soon for releases to be downloadable from https://github.com/KOTORCommunityPatches/K1_Community_Patch We'll continue to also keep the release here on DeadlyStream up-to-date, but now you'll be able to get alpha and beta builds from GitHub to help us test, or to get your hands on the latest fixes. Enjoy!
-
1 pointI like the idea, for what it's worth. I'd say the new requirement should be implemented to every instance where it makes sense. So besides the circlet, there's Tulak's mask, as you said, but also Ragnos' gauntlets. Qel-Droma's robes you can't equip without the Jedi Defense feat anyway. It doesn't make sense to have a special restriction for the robes but not for any of these items. They should've either removed the Jedi restriction thing or applied it to everything pertinent. To be honest, Sith artifacts requiring a Force user sounds way more fitting than restricting non Force sensitives from wearing plain robes. EDIT: Ajunta's blade is another possibility, though more crippling gameplay wise.
-
1 point
-
1 pointHello, ebmar! That is exactly what I had done locally but I wasn't quite sure. Especially considering that the polar opposite item (Tulak Hord's Mask, which also looks identical in the original game) is restricted to Dark Side but not Jedi. I hope others will chime in and give us their opinion as well. Cheers!
-
1 point
@Malkior: Remember when we thought 2019 was crazy? How young and foolish we were. -
1 pointThat's exactly what I was suggesting since it really is very simple to load the area into Max. The problem is mainly the missing geometry when viewing the area from above and the issue of getting the lightmaps into Max. Doing this manually for each mesh would take forever.
-
1 pointInteresting idea and correct me if I am wrong, but couldn't the entire map be rendered at once? Just import to Blender with KotorMax and use the .lyt file to arrange the level, then use top-down rendering techniques to make a map from it, I am almost certain I have seen a technique / tutorial somewhere for rendering a whole level to a minimap at once, I shall have to track it down. At some point I need to re-render the K1 maps for K2 anyway so I might look into this as well ( won't be any time soon though ) as for setting up the lightmaps, I do not even know how to apply the lightmaps myself, using GMax and KOTORMax it's relatively simple to get the whole level loaded in.
-
1 pointI just tested this on an unmodded playthrough. The holocron spawns despite the install error. The corpse with the holocon can be found
-
1 pointYou can do it directly in MDLEdit, or decompile it to an ASCII, edit it in a text editor to change the name, then recompile. Alternatively, you can hex edit the model and do an ASCII string find and replace, but you'll want to keep the same number of characters for the filename going that route.
-
1 pointYou can still get the original version (blue) from my site for both K1 and TSL.
-
1 pointI'm using a mod which replaced the Mandalorian armours with their disguise version, but the Red and Yellow version have a metal clanking sound for their footsteps like it was HK-47 or some other droid. I'm trying to see if I can change the footstep sounds for these 2 armours with Kotor Tools but I don't know how to do so. Does anyone have a clue? Thanks
-
1 pointThanks guys, I'll give it a go and edit my reply with the results :3 Edit: Thank you both! I messed around with it and found that 1 for the footsteps and 0 for the soundapptype is what I needed it to be
-
1 pointI would love to be able to use the character model of the galaxy's most fearsome warrior, Deadeye Duncan, for the player's character. Unfortunately I have zero modding experience. I decided to dig around in the game's files to see if I could find Deadeye Duncan's character model by name, but quickly realized I have no idea what I'm doing. I suspect that, for those who know what they're doing, a character model swap like this is super simple, so I'd love to know how to do it. Thanks!
-
1 pointIf you pull a module's GIT from a save file and check the doors in the level, I don't think the Interruptable flag is stored at all, regardless of whether it is set to true or false.
-
1 pointOk, that's quite disturbing... and hilarious xD
-
1 point
Version 1.0.1
557 downloads
================================ KNIGHTS OF THE REPUBLIC II Mod ================================ Title: K1 Heads Port Version: 1.0.1 Author: Ferc Kast Contact: PM me on DeadlyStream *********** DESCRIPTION *********** This mod ports the original player heads from KOTOR I for use as playable heads in KOTOR II. To use reskins for these heads, follow these steps: 1) Move the relevant head and / or portrait tpcs out of your override folder. 2) After extracting the textures from the reskin mod, prefix the head texture filenames with "K1_" or "k1_" (without the quotes). 3) Copy the textures into your override folder. ************ INSTALLATION ************ Unzip the file. Run TSLPatcher, and point the installer to your KOTOR II installation folder. If you are using the Steam copy of TSLRCM, point it to the folder where it is installed. ************** UNINSTALLATION ************** Copy the 2das from the backup folder into the Override folder. Remove the following files from the Override folder: - k1_pfha01.mdl - k1_pfha01.mdx - k1_pfha01.tpc - k1_pfha01d.tpc - k1_pfha01d1.tpc - k1_pfha01d2.tpc - k1_pfha01d3.tpc - k1_pfha02.mdl - k1_pfha02.mdx - k1_pfha02.tpc - k1_pfha02d.tpc - k1_pfha02d1.tpc - k1_pfha02d2.tpc - k1_pfha02d3.tpc - k1_pfha03.mdl - k1_pfha03.mdx - k1_pfha03.tpc - k1_pfha03d.tpc - k1_pfha03d1.tpc - k1_pfha03d2.tpc - k1_pfha03d3.tpc - k1_pfha04.mdl - k1_pfha04.mdx - k1_pfha04.tpc - k1_pfha04d.tpc - k1_pfha04d1.tpc - k1_pfha04d2.tpc - k1_pfha04d3.tpc - k1_pfha05.mdl - k1_pfha05.mdx - k1_pfha05.tpc - k1_pfha05d.tpc - k1_pfha05d1.tpc - k1_pfha05d2.tpc - k1_pfha05d3.tpc - k1_pfhb01.mdl - k1_pfhb01.mdx - k1_pfhb01.tpc - k1_pfhb01d.tpc - k1_pfhb01d1.tpc - k1_pfhb01d2.tpc - k1_pfhb01d3.tpc - k1_pfhb02.mdl - k1_pfhb02.mdx - k1_pfhb02.tpc - k1_pfhb02d.tpc - k1_pfhb02d1.tpc - k1_pfhb02d2.tpc - k1_pfhb02d3.tpc - k1_pfhb03.mdl - k1_pfhb03.mdx - k1_pfhb03.tpc - k1_pfhb03d.tpc - k1_pfhb03d1.tpc - k1_pfhb03d2.tpc - k1_pfhb03d3.tpc - k1_pfhb04.mdl - k1_pfhb04.mdx - k1_pfhb04.tpc - k1_pfhb04d.tpc - k1_pfhb04d1.tpc - k1_pfhb04d2.tpc - k1_pfhb04d3.tpc - k1_pfhb05.mdl - k1_pfhb05.mdx - k1_pfhb05.tpc - k1_pfhb05d.tpc - k1_pfhb05d1.tpc - k1_pfhb05d2.tpc - k1_pfhb05d3.tpc - k1_pfhc01.mdl - k1_pfhc01.mdx - k1_pfhc01.tpc - k1_pfhc01d.tpc - k1_pfhc01d1.tpc - k1_pfhc01d2.tpc - k1_pfhc01d3.tpc - k1_pfhc02.mdl - k1_pfhc02.mdx - k1_pfhc02.tpc - k1_pfhc02d.tpc - k1_pfhc02d1.tpc - k1_pfhc02d2.tpc - k1_pfhc02d3.tpc - k1_pfhc03.mdl - k1_pfhc03.mdx - k1_pfhc03.tpc - k1_pfhc03d.tpc - k1_pfhc03d1.tpc - k1_pfhc03d2.tpc - k1_pfhc03d3.tpc - k1_pfhc04.mdl - k1_pfhc04.mdx - k1_pfhc04.tpc - k1_pfhc04d.tpc - k1_pfhc04d1.tpc - k1_pfhc04d2.tpc - k1_pfhc04d3.tpc - k1_pfhc05.mdl - k1_pfhc05.mdx - k1_pfhc05.tpc - k1_pfhc05d.tpc - k1_pfhc05d1.tpc - k1_pfhc05d2.tpc - k1_pfhc05d3.tpc - k1_pmha01.mdl - k1_pmha01.mdx - k1_pmha01.tpc - k1_pmha01d.tpc - k1_pmha01d1.tpc - k1_pmha01d2.tpc - k1_pmha01d3.tpc - k1_pmha02.mdl - k1_pmha02.mdx - k1_pmha02.tpc - k1_pmha02d.tpc - k1_pmha02d1.tpc - k1_pmha02d2.tpc - k1_pmha02d3.tpc - k1_pmha03.mdl - k1_pmha03.mdx - k1_pmha03.tpc - k1_pmha03d.tpc - k1_pmha03d1.tpc - k1_pmha03d2.tpc - k1_pmha03d3.tpc - k1_pmha04.mdl - k1_pmha04.mdx - k1_pmha04.tpc - k1_pmha04d.tpc - k1_pmha04d1.tpc - k1_pmha04d2.tpc - k1_pmha04d3.tpc - k1_pmha05.mdl - k1_pmha05.mdx - k1_pmha05.tpc - k1_pmha05d.tpc - k1_pmha05d1.tpc - k1_pmha05d2.tpc - k1_pmha05d3.tpc - k1_pmhb01.mdl - k1_pmhb01.mdx - k1_pmhb01.tpc - k1_pmhb01d.tpc - k1_pmhb01d1.tpc - k1_pmhb01d2.tpc - k1_pmhb01d3.tpc - k1_pmhb02.mdl - k1_pmhb02.mdx - k1_pmhb02.tpc - k1_pmhb02d.tpc - k1_pmhb02d1.tpc - k1_pmhb02d2.tpc - k1_pmhb02d3.tpc - k1_pmhb03.mdl - k1_pmhb03.mdx - k1_pmhb03.tpc - k1_pmhb03d.tpc - k1_pmhb03d1.tpc - k1_pmhb03d2.tpc - k1_pmhb03d3.tpc - k1_pmhb04.mdl - k1_pmhb04.mdx - k1_pmhb04.tpc - k1_pmhb04d.tpc - k1_pmhb04d1.tpc - k1_pmhb04d2.tpc - k1_pmhb04d3.tpc - k1_pmhb05.mdl - k1_pmhb05.mdx - k1_pmhb05.tpc - k1_pmhb05d.tpc - k1_pmhb05d1.tpc - k1_pmhb05d2.tpc - k1_pmhb05d3.tpc - k1_pmhc01.mdl - k1_pmhc01.mdx - k1_pmhc01.tpc - k1_pmhc01d.tpc - k1_pmhc01d1.tpc - k1_pmhc01d2.tpc - k1_pmhc01d3.tpc - k1_pmhc02.mdl - k1_pmhc02.mdx - k1_pmhc02.tpc - k1_pmhc02d.tpc - k1_pmhc02d1.tpc - k1_pmhc02d2.tpc - k1_pmhc02d3.tpc - k1_pmhc03.mdl - k1_pmhc03.mdx - k1_pmhc03.tpc - k1_pmhc03d.tpc - k1_pmhc03d1.tpc - k1_pmhc03d2.tpc - k1_pmhc03d3.tpc - k1_pmhc04.mdl - k1_pmhc04.mdx - k1_pmhc04.tpc - k1_pmhc04d.tpc - k1_pmhc04d1.tpc - k1_pmhc04d2.tpc - k1_pmhc04d3.tpc - k1_pmhc05.mdl - k1_pmhc05.mdx - k1_pmhc05.tpc - k1_pmhc05d.tpc - k1_pmhc05d1.tpc - k1_pmhc05d2.tpc - k1_pmhc05d3.tpc - pmha05hair.tpc - po_pfha1.tpc - po_pfha1d.tpc - po_pfha1d1.tpc - po_pfha1d2.tpc - po_pfha1d3.tpc - po_pfha2.tpc - po_pfha2d.tpc - po_pfha2d1.tpc - po_pfha2d2.tpc - po_pfha2d3.tpc - po_pfha3.tpc - po_pfha3d.tpc - po_pfha3d1.tpc - po_pfha3d2.tpc - po_pfha3d3.tpc - po_pfha4.tpc - po_pfha4d.tpc - po_pfha4d1.tpc - po_pfha4d2.tpc - po_pfha4d3.tpc - po_pfha5.tpc - po_pfha5d.tpc - po_pfha5d1.tpc - po_pfha5d2.tpc - po_pfha5d3.tpc - po_pfhb1.tpc - po_pfhb1d.tpc - po_pfhb1d1.tpc - po_pfhb1d2.tpc - po_pfhb1d3.tpc - po_pfhb2.tpc - po_pfhb2d.tpc - po_pfhb2d1.tpc - po_pfhb2d2.tpc - po_pfhb2d3.tpc - po_pfhb3.tpc - po_pfhb3d.tpc - po_pfhb3d1.tpc - po_pfhb3d2.tpc - po_pfhb3d3.tpc - po_pfhb4.tpc - po_pfhb4d.tpc - po_pfhb4d1.tpc - po_pfhb4d2.tpc - po_pfhb4d3.tpc - po_pfhb5.tpc - po_pfhb5d.tpc - po_pfhb5d1.tpc - po_pfhb5d2.tpc - po_pfhb5d3.tpc - po_pfhc1.tpc - po_pfhc1d.tpc - po_pfhc1d1.tpc - po_pfhc1d2.tpc - po_pfhc1d3.tpc - po_pfhc2.tpc - po_pfhc2d.tpc - po_pfhc2d1.tpc - po_pfhc2d2.tpc - po_pfhc2d3.tpc - po_pfhc3.tpc - po_pfhc3d.tpc - po_pfhc3d1.tpc - po_pfhc3d2.tpc - po_pfhc3d3.tpc - po_pfhc4.tpc - po_pfhc4d.tpc - po_pfhc4d1.tpc - po_pfhc4d2.tpc - po_pfhc4d3.tpc - po_pfhc5.tpc - po_pfhc5d.tpc - po_pfhc5d1.tpc - po_pfhc5d2.tpc - po_pfhc5d3.tpc - po_pmha1.tpc - po_pmha1d.tpc - po_pmha1d1.tpc - po_pmha1d2.tpc - po_pmha1d3.tpc - po_pmha2.tpc - po_pmha2d.tpc - po_pmha2d1.tpc - po_pmha2d2.tpc - po_pmha2d3.tpc - po_pmha3.tpc - po_pmha3d.tpc - po_pmha3d1.tpc - po_pmha3d2.tpc - po_pmha3d3.tpc - po_pmha4.tpc - po_pmha4d.tpc - po_pmha4d1.tpc - po_pmha4d2.tpc - po_pmha4d3.tpc - po_pmha5.tpc - po_pmha5d.tpc - po_pmha5d1.tpc - po_pmha5d2.tpc - po_pmha5d3.tpc - po_pmhb1.tpc - po_pmhb1d.tpc - po_pmhb1d1.tpc - po_pmhb1d2.tpc - po_pmhb1d3.tpc - po_pmhb2.tpc - po_pmhb2d.tpc - po_pmhb2d1.tpc - po_pmhb2d2.tpc - po_pmhb2d3.tpc - po_pmhb3.tpc - po_pmhb3d.tpc - po_pmhb3d1.tpc - po_pmhb3d2.tpc - po_pmhb3d3.tpc - po_pmhb4.tpc - po_pmhb4d.tpc - po_pmhb4d1.tpc - po_pmhb4d2.tpc - po_pmhb4d3.tpc - po_pmhb5.tpc - po_pmhb5d.tpc - po_pmhb5d1.tpc - po_pmhb5d2.tpc - po_pmhb5d3.tpc - po_pmhc1.tpc - po_pmhc1d.tpc - po_pmhc1d1.tpc - po_pmhc1d2.tpc - po_pmhc1d3.tpc - po_pmhc2.tpc - po_pmhc2d.tpc - po_pmhc2d1.tpc - po_pmhc2d2.tpc - po_pmhc2d3.tpc - po_pmhc3.tpc - po_pmhc3d.tpc - po_pmhc3d1.tpc - po_pmhc3d2.tpc - po_pmhc3d3.tpc - po_pmhc4.tpc - po_pmhc4d.tpc - po_pmhc4d1.tpc - po_pmhc4d2.tpc - po_pmhc4d3.tpc - po_pmhc5.tpc - po_pmhc5d.tpc - po_pmhc5d1.tpc - po_pmhc5d2.tpc - po_pmhc5d3.tpc **** BUGS **** Some of the male lips clip slightly on the character creation screen, but they are fine during the rest of the game. Let me know if you find any others. ******* CREDITS ******* - Fred Tetra, for developing the KOTOR Tool - Stoffe, for developing TSLPatcher ********* CHANGELOG ********* 1.0.1 - Updated Readme for clearer instructions on using reskins with this mod. 1.0 - Initial Release *********** PERMISSIONS *********** You may not redistribute this mod on other sites without my permission. You may use this mod in your own if you ask me. ********** DISCLAIMER ********** THIS MODIFICATION IS PROVIDED AS-IS AND IS NOT SUPPORTED BY BIOWARE/OBSIDIAN ENTERTAINMENT OR LUCASARTS OR ANY LICENSERS/SPONSORS OF THE MENTIONED COMPANIES. USE OF THIS FILE IS AT YOUR OWN RISK AND THE ABOVE MENTIONED COMPANIES OR THE AUTHOR IS NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR COMPUTER FOR THE USAGE OF THIS FILE. -
1 pointExactly. Oh, you just save the changes in the Override folder, just like any other mod that doesn't use TSLPatcher. EDIT: I've made a couple edits to the previous post to make it clearer. Try reading it again, see if that helps.
-
1 pointTry K1 Heads Port.
-
1 pointNote that if all you want is a head model swap, that is done by making changes in appearance.2da, which you'll find in BIFs - 2da.bif - 2D Array. That will display a list of the models and textures the game uses, in a series of columns and rows. You just need to replace the head model your character uses with Deadeye's. Deadeye's row is 412, so his head is the number you see under normalhead (74). Just copy that and use it to replace your PC's. In order to locate your character, you need to understand the labeling and the face order. Look for the bunch of rows that start with P_MAL ... Then there's A for Asian, B for Black and C for Caucasian. SML is the Scoundrel class, MED is Scout, LRG is Soldier. You'll want to replace a Caucasian one, naturally, although the Asian underwear texture probably matches Deadeye's skin tone better. You can check the face order by a couple ways. You can open the texture files in swpc_tex_tpa.erf, but what I usually do is just launch the game and click on New Game to go to the character creation menu, then check which one your character is. There are 5 for each race. You'll still have the problem of the portrait not matching the head, though. You won't have dark side transitions either. EDIT: Note that you'll have to change Deadeye's row for it to use a different head, since the game leaves NPCs headless if they coincide with the player's.
-
1 pointInstall Kotor Tool (KT). Open KT > Kotor 1 > ERFs > Texture Packs > swpc_tex_tpa.erf > N > N_DeadeyeH01.tpc > extract. Simplest way is to reskin an existing head texture, but you won't have darkside textures/transformation without creating additional textures. KT > ERFS > Texture Packs > swpc_tex_tpa.erf > P > any PMHC but let's give an example one > PMHC05.tpc. Rename extracted N_DeadeyeH01.tpc to PMHC05.tpc. Copy and paste into Override folder located within the Kotor main folder, where ever it was installed to. May have to copy that file four times and rename each copy as the following PMHC05d PMHC05d1 PMHC05d2 PMHC05d3 These represent darkside transitions, I'm not sure if you gain darkside points if the face will default to vanilla files and change your face to another face texture so this additional step will prevent that possibility. Lastly, your portrait will not look like Dead-eye Duncan, because the game doesn't have a portrait of him. You can make a custom portrait with textures, or grab a sloppy screenshot, crop/edit it, then re-name it as PO_PMHC5.tpc You can find the vanilla head portrait from KT > ERFS > Texture Packs > swpc_tex_GUI.erf > P > PO_PMHC5.tpc but this would be for the normal head and not for Deadeye duncan. Notice that the player heads correspond with each other, so PMHC05 is listed as PO (for portrait) PO_PMHC5.tpc Now you have a working head and possibly a working portrait. An important note is that there are only so many file extension the game will recognize in the override, mainly tpc or tga. Good luck!
-
1 pointThat's a great picture right there. I didn't even know about Juan Giménez. Just learned about him searching for the image. Great futuristic vibes.
-
1 point
All the vanilla 'Master' robes are robes with capes, truthfully they 'might' be a rarity as of right now so in coming patches that will change. I can guarantee in this mod Jolee comes with caped Jedi robes for free. -
1 point0.8.3 Experimental Files for the Expanded Galaxy Project now feature demo levels of the Endar Spire. The video is outdated and the levels are now 99% functional / can be played through, I suggest starting a new game, skipping the prologue and then warping to "end_m01aa" In the future I might work on more levels, I found deconstructing and rebuilding these levels to be a really fun experience. I also think that they play and feel a lot better.
-
1 point
Version 4.1
84,463 downloads
THE UPDATE IS FOR STEAM USERS, PLAYING THE ASPYR VERSION IN 2K. -------------------------------------------------- Title: Widescreen UI Fix for Knights of the Old Republic 2: The Sith Lords -------------------------------------------------- Special Thanks to the following individuals: Alien - For the original version of the 16x9 mod, without which none of this would have happened. tk102 - Since GFFEditor broke stuff and KGFF saved the day, teekay deserves some recognition for his awesome (TSL-friendly) tool. -------------------------------------------------- Original mod info (including link to download and screenshots) can be found here: http://steamcommunity.com/app/208580/discussions/0/864975632546978851/ As you can see, Alien's work is remarkable. Unfortunately, v.1 has some issues with the Actions UI in the lower left (mines and force form are borked, and the action description hovers over the menus rather than displaying above, making the arrows a pain to use). After some digging around, I was able to fix these issues and am releasing the fix with Alien's permission. *CD/DVD/GOG/Steam (Non-Aspyr) Installation Instructions* Download the GOG version Extract the download Select either the 16x9 or 16x10 version (not both) Copy the folder to Override To uninstall, remove the installed files. *Steam (Aspyr version) Installation Instructions* [Optional, but recommended] Find equip_p.gui in the game's install directory and make a backup Delete equip_p.gui from the install directory Extract the contents of the download to Override. To uninstall, remove the installed files. -
1 pointThere's your next project: Hanharr Romance Mod
-
1 point
Version 1.22
20,495 downloads
Author: Kainzorus Prime Mod Name: NPC Overhaul Mod ************************* Under NO circumstances is this, or any of my other, mod(s) to be posted on ANY site other than by myself. ************************* 1. Info =========== This mod attempts to fix the ‘clone effect’ which TSL is notorious for, across multiple locations. It differentiates the NPCs in an attempt to eliminate several of them looking identical in one location, due to the way it was set up by Obsidian. It also provides a different clothing for each starting Jedi class, rather than conform to a single texture across all of them. Several shaders across multiple characters are also restored, such as the Mandalorians, Hutts, droids, etc. 2. Installation: ========= Run the patcher for each listed location and let it do its magic. I apologize for the need to run it several times, but it’s the only viable way. 3. Credits: =========== Special thanks to: Holowan Laboratories - For all the great resources. 4. DISCLAIMER: =============== This Mod is not supported by LucasArts, Bioware or Obsidian. Please do not contact them for support of this mod. Copyright: Star Wars: Knights of the Old Republic, characters, items, etc. are trademarks and copyrights owned by their respective trademark and copyright holders. Star Wars: Knights of the Old Republic: The Sith Lords, characters, items, etc. are trademarks and copyrights owned by their respective trademark and copyright holders. Bioware and the Odyssey Engine are trademarks of Bioware Corp. Obsidian are trademarks of Obsidian Entertainment. All trademarks and copyrights contained in this document are owned by their respective trademark and copyright holders. More Screenshots: -
1 pointAmongst the little things I am playing with, this feature appears to be in a 'releasable' condition.
-
1 point
Version 1.2
11,884 downloads
The mood was upon me . . . Here's my second small mod. Texture for Atris' Sith Holocrons ======================================== MOD AUTHOR: Sith Holocron ORIGINAL RELEASE: 19 JAN 2013 UPDATED RELEASE: 17 JUL 2014 UPDATED RELEASE: 28 FEB 2018 GAMES: Star Wars Knights of the Old Republic 2: The Sith Lords Description: ------------ Being a stickler for detail, I always been irked about how the Sith Holocrons were represented in Atris' Holocron Chamber in her Secret Academy. I decided to do something about it. Installation: ------------- There are two versions of the holocron now: the original version and the unreleased-until-now animated version. Each version has its own folder. Choose your version's folder and put the 2 files in it into your Override folder. For Star Wars Knights of the Old Republic 2 - Extract the TGA file into the Star Wars Knights of the Old Republic/Override folder. Uninstallation: ------------- Take it out again. Known Bugs: ------------- None known at this time. Legal Disclaimer: ------------------- All materials and copyrights belong to LucasArts, Bioware and Obsidian Entertainment Inc., I own none of the materials, and I'm not making any money out of this mod. It is to be distributed as-is without alteration, unless by permission of the mod author. This mod is not to be distributed for profit, either. I hereby state that I specifically do NOT wish this mod to be uploaded to Steam Workshop - with the exception of Hassat Hunter who has my permission to do so. I may release this on NexusMods at a later date but I don't wish others to do so. Usage in other mods must be requested AND approved by me before your use. -
1 point
Version 1.0
14,376 downloads
so here is the HD visas part of my ongoing texture project series, I desired to maintain the vanilla "look", but with much higher quality textures, I feel I have sufficiently achieved this, (i took a little liberty on the dark side transitions, but they are definitely not "movie style") the usual disclaimers apply, and of course you don't need my permission to reuse this, as long as it's not for profit. -
1 point
I like the idea a lot. Ahh... How many times walking to that compartiment knowing in advance the answer... Hoping to be able to melt -just a bit- her hardened heart (and a glitch in the game...) What about make the romance available for female characters as well? The hottest huntress in the galaxy seduced by a sensual female exile? As a female PC she does not even want to be my friend... sniff... -
1 point
working good thanks, good for the "silent strong type" Player Characters out there
-
1 point02 - [TUTORIAL] - Creating a Merchant - TSL 03-05 - Using ERFEdit 03 [ADDITIONAL] - Picking an NPC to place in your level - TSL 04 - [ADDITIONAL] - Picking Placeables to fill your level with - TSL 05 - [ADDITIONAL] - Picking Alien Voice Over Dialog for your level - TSL 06 - [ADDITIONAL] - Placement & Rotation 07 - [TUTORIAL] - Waypoint Markers 08 [TUTORIAL] - Scripting Basics 09 [EXAMPLE SCRIPT] - Spawning NPC's on Enter 10 [EXAMPLE SCRIPT] - Making NPC's Hostile! 11 [EXAMPLE SCRIPT] - Trigger talking to an NPC! 11 [EXAMPLE SCRIPT] - Make an NPC walk randomly 12 [EXAMPLE SCRIPT] - Place a dead NPC I will continue to provide examples that I think might be useful to people, these are all for TSL so far. I hope these tutorials and any others I write will help people continue to make mods for KotOR 1 & 2. These tutorials are getting shorter and less detailed, I may or may not go back and re-write them at some point but if anyone struggles with anything feel free to message me and let me know what I haven't covered very well.
-
1 pointQuery: What? Yes, you heard that right, what started as what was (probably) a joke made by @A Future Pilot on the r/kotor discord has gotten my creative juices flowing. If you're like me, you might have asked yourself at some point "HK-47 is my favorite companion in the KotOR games, so why can't I romance him?" Well, soon™️ you can! The goal of this mod is to make a believably written, slightly tongue in cheek but also emotionally sound "mini romance" option between a dark sided player character and her/his homicidal droid companion. What do I mean by "mini romance"? For now, I am going to try and keep the scope small while I learn the fundamentals of modding. I have finished a first pass at the script, and will be working on recording the voice over sometime soon to get a feel for how it all sounds when spoken. Right now, it is a total of 2 to 3 conversations, depending on whether you pass a [Repair/Computer Use] (player's preference) skill check on the first try or not. Perhaps this will expand in the future, but right now, I think it gets the job done without needless beating around the bush. This is an optional/additional romance and its not meant to rival/replace any of the vanilla options in terms of complexity. The non-spoilery gist of it is, HK has discovered that he has developed what he sees as a flaw in his programming since he's started travelling with you, that's since grown stronger with every act of cruelty you inflict upon others. The player character has the option to dismiss outright, confusedly entertain his concerns to an extent, or try their best to understand the situation, some of which open up a path to a whole new look into his "abnormality" that's formed. Basically, I'll be using this thread to update with progress and let you know how it's going. Keep in mind, this is my first ever mod and thus I have no idea how long this project will take me. I'm also attaching to this post a design document that features all of the dialogue that I've currently written for the mod, if you're interested. I would appreciate that if you'd like to mention something about it in this thread, that you properly spoiler tag it. Thank you. - UC P.S. Let me make this point for you, so that you don't have to. HKromance.docx
-
1 point
To everyone in the thread who was having issues with crashing: I found the issue. One of the lines in "appearance.2da" was incorrectly modified. I fixed the file so that it works, if you guys want to download it here. https://www.sendspace.com/file/s7k9ln If you'd rather try and fix it yourself, you basically need use KTool to open the original "appearance.2da" in the "2da.bif" file, find the data values for DarthRevanM under the "race" column, and modify this mod's 2da file so that it matches up to the original. -
1 pointAt the very least, many of those immersion things seem worthy of becoming a standalone addition compatible with RCM
-
1 point.2da files are a very common and important file type in both KotOR games and are also very common to be edited in mods. That's why this tutorial aims to bring you a list with detailed explanations on what they do. Introduction You can find all .2da files in the 2da.bif file, where they can be accessed using KotOR Tool. KotOR Tool also provides a 2da-editor to modify them as you want. Basically, .2da files are 2d arrays or put simply: tables, just like you know them from programs like Excel. The one difference here would be that in a .2da file, each column has a specific and pre-defined (hardcoded) function. Each .2da file collects a set of "objects" that differ in details. Thus every column in the .2da file represents a certain characteristic of such an object while each row represents one specific instance of this type of object. As a simple example, you could have a file called trees.2da that contains information on different types of trees. The columns would then include details like height, age, etc and every row would stand for one tree species with details entered in each entry of this row. This tutorial will consist of two parts: First a (currently incomplete) list of all .2da files used in both games with detailed information on what they do and what each column stands for. The second part will be a list of .2da files that exist in KotOR but that aren't actually used since they're only remnants from Never Winter Nights (an older game by Bioware based on the same engine). This second part is only for reference, so that you know these files are useless. Now, this tutorial is currently far from being complete. There are many .2da files that are still missing and even for those that are already listed there may be missing information or maybe even incorrect information. If you notice a mistake or know things that are still missing, please post them to this thread so that I can add them to improve on this ressource. Thank you very much A big thanks already goes to Fair Strides, who provided most of the information currently listed. Thank you! Used .2da files In this section I will (eventually) list all .2da files used by both KotOR and its sequel TSL. Most of these appear in both games and are identical or have only very minor differences. Those are marked with (K1/TSL) after their names and possible differences will be explained in the proper place. Some .2da files however differ on a bigger scale between the two games or exist only in one of them. Those are then marked by either (K1) or (TSL) depending on which game they are from. Each listed file has a short introduction that describes what these files are used for, followed by a list of their columns with descriptions. If there is no description for a certain column, then that's just because I don't know what it does, while descriptions written in red are unconfirmed and might be wrong. And as a final note: When you open a .2da file in KotOR Tool, you will notice the first column labeled (Row Label). This column exists in every .2da file and labels the rows numerically from 0 upwards. This label can then be used by other .2da files to reference specific lines from this file. But since this column is the same in every .2da file, I won't list it everytime. And here we go: acbonus.2da (K1/TSL) aiscripts.2da (K1/TSL) aliensound.2da (K1/TSL) ambientmusic.2da (K1/TSL) ambientsound.2da (K1/TSL) ammunitiontypes.2da (K1/TSL) animations.2da (K1/TSL) appearance.2da (K1) appearance.2da (TSL) appearancesndset.2da (K1/TSL) baseitems.2da (K1/TSL) bindablekeys.2da (K1/TSL) bodybag.2da (K1/TSL) camerastyle.2da (K1/TSL) chemicalcreate.2da (TSL) classes.2da (K1/TSL) comptypes.2da (K1/TSL) footstepsounds.2da (K1/TSL) globalcat.2da (K1/TSL) heads.2da (K1/TSL) itemcreate.2da & itemcreatemira.2da (TSL) portraits.2da (K1/TSL) regeneration.2da (K1) subrace.2da (K1/TSL) upcrystals.2da (K1/TSL) videoeffects.2da (K1/TSL) Unused .2da files This section will simply list files that are not used by the KotOR games. Many of these only exist in the KotOR 1 files and were removed for TSL. actions.2da areaeffects.2da caarmorclass.2da capart.2da categories.2da catype.2da chargenclothes.2da Changelog
Chroma(-10)Lightness(-20).thumb.png.aed2d718da50b47c91787424a2c4bc83.png)
