Jump to content

Unsure how to make a rocket engine that can gimbal.


Recommended Posts

So I recently got started making parts for KSP, and I have a question on how gimbal is set up, so that I can add it to the engines that I make. First of all, how does gimbal work for the stock parts? I've tried adding my nozzle model to the thustTranform in unity, adding it sperately under the thrustTransform, having my nozzle be the thrustTransform, and keeping it under the model it originally was attached to, but all to no avail. With each of these models, I've tried to mimic referencing the nozzle in the part.cfg file the same way that the game does it, but I have had no luck. Hopefully somebody on the forums can help me with this, or tell me 'm just being stupid. Also, i'm happy to send screenshots or give more information as to my problem if that is required.

Link to comment
Share on other sites

Gimbal is ranged in the part config (how far the engine gimbals) but to actually make the nozzle move if you are turning the rocket, the nozzle mesh should be under the thrustTransform and it should be pointed to the correct direction (was it the blue one on unity, iirc, it is). The center of the thrustTransform is where the nozzle will gimbal and where the plume go off.

PS: It's spelled Jebediah :)

Link to comment
Share on other sites

The nozzle mesh is listed under the thrustTransform and both are set up in a way that should work, however they do not. I am fairly certain that this is a problem with the part.cfg not referencing the nozzle correctly. What I want to know is if in Unity, if the nozzle is listed in this way, is it supposed to work? If not, then what do I need to do?

Link to comment
Share on other sites

You're not actually calling ModuleGimbal, you have name = nozzle in the config, so replace the

MODULE

{

name = nozzle

gimbaltranformname = thrustTransform

gimbalrange = 0.5

}

with

MODULE

{

name = ModuleGimbal

gimbalTransformName = thrustTransform

gimbalRange = 0.5

}

Link to comment
Share on other sites

Nope, the name = argument specifies the name of the module{} you are calling

For example, even in your own .cfg a bit earlier you have

MODULE

{

name = ModuleEngines

etc

}

For ModuleGimbal it only needs to know the name of the transform to wiggle around, then all the child parts of that transform (in this case the nozzle mesh) are, well, wiggled.

Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...