Changing command pod orientation

[DChurchill]

I just created a probe body with command pod functionality, but what I'd like to do now is change the orientation so that "up" is "forward"

Notice the pitch is 90 degrees. I'd like to change that if possible.

[Greys]

command pod orientation is based off the orientation top level context in the mu, to alter the relative orientation of the parts models and the part itself you'd have to use MODEL{} to rotate the model, which will break every craft using that part, you'll want to create a duplicate part instead.

If you had made this part yourself you could rotate the models in Unity to achieve the same effect

[DChurchill]

Modeling in Unity is way more than I want to do. At least at this point.

I created a whole new part for this so I wouldn't break anything I already had. So to do this I need to alter the .mu file? What do I need to edit that? I got HxD so I could mess with the textures, but looking at the mu file with that doesn't help much.

Edited August 26, 2013 by DChurchill

[Greys]

You don't model in Unity, it's a finishing suite where you prepare assets from other programs and bring it all together into what KSP loads.

You need to edit the .cfg to use MODEL{} instead of mesh= (MODEL{} supercedes mesh=), and use MODEL{rotation=} to alter the rotation of the model within the part

[DChurchill]

Not sure what all that means, so maybe I'll leave it for the experts and just live with it.

I sort of follow what you're saying, but I'm not really sure what's involved. I just had an idea and started to run with it. I'd like to know how it all works, but I'm a total noob with it.

Other than knowing mesh = model.mu points the part to the mesh in the mu file, I'm not sure what to do from there.

[sumghai]

DChurchill, have you seen the following snippet Mu posted in this sticky topic?:

MODEL Nodes

In the old system, models were loaded directly from a part config's directory. This is still the case however can be overridden using MODEL config nodes.

MODEL nodes can be used to compile parts containing scaled, translated or rotated models. You can define multiple MODEL nodes to compile multiple models into one part. It also allows you to overload textures on the model.

Parts, Props and InternalSpaces can all use MODEL nodes instead of the traditional same-driectory loading system.

Here is a sample MODEL node showing all valid values

MODEL
{
   model = Squad/Parts/Command/cupola/model
   position = 0.25, 0.5, 1.0
   scale = 2.0, 2.0, 4.0
   rotation = 0, 90, 0
   parent = anotherModelTransform
   texture = model000 , Squad/Parts/Command/landerCabinSmall/model000
   texture = oldTextureName , newTextureURL
}

Just add the "rotation = " arugment and play around with the values. It's not that hard.

[DChurchill]

Hadn't seen that. Thanks. I'll give it a shot.

Edit: got it, thanks. Now for textures.

Edited August 27, 2013 by DChurchill