DarthParametric

You could always do the smoothing in GMax if necessary. Or get someone else to run it through Max/GMax for you.

Download the newer version of TSLPatcher - Delete Install Kyle Katarn.exe and use TSLPatcher.exe from the link above instead.

You've lost all the smoothing information by the looks. I gather the Blender script doesn't export that data.

It wouldn't make it any less of a pain in the ass to implement.

Given the issues with K1 placeable limits, I'd probably rule out discreet placeable versions altogether. You could try the room model edit approach, but I'd question whether the effort required would be worth it. If you do want to pursue that though, I'd suggest you not actually making the map itself part of the room. but instead just focus on adding some static props around it. A middle ground approach that minimises the work required and the sources of things going wrong, but still gives you some differentiation. As to your animation points, yeah, at this juncture there is no practical alternative to creating custom animations in Max/GMax. Perhaps one day you'll get an equivalent functionality for Blender, but for now I'd probably curb your ambitions in that regard (at least if you want to stick with Blender).

I was talking about the power up/down/hum sounds, which are specified in baseitems.2da and what I imagine OP was specifically referring to when talking about Luke's ROTJ saber sounds, but you are right that there are also all the swing/clash/impact/etc. sounds as well.

No, you won't be including this one. There are still elements of it to be revised, and it's far too much of a pain in the ass having multiple distributions of a large mod like that in the wild. This one should be fine.

Yeah, in other words, sabers are effectively hard-coded. What's there is what you are stuck with.

Yes, sounds are defined in baseitems.2da, and by default there are only 3 types of saber - short, single, double. You'd have to create new base item types for unique sounds, but I don't know if that would actually work for sabers given that upcrystals.2da only accepts the 3 base saber types.

I think you are thinking of @JCarter426

I don't have one myself, so can't test it directly. But I see that @jc2 's blog has a custom header.

It's your secret admin power at work. Mere mortals don't have access to it.

Yep, normal map functionality has been implemented. It was a two part issue, requiring both stuff in the model and saving the maps as TPCs. The models in this thread all use normal maps. There are some engine limitations regarding what you can do with them though, particularly when trying to combine them with envmaps.