DarthParametric

Depends entirely on the specifics of what you want. A simple colour switch from one solid colour to another is relatively straightforward, at least in PS (and I assume Gimp has similar functionality). If you want patterns and so forth then it starts to become more complex. You could also edit the item to switch it to a different base armour model, if that might get you closer to what you want. Although that obviously adds a whole extra layer of complexity. If you think that doing it yourself is too much, you can always make a post asking for someone else to do it in the Mod Requests forum.

It would require a texture edit. KTool can extract the texture, but it is not a texture editor. You'd need something like Photoshop, GIMP, Paint.NET, etc.

You could do it all in one script. It would just be a series of if statements. But you'd have to edit the individual scripts for every merchant in the game. They aren't defined universally.

You don't edit any 2DAs. You edit the supermodel/s that holds the original anim/s, delete it/them, and replace it/them with TSL's version/s, giving it/them the same name as the original/s. Some knowledge/experience is required ideally, yes. I have no idea how you'd go about a rig transfer in Blender. Someone like @seedhartha would have to chime in with information about that. in KMax, there's an animation tool that lets you import an animation from an external model and map it to the scene rig (Anim Tools -> Mapper). It should be a simple case of autogenerating the bone name matches, since the rigs are more or less the same at the core, TSL's just has some added bones for flappy sleeves and cloaks. Given the complexity of supermodels, I'd suggest the easiest approach would be to remap the anim/s onto an empty copy of the target rig, export that, then edit the ASCII copy of the supermodel to swap the anim/s. You'll need to edit the ASCII anyway to add the sound events anyway, at least using KMax, since that doesn't import/export them properly. Strictly speaking you don't actually need to do the rig transfer. You could do the whole thing in a text editor, just swapping the anim blocks. But doing the transfer allows you to check that everything is working as intended, and adjust/fix it if not. K1 and TSL bone positions/rotations aren't entirely 1:1, which is why head model ports have facial animation issues. There is also a bit of a trick to compiling supermodels, since they are a bit wonky. @JCarter426 is the resident authority on the matter, and did detail the process in a post somewhere, although I can't find it at the moment.

You can't do that in K1 anyway. It's possible, yes. How practical it is depends entirely on how conversant you are with the game's models and animations, and importing/exporting them. I'm guessing "not at all"? Probably not the best place to start then. It will require editing one of the supermodels and replacing the existing anim with the TSL version. Before that you'll probably want to transfer it to the K1 rig to make sure it doesn't need any editing.

About goddamn time.

Might as well throw mine up as well. But I'm not going to bother with their life stories since I'm an altoholic so there are too bloody many. Click for embiggening.

It's simple. You renamed the OdysseyBase to Dia_Nu but didn't change the other instances of the original base name. They are all still linked to PFHA02, which no longer exists. So MDLEdit throws an error.

Here you go. k_fab_enter.nss a_xtracrystals.nss

From k_ai_master: case 1008: //KOTOR_DEFAULT_EVENT_ON_DISTURBED { //NOT USED } break;

Sure, go ahead. Usual deal, credit blah blah blah.

I'd guess it's the fact that that particular mesh (or meshes) has the dirt flag enabled. You'd need to edit the model/s to change it, but you need to flip some of the UVs anyway judging by your first pic.

void main() { object oPC = GetFirstPC(); object oComp = GetItemPossessedBy(oPC, "bao_cmpnts"); DestroyObject(oComp); object oMesh = GetItemPossessedBy(oPC, "bao_mesh"); DestroyObject(oMesh); AddJournalQuestEntry("bao_armor", 50, FALSE); }

Unless you can recalculate the positions of a multi-hundred/thousand vertex point cloud in 3D space in your head, no.

Win 10 with a GTX 1080 Ti. But the thread OP also had a 1080, and I believe we were both running on the same Geforce driver revision at the time, so I have no idea what the root cause is.

I don't have the issue at all. I only ever saw it one time on a single texture on an XP machine.

Yeah nothing special is required. This is just a simple file overwrite, since you can't patch a TLK to replace existing lines with TSLPatcher.

No, there are other issues. For example, problems with compiling condensed models were never resolved. The engine simply can't handle multiple on-screen animated entities, which is why Bioware went with the sprites. That's a non-resolvable issue, at least while still using Odyssey.

You'd reckon wrong.

STUNT_57.

Just warp directly to STUNT_55a if all you need is to see the end sequence.

Whether or not you side with Bastila on the temple roof. Check the scripts in that convo.

The game doesn't have any dedicated facial animations aside from the mouth flapping for VO phonemes. Anything else is part of a larger animation for talking or listening. You can try creating a DLG and specifying various conversation anims like TALK_NORMAL and so forth. Otherwise, in TSL you can script any anim in the game (in K1 you can only script a limited selection listed in nwscript.nss).