Search the Community
Showing results for tags 'appearance.2da'.
Found 3 results
Could someone help me out? I'm attempting to add another line in the appearance.2da file. I'll attach it as a zip file so you can see what I've attempted. I've spent the last 5 hours reading tutorials and threads on deadlystream and Holowan labs (using the internet archive). However, I cannot be sure I've successfully added a new line to the appearance.2da. I believe I have though. I want to use the newly added 2da line to change the look of a custom uti file allowing a PC or party member to wear the new uti with the new appearance. The issue arises is that, I am adding N_Mandalorian09 and my attempts to edit the XML file to a disguise have failed.. My changes to the appearance.2da do not show up. Therefore, I cannot make a uti recognize the disguise N_Mandalorian09. (I have learned how to test out the N_Mandalorian09 by giving it to a UTC, and I found out it does not work.) I've tried exporting the XML file editing it manually to show the disguise as N_Manadalorian09 instead of the default N_Mandalorian01, and then loading it back. This did not work. N_Mandalorian09 is the Appearance.2da line. Also, I have a N_Mandalorian09.tga test image. The goal is to add more wearable Mandalorian armor to k1. I've downloaded ShemL's mod and tried to learn what I could from there. > http://deadlystream.com/forum/files/file/665-mandalorian-ultimate-mod/ I'm completely stumped. Any help would be greatly appreciated. I have read the following: http://deadlystream.com/forum/topic/4725-detailed-information-of-2da-files http://deadlystream.com/forum/topic/4791-creating-new-npcs-via-appearence2da/page-2 https://web.archive.org/web/20121210211212/http://www.lucasforums.com/showthread.php?t=149992
Hey guys! I've got a bundle tutorial for you today. Although these two have nothing to do with each other, I wanted to bundle them together instead of just having two separate threads. Anyways, I'll be showing you two things for these tutorials: Creating a custom design with an armor plating for droids. Creating custom lightsabers that are also upgradeable. While everything is explained in these tutorials, I'll still try and put a little description for them here. For the first tutorial: In this video I'll be showing you how to put custom designs on droids via an armor plating, and appearance.2da. It's kind of hard for me to explain what exactly I mean, but have you ever wanted, say T3 to have a custom design when you equip a certain armor? Well, this will show you how. This applies to any droid, or well i guess any disguise. For the second tutorial: In this video I'm going to show you how to make custom Lightsabers for Kotor 1 and 2. Sorry if the tutorial kind of sucks at some points, I had to keep restarting certain parts because I messed up so much. Also, you don't have to listen to me about the whole "Don't use the same numbers that I use in my mod" I just say that so you can make yours compatible with mine. Anyways, hope this helps! Also, I follow the tutorial made by Achilles on how to create custom models for your lightsabers. I'll leave his text tutorial in case my video is too confusing (which it probably is). Achilles text tutorial: Resources that you will need to build your mod: • KotOR Tool – Used to locate and extract templates, models, and skins • GFF Editor – Program used to edit .uti (template) files. • Hex editor - used to modify .mdl (model) files. • Tpc2Tga.exe – Simple executable that will allow KT to automatically convert game images to convertible format • A file reference – used for identifying files in KT. I like to use http://www.goldensun-syndicate.net/kotor/codeFAQ.txt • Photoshop (optional) – used to modify game images such as saber color, robes, armor, etc. Files that you will need to extract using KT: *Note: xxx represents the model # Templates – Assign properties to the item(s). Use the file reference to determine what files you need. For instance g_w_sbrcrstl14 is the code for Blue Lightsaber Crystal. Knowing this information will help ensure that you extract the correct files. • g_w_sbrcrstlxx.uti <BIFs/templates.bif/g_w_sbrcrstxx.uti> • g_w_lghtsbrxx.uti <BIFs/templates.bif/g_w_lghtsbrxx.uti> Models – Used to render the image of your item in-game • w_lght_xxx.mdl <Bifs/items.bif/w_lght_xxx.mdl> • w_lght_xxx.mdx <Bifs/items.bif/w_lght_xxx.mdx> Images – used to skin the model in-game (ie they’re what make the blue lightsaber file appear as a blue lightsaber in your game) **Note: Rather than use the Extract button to save these files, you will double click them to open the Image Viewer window. Use the Write File button to extract the file to your save folder. ***Note: In KT open Tools<Options and set the program to automatically convert .tpc files to .tga format. Make sure that Tpc2tga.exe is in the same directory as KT for this to work. ****Note: If there are any “special instructions” in the Image Viewer window, you will need to copy them into a .txt file in your save folder. You will modify the format of this file later. iw_sbrcrstl_xxx.tga <ERFs/texturepacks/swpc_tex_gui.erf/iw_sbrcrstl_xxx.tpc> iw_lghtsbr_xxx.tga <ERFs/texturepacks/swpc_tex_gui.erf/iw_lghtsbr_xxx.tpc>-w_lsabre<color>01.tga <ERFs/swpc_tex_tpa.erf/w_lsabreturq01.tpc> Other Files *Required* w_lsabre<color>01.txt – You should create this file in your save folder and copy the special instructions from w_lsabre<color>01.tpc into the body of the file. You will change this file later. *Optional* upcrsystals.2da <bifs/2da.bif/upcrystals> - This property table is used to make lightsabers upgradeable in-game. Although optional it is highly recommended that select this option. More details will be available later in this tutorial. How to build your lightsaber: Open GFF Editor and use File<Open to open g_w_sbrcrstlxx.uti. KT has it’s owned GFF Editor, but I’m used to using this one. Please note the following properties: • LocalizedName – this is the display name that the game uses when rendering your item in the gui (ie inventory screen). The # in STRREF box refers to the dialog.tlk file, but not to worry. Change this number to -1 and change Language to 0 and hit Enter. The box below should now be editable. Go ahead and enter a custom name for your crystal if you would like =) • ModelVariation - this number of the saber model. Referring back to our code resource, we see that the game already uses 01-19. You will need to pick a unique number between 20-99. *****Note: be sure that you do not use a number already taken by another mod that you plan on using. • Tag: change the number at the end of this name to the same number that you selected for ModelVariation • TemplateResRef: same steps as Tag • Save your file Open GFF Editor and use File<Open to open g_w_lghtsbrxx.uti • Follow the same process for LocalizedName, ModelVariation, Tag, and TemplateResRef as outlined above. It is HIGHLY RECOMMENDED that you create a custom name for your lightsaber. Not only does it help you identify it in your inventory, its fun! ##Note: It is very important that the unique number used for your crystal and the saber is the same (example 99) ####Note: This is also where you would modify the properties of your weapon, but that’s another tutorial. • Save your file Open your Hex editor and use File<Open to open w_lghtsbr_0XX.mdl. • BREATHE! • Use the Text Find function to locate the references to your w_lsabre<color>01 file. I usually look for “01” or the color (“blue, red, turq, etc) to ensure that I find it right away. • Very carefully change the 01 to 02 • There are 4 of these references. Find the other three and change them as well. ##Note: Double Bladed lightsabers will have 8 of these references. ###Note: changing only some of these references will result in a multi colored saber blade • Save your file Rename all of the files in your save folder, except w_lsaber<color>01.tga and w_lsaber<color>01.txt to reflect that model number that you selected. For example: • g_w_lghtsbrXX.uti => g_w_lghtsbr99.uti • g_w_sbrcrstlXX.uti => g_w_sbrcrstl99.uti • w_lghtsbr_0XX.mdl => w_lghtsbr_099.mdl • w_lghtsbr_0XX.mdx => w_lghtsbr_099.mdx • iw_sbrcrstl_XXX.tga => iw_sbrcrstl_099.tga • iw_lghtsbr_XXX.tga => iw_lghtsbr_099.tga Lastly, • Rename w_lsaber<color>01.tga to w_lsaber<color>02.tga (remember we changed the reference in the model using Hex editor) • Rename w_lsaber<color>01.txt to w_lsaber<color>02.txi (note that we changed the file extention here. You will receive an pop-up. Just click through it) All finished! Copy and paste all of these files into C:\Program Files\Lucas Arts\SWKotOR\Override, open your game, and enjoy =)
This is in reference to the forum topic discussed HERE. This tutorial is to show step-by-step instructions in how to manually change appearance.2da to resolve the transparent character issues that some have reported with certain textures. * Models used are from the Battle Hardened Mandalorians mod by Canderis - only using this as example as I experienced this issue with this mod, and it's a really cool re-texture... Some textures containing alpha channels show up as transparent in-game: This is how you fix it. It is highly recommended you backup you appearance.2da file before proceeding. Extract appearance.2da using KOTOR tool. - you can open it by double-clicking on the appearance.2da file in your Override folder Find the model you are trying to fix. In this case, I'm looking for Alien_Mandalorian. Highlight the row(s) and scroll to the right until you see the envmap tab. Most of the entries in the field should read DEFAULT. Change DEFAULT to read CM_Baremetal in all of the models that you have transparent textures for. Go to File->Save as appearance.2da.b.... into another folder. Copy to the override folder, overwriting any files with the same name. When you launch you game, the characters should now show all texture maps as they were meant to be: And that's it