DarthParametric

Blender has built-in GLTF support, so the GLB would be your best bet. Note that the model was textured for a modern PBR rendering pipeline. KOTOR uses an extremely basic Blinn-Phong based renderer, so you'll need to convert the textures to work with that. Fortunately it's an extremely simplistic set of metals for the most part. Unfortunately, KOTOR doesn't support specular, but instead tries to fake it with cubemaps. Getting metal to look good is challenging. One other thing of note is that while KOTOR does support normal maps, its implementation is poor, so detail relying on normal maps won't show up as well. As to the use, you don't need to request permission. It's already licensed for use with attribution. That's the entire point of the license.

Ah, thanks for the tip. Doing a bit of poking around, it seems like Qwen Image Edit might be a better bet, since it appears to be arguably at least as good, but more importantly you can run it locally with a quantised version.

Bit of an off-topic question, unrelated to KOTOR, but does your model handle merging two images? Or img2img to merge/morph aspects of one image into another? I'm playing around with some portraits from another game and I wanted to change one of the full body portraits of a party member in their starting armour to what they wear later in the game. I've looked around a bit and there doesn't seem to be a lot of off-the-shelf stuff for that type of thing outside of prompt-based approaches.

You can try using the Mesa DX12 or Vulkan wrappers available here - https://github.com/mmozeiko/build-mesa/releases/latest Grab mesa-d3d12-x64 for the former or mesa-zink-x64 for the latter. Extract the opengl32.dll from your chosen archive and put it in the game folder (next to the exe). Note that this means it is not compatible with GLIntercept or anything else that does the same sort of DLL hijack, like Reshade, etc.

Based on a quick bit of Googling, sounds like the save format is probably still the same. Your saves should be in Android/data/com.aspyr.swkotor/files/saves apparently. Attach the save you want edited and detail everything you want changed.

Impractical to the point of never eventuating. Especially solo. If you are that keen, there are already a bunch of engine implementation projects you could get involved with. Check out the OpenKotor Discord and talk to the folks there - https://openkotor.com/#projects

Seems like your 2DA was borked by a mod that was poorly implemented. The vast majority of rows should be DEFAULT by, well, default. Mostly it's only the droid rows that use CM_Baremetal, aside from a few extras like Mandos, swoop gang members, etc.

You should set it to DEFAULT or ****, not CM_Baremetal.

Most of the combat stuff is probably hardcoded to some degree. It could be possible to edit that via the exe hacking project. Perhaps @Lane could offer some insight as to the practicality. Aside from that, you can pipe messages to the feedback window via script. If you wanted to add additional information, that might be one route, editing the AI scripts.

Don't Break It Again, Admiral.zip

So this topic came up on the DS Discord's modding channel. Not sure how practical it would be, but I thought I'd run the idea by you. Someone asked about having a walk/run speed penalty being applied based on the type of armour equipped. Since this is controlled via the appearance.2da row's walkdist / rundist / driveanimwalk / driveanimrun values, I figured the only practical route would be some sort of lookup that checks the creature's currently equipped armour class and then dynamically scales those 2DA values according to some tiered list of penalty factors. Presumably you'd need to limit it to just the party to prevent issues with other appearance rows, and exclude Wookiees/droids and certain rows like the space suit/underwater suit disguises. It could also cause problems if it was active during conversations/cutscenes. I'm not sure it actually makes a lot of (or any) sense game-wise, but I found it an interesting mechanical concept nonetheless.

An item property disguise will only work if it is applied to an armour/robe/clothing item in the torso slot that points to the appearance row to replace it with. The only way to do it via an armband would be to create a script that fires EffectDisguise. But it would be quicker and easier for you to just use KSE to edit your save and change the appearance there.

As I said on the DS Discord, it's literally a nothingburger. It's pure concept art at this stage. The developer is a company started by Hudson earlier this year. Come back in 2030 and it might have a release date.

If you post them, I can show you how to manually merge them. Kind of hard for you to learn otherwise.

Per @th3w1zard1 , co-author of pyKotor and HoloPatcher: It's a rare unused feature of TSLPatcher that's off by default. HoloPatcher has it enabled. Basically tells you if a mod installs to a module directly (.rim/.erf/.mod) when it'd be 'shadowed' by a higher priority file existing in Override. See: https://github.com/th3w1zard1/PyKotor/wiki/Explanations-on-HoloPatcher-Internal-Logic#the-patch-loop Part of step 5. In other words, a mod has injected a file into a module (MOD), but a file in the Override will supersede it. On an unrelated note, why the hell is your game installed in the Users folder?