[K1] Replacing/adding into .mdl and how to retain animations?

[CarthOnasty 214]

First things first: yes, this is star map related. 😉

I created new arms I'd like to try out but have no idea how to get those into the current star map model. (plc_starmap.mdl) I created them separately.

So question would be, how do I replace what's in the old model with what I have created, and then how do I retain the animations?

[DarthParametric 3,785]

Pretty sure I already told you how to do this. Just copy and paste from one ASCII to another. Export your geometry in the same hierarchy as the original and all the pivots and rotations are the same, etc., then copy and paste all the emitter nodes, etc. and anims from the vanilla file. Possibly you may have to fiddle with the hierarchy to makes things easier.

[CarthOnasty 214]

I'm sure you did. I'm forgetful and don't save things.

So I would need to export the new model to ASCII via KotORMax/Blender. And that's the code I would copy and replace in the ASCII of the original model?

How would I know if I'm exporting it in the same hierarchy?

[DarthParametric 3,785]

I don't use Blender, so I couldn't tell you how to handle that side of things. Here's what the top of the hierarchy looks like in Max:

So you'd have to deal with the legs being below parts you'd (presumably) retain from the vanilla ASCII. It's actually not too difficult if you use Notepad++ and the Aurora MDL language definition for it. That will let you collapse each mesh/object so you can easily select and excise bits you don't need:

[CarthOnasty 214]

Okay, yeah, Blender's basically the same.

 

Thanks for the Notepad++ tip, that's really convenient!

And then for my new model, would I need to export that as an .ascii? And that's what I would copy/paste?

[DarthParametric 3,785]

Yeah I would just start with a copy of the original star map, delete everything except the base and the meshes you are going to replace. Add your new meshes and give them the same pivot position/orientation as the originals. Export that as an ASCII when done.

You don't even necessarily need to delete the originals - you could just disable their render flag. They might be useful as shadowcasters. That would also make your life easier for the merge, since if you make your new meshes each children of the originals, then all you need to do is paste the data for your new meshes at the end of the geometry list , since their data block lists their parent object (although you would need to edit the render flag settings of the originals). Order in an ASCII is more or less irrelevant, outside of listing parent objects before children. I'm not sure if that is strictly required, but MDLEdit is kind of finicky so better to be safe than sorry.

[Hunters Run 57]

You could also  change the data of the legs to your new legs and import the animations later. 

 

 

Some notes - you will need to copy your arms to new scene and import without animations if you want to take this approach, and you should reveres that  when it's time to import animations(import only animations ). Also you may have to mess with the rotation and origin to get it to line up.

 

[CarthOnasty 214]

Rough progress: