DarthParametric

Trying out swapping out the terrible crowd sprites in the Taris arena with some from TOR. Also did some remodelling of the "stands" as well, resizing them and adding some glass barriers.

Hypothetically. But only if you are willing to subject yourself to the Windows Store.

No. They were dead anyway. At least now they will live long enough to ship Outer Worlds, and the contract with Take Two should prevent MS from screwing it up. Ditto Wasteland 3 from inXile. Enough deals are in place to prevent either ending up as Win 10 Store exclusives. But all bets are off after that. Both will be churning out exclusives for the Xbone in the future, so whether you are into action console faire determines your take on it. But we weren't getting another KOTOR 2, Mask of the Betrayer, or New Vegas anyway.

Notepad++ is what you want to use, at least on Windows. Then you can use the Aurora MDL language definition and @JCarter426's NSS language definition.

If your head is a player/party member head, you'll have to do a lot more work to integrate the mask into the model than just fixing the hook due to the way head textures and DS transitions work. Even if it's an NPC, fixing the hook is still probably more advisable. If you already added the hook correctly via editing the ASCII, then all you need to do is load that ACII via KOTORMax and position the hook properly. Typically you'd want to import a mask model, make its OdysseyBase a child of the hook, select the Move tool, switch its co-ord system to Parent, then zero out its position. Now you can select the hook itself and manually move it into the right position, using the mask as a guide. I'd suggest using something like the Verpine Headband (I_Mask_011) rather than a full face mask. Once the hook is positioned, delete all the mask bits and then export the head model. Or you could even just set the co-ord system back to World or View and copy the XYZ values of the hook into your original ASCII.

Steam doesn't include it. GOG has it, but only as a separate "goodies" download I believe.

Ah, just outside the door. The wall panel is DXN_Tmp3. The wall stone inset is TEL_rock02. The side stone floor is OND_fl03. The center floor strip is TEL_rock02.

Interior or exterior? The former is 411DXN, the latter 410DXN. Edit. That would appear to be a reskin. That's not what the vanilla module uses, assuming this is 411DXN.

Might help if you gave the exact location.

I know there was at least one other one doing the rounds years ago on LucasForums. You could check Nexus Mods.

One of the bearded mullet man mods it looks like. You could try the brown option of mine: https://www.darthparametric.com/files/kotor/k1/[K1]_Bearded_Mullet_Man_PMHC04.7z

As I said earlier in the thread: Every time someone asks, I bump it back to the bottom of the list. Ask me again in a year's time.

Yeah it patches the UTCs for Kaah and Bastila's hologram UTCs to point to new appearance.2da entries with fixed, full body models. Thanks for the confirmation. I have updated the readme/instructions to add references to v1.5.

No need. I already have a fix, just need to test it in-game. Edit: I've uploaded a separate compatibility patch that resolves the issue.

What's the actual nature of this conflict?

I haven't checked it properly yet, but a cursory glance over the mod's page would suggest that the added changes are all related to the M4-78 planet itself. I am assuming 1.5 continues with the added Korriban module route they went with in 1.3, so choosing the 1.3 option in the installer should be fine. If you want to be certain, check for the presence of RIM files labelled "703KOR" in your Modules folder. I'll make a proper assessment and update the instructions over the weekend.

It happens when KTool can't find the install directory. It was coded back in the original 4CD version days, so all it knows is the registry key for that version, which it looks for to find the install directory. If you have the GOG or Steam versions, it won't see them. The fix is fairly easy, a dummy registry key pointing to the install location. See this post for details.