WildKarrde

Sure, I'll work on that next after I finish the Taris Freighter lightmaps.

The wrecked ones should be OK as-is, they look like they already have a similar detail level as the Manaan/Nar Shaddaa freighters. To clarify, for Taris I just borrowed the higher-quality freighter model from Manaan as noted by Dark Hope in this thread:

Thank you! I may just do that after I explore the lighting/lightmapping a bit more. It’s only two freighters, so I suppose it wouldn't be too much work. Creating the lightmap UVs tends to be the slow part for me, but I would only need to do that once for both freighters. There is also the drawback that the baked lighting will remain static when the freighters are moving around…but on the other hand, that never bothered me with the vanilla version. On a quick examination, I see it at the Nar Shaddaa docks (which already uses the higher-quality version) and flying over the Onderon spaceport. I don’t suppose anyone happens to know of any others offhand?

I know I'm a little late, but how about this? Before: After: Before: After: A few notes on the edits: The Manaan freighter is slightly larger than the original ones on Taris. I chose to keep the Manaan sizing instead of trying to scale them down. I relied on the in-game lighting instead of creating new lightmaps, which is why the new freighters look somewhat darker than the originals. While I was at it, I also patched a major hole in the bottom of the upper freighter's platform. High Quality Taris Freighter.zip

A few additional notes based on my own experience: KOTORBlender can actually handle multiple models and model roots/OdysseyBases in a single scene. The key is that when you export the model, you must first select the OdysseyBase of the specific model you wish to export. Except for walkmeshes, KOTORBlender actually ignores the Blender material completely. All of the parameters that KOTORBlender cares about are set up as properties of the mesh under “KOTOR Model Node”, which can be edited independently of the material. I’ve had cases where I was lazy and edited the texture name in the model property but didn’t bother to update the Blender material to match, and it still exported fine. The lightmap UVs are saved under a second UV map called UVMap_lm, and the lightmap texture is set in the KOTOR Model Node properties of the mesh. Blender calls it the Parent Inverse, you can read more about it here: https://docs.blender.org/manual/en/latest/scene_layout/object/editing/parent.html. I’ve mainly had it come up as an issue when parenting objects. I recommend using the “Make Parent without Inverse (Keep Transform)” command to avoid offset issues like this. I also use this handy addon, which can zero out the Parent Inverse of a mesh after it was already parented while keeping its current position: https://github.com/drewcassidy/blender-apply-parent-inverse. Collisions for area models are set by creating non-walkable areas in the walkmesh, which is stored in the .wok file matching the model name. KOTORBlender will read and write .wok files as part of the import/export process if they are in the same location as the main MDL/MDX.