DarthParametric

Technically the Glorious Jewel is Nal Hutta. Nar Shaddaa was just one of its five moons.

Here: Ratgo Door Fix.zip I just wish one of you miscreants could tell me how you're managing it. I have never been able to recreate it. Edit the save to add in an armband that runs a custom script to close the door and reset its plot state, load the game and fire the script, save, test the scene triggers correctly and exit, edit the save to remove the armband.

First picture seems to be broken UVs on the left and bad/non-existent lightmapping and a missing emissive panel on the right? What about the second picture? UV misalignment? Not matching the layout on the right? And what's the module/s and the specific locations?

You can use the DestroyObject command, but trying to grab a corpse via script can be flaky. The most reliable way might be to first flag him as non-destroyable, something like: AssignCommand(oSion, SetIsDestroyable(FALSE, FALSE, FALSE)); ApplyEffectToObject(DURATION_TYPE_INSTANT, EffectDeath(), oSion); DelayCommand(1.0, AssignCommand(oSion, SetIsDestroyable(TRUE))); DelayCommand(1.1, DestroyObject(oSion)); Adjust timings as necessary.

Besides being not able to spell, it's a 2DA edit that was literally already done 20+ years ago. So new for zoomers I guess? But muh Nexus pennies!

You don't want to leave the vanilla script. That kills him. You need to replace that script with your own that does all the stuff the vanilla script does and then modifies it to get the result you want. Yes, to add static cameras you will need to edit the module's GIT. Which means that they won't take effect in a saved game (unless you extract the save and edit its module GIT). Alternatively, you can create an animated camera, which is a motion track stored in a model that the game can attach a camera to. Any time you see a cutscene with a camera panning or the like, that's an anicam. But you can also use it for simple position switches where you just jump the camera to different points as needed. This would require the use of Blender or 3DS Max and their appropriate I/O scripts.

This is all scripting for the most part. If you look at 903sion.dlg, E121 should be the node of interest. You can see that fires the script a_sion with parameter 3 - https://github.com/KOTORCommunityPatches/Vanilla_KOTOR_Script_Source/blob/master/TSL/TSLRCM/Modules/903MAL_Malachor_V_Trayus_Academy/a_sion.nss That triggers case 3 of the switch runs that function that handles his death scene. Clears all effects on him, plays the ANIMATION_LOOPING_RAGE animation on him for 1.5 seconds, removes his minimum 1HP flag, applies the instant death effect, then unlocks the door. If you want to prevent a node from skipping and run for as long as you want, then you need the ActionPauseConversation and ActionResumeConversation functions. However, you have an added wrinkle here. Sion is the conversation owner. A conversation will immediately terminate if the owner dies. Typically in cases like this where an NPC needs to die, you get around it by making the owner an invisible placeable, but in this case that would probably break all the other scripts. So you'll need a bit of slight of hand to get around it. What I would do is have him manually play the death anim, spawn the VFX placeable over the top of him, then use that as cover to jump Sion somewhere out of sight so he can be killed after the cutscene finishes. The question will be whether the VFX actually obscures him sufficiently. That will probably require some custom shot framing with new static cameras. You could probably do a wide shot from behind the PC and use the PC themselves to block it if absolutely necessary. You can script switching between static cameras using the SetDialogPlaceableCamera function.

If it exists, it would likely be in the Xbox version rather than the PC version. That said, I can see two references in the PC TLK: <string id="79038" soundlength="0.000000">This is Captain Opelle of the Valiant.</string> <string id="79046" soundlength="0.000000">My schematics show the closest docks to your location at Module 083. We&apos;ll arrive shortly and handle the situation from here. Opelle out.</string>

Yes. The model format only "officially" supports 16 bones per mesh, but actually has provision for 17. Hence why vanilla body models are split.

There's something very weird going on. There is no UV data stored in the traditional manner if you load it into Max, but if you it into Blender it appears to show island boundaries that conform to the body shape. Doesn't actually show any UVs though, although I have no idea how to use Blender's UV editor. Whatever you did, you apparently didn't store the UVs in channel 0. Not sure how that would make the mesh invisible though.

This is an issue with the model itself, not the UVs. Attach your exported MDL/MDX and source blend file.

Like any other global item, you can check the UTIs in BIFs -> Templates.bif using something like Holocron Toolset or KTool. Components have the ResRef: compont_00001 Similarly, chemicals have the ResRef: chem_00001

Not particularly difficult for the most part, if you know what you're doing, but not the ideal first mod for someone who has no experience. This would require multiple script edits, dialogue creation, cutscene creation, and the ever-thorny issue of dealing with adding/replacing vanilla companion/NPC dialogue.

You should look at how vanilla faked metal works using envmaps (i.e. cubemaps). Basically you create a mask in the diffuse texture's alpha channel, and then create text file with the same name as the texture and the TXI extension. In that you can add various instructions that tell the engine how to render the associated texture/s. In this case, you'd want something like envmaptexture CM_Baremetal If you are converting your diffuse to a TPC, you'd need to convert it again and make sure you tell TGA2TPC to use the TXI. It will then embed the TXI data into the TPC (TGAs use a loose TXI file).