How do I add gimballing to a rocket engine in KSP (specifically in 1.2.2 with RSS, RO, and RP-0)?

[Grant Exploit]

I have been messing with the Engine config files in my copy of KSP 1.2.2 with Real Solar System, Realism Overhaul, and Realistic Progression Zero mods installed, mostly to create fictional engines or engines that do not exist in currently available mods. However, I have not been able to add gimballing to an engine that previously had none. For example, I attempted to add gimbal to the RS-88 engine for an orbital launch vehicle using that to power its first stage and an AJ10 to power its second stage, but even after ~8 attempts at adding and modifying the ModuleGimbal, it still didn't work. What am I doing wrong?

Here's the RS-88 code at the final attempt: RS88_Config.cfg - Google Drive

[Mecripp]

30 minutes ago, Grant Exploit said:

I have been messing with the Engine config files in my copy of KSP 1.2.2 with Real Solar System, Realism Overhaul, and Realistic Progression Zero mods installed, mostly to create fictional engines or engines that do not exist in currently available mods. However, I have not been able to add gimballing to an engine that previously had none. For example, I attempted to add gimbal to the RS-88 engine for an orbital launch vehicle using that to power its first stage and an AJ10 to power its second stage, but even after ~8 attempts at adding and modifying the ModuleGimbal, it still didn't work. What am I doing wrong?

Here's the RS-88 code at the final attempt: RS88_Config.cfg - Google Drive

You just add 

	MODULE
	{
		name = ModuleGimbal
		gimbalTransformName = ******* //<----- The name of what you want to gimbal this can be the thrusttransformer or the bell
		gimbalRange = *  //<---  and range 1 throught 5 lets say
	}

and you could have just copied what ever you posted in the thread if some one dont have a google account its asking for stuff hope it helps

[Grant Exploit]

On ‎10‎/‎21‎/‎2017 at 9:05 PM, Mecripp said:

You just add 

	MODULE
	{
		name = ModuleGimbal
		gimbalTransformName = ******* //<----- The name of what you want to gimbal this can be the thrusttransformer or the bell
		gimbalRange = *  //<---  and range 1 throught 5 lets say
	}

and you could have just copied what ever you posted in the thread if some one dont have a google account its asking for stuff hope it helps

To be clear, this is my current version after I saw your comment: 

Quote

//  ==================================================
//  RS-88 global engine configuration.

//  Inert Mass: 250 Kg
//  Throttle Range: N/A
//  Burn Time: -
//  O/F Ratio: 1.29 (Ethanol version), 1.65 (Hypergolic version)

//  Sources:
//      NTRS - RS-88 Pad Abort Demonstrator Thrust Chamber Assembly:                http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20050237017.pdf
//      Encyclopedia Astronautica - RS-88 engine:                                   http://astronautix.com/r/rs-88.html
//      Boeing - Design Considerations for a Commercial Crew Transportation System: http://www.boeing.com/assets/pdf/defense-space/space/ccts/docs/Space_2011_Boeing.pdf

//  Used by:
//      CST-100 pack
//      RLA

//  FIXME:
//      No sources for some values (inert mass, rated burn time and ignition count).
//  ==================================================

@PART[*]:HAS[#engineType[RS88]]:FOR[RealismOverhaulEngines]
{
    %category = Engine
    %title = RS-88 Series
    %manufacturer = Rocketdyne
    %description = High thrust pressure-fed hypergolic engine. Initially designed and built as a part of the NASA Bantam System Technology program, aiming for a low cost, high power propulsion system. It was later modified by Lockheed Martin for use as a launch abort engine. A derivative of the RS-88 is used by the Boeing CST-100 "Starliner" spacecraft for launch aborts under the name "Launch Abort Engine - LAE". Diameter: [1.9 m].

    @MODULE[ModuleEngines*]
    {
        %EngineType = LiquidFuel

        !IGNITOR_RESOURCE,*{}
    }

    !MODULE[ModuleGimbal],*{}

 MODULE
 {
  name = ModuleGimbal
  gimbalTransformName = bell
  gimbalRange = 4.25
  useGimbalResponseSpeed = true
  gimbalResponseSpeed = 16
 }

    !MODULE[ModuleEngineConfigs],*{}

    MODULE
    {
        name = ModuleEngineConfigs
        type = ModuleEngines
        configuration = RS-88
        modded = False
        origMass = 0.25

        CONFIG
        {
            name = RS-88
            maxThrust = 220
            minThrust = 220
            ullage = True
            pressureFed = True
            ignitions = 1

            IGNITOR_RESOURCE
            {
                name = ElectricCharge
                amount = 0.1
            }

            PROPELLANT
            {
                name = Ethanol75
                ratio = 0.5285
                DrawGauge = True
            }

            PROPELLANT
            {
                name = LqdOxygen
                ratio = 0.4715
                DrawGauge = False
            }

            atmosphereCurve
            {
                key = 0 324
                key = 1 273
            }
        }

        CONFIG
        {
            name = LAE
            minThrust = 258
            maxThrust = 258
            heatProduction = 0.88 //0.220
            ullage = True
            pressureFed = True
            ignitions = 1

            IGNITOR_RESOURCE
            {
                name = ElectricCharge
                amount = 0.1
            }

            PROPELLANT
            {
                name = MMH
                ratio = 0.499
                DrawGauge = True
            }

            PROPELLANT
            {
                name = MON3
                ratio = 0.501
                DrawGauge = False
            }

            atmosphereCurve
            {
                key = 0 290
                key = 1 220
            }
        }
    }

    !MODULE[ModuleAlternator],*{}

    !RESOURCE,*{}
}

For the first time, the gimbal box actually shows up in the Part window, but it still seems to have no or negligible gimbal on ascent (there may have been a tiny bit of eastward shift right before it lunged west and spun out of control). Could it be something to do with the gimbalTransformName such as it not corresponding with a model? Faulty positioning? The things related to gimbal response time I added from other configs? Other things?

[JadeOfMaar]

gimbalResponseSpeed is optional and how long in seconds it takes to respond to control input. 16 seconds is far too long. Might as well not have gimbal.

[Mecripp]

15 hours ago, Grant Exploit said:

To be clear, this is my current version after I saw your comment: 

For the first time, the gimbal box actually shows up in the Part window, but it still seems to have no or negligible gimbal on ascent (there may have been a tiny bit of eastward shift right before it lunged west and spun out of control). Could it be something to do with the gimbalTransformName such as it not corresponding with a model? Faulty positioning? The things related to gimbal response time I added from other configs? Other things?

Looking at that model you might try and change 

 

15 hours ago, Grant Exploit said:

gimbalTransformName = bell

to gimbaltransformName = RS88

and much like JadeOfMaar pointed out you might lower it to your like

EDIT- and here you can get a handing little plugin to get some of the names you might need 

 

Edited October 24, 2017 by Mecripp

[Grant Exploit]

SUXESSSZ!!@ Thanks, @JadeOfMaar and @Mecripp!

Here's the final code: 

//  ==================================================
//  RS-88 global engine configuration.

//  Inert Mass: 250 Kg
//  Throttle Range: N/A
//  Burn Time: -
//  O/F Ratio: 1.29 (Ethanol version), 1.65 (Hypergolic version)

//  Sources:
//      NTRS - RS-88 Pad Abort Demonstrator Thrust Chamber Assembly:                http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/20050237017.pdf
//      Encyclopedia Astronautica - RS-88 engine:                                   http://astronautix.com/r/rs-88.html
//      Boeing - Design Considerations for a Commercial Crew Transportation System: http://www.boeing.com/assets/pdf/defense-space/space/ccts/docs/Space_2011_Boeing.pdf

//  Used by:
//      CST-100 pack
//      RLA

//  FIXME:
//      No sources for some values (inert mass, rated burn time and ignition count).
//  ==================================================

@PART[*]:HAS[#engineType[RS88]]:FOR[RealismOverhaulEngines]
{
    %category = Engine
    %title = RS-88 Series
    %manufacturer = Rocketdyne
    %description = High thrust pressure-fed hypergolic engine. Initially designed and built as a part of the NASA Bantam System Technology program, aiming for a low cost, high power propulsion system. It was later modified by Lockheed Martin for use as a launch abort engine. A derivative of the RS-88 is used by the Boeing CST-100 "Starliner" spacecraft for launch aborts under the name "Launch Abort Engine - LAE". Diameter: [1.9 m].

    @MODULE[ModuleEngines*]
    {
        %EngineType = LiquidFuel

        !IGNITOR_RESOURCE,*{}
    }

    !MODULE[ModuleGimbal],*{}

	MODULE
	{
		name = ModuleGimbal
		gimbalTransformName = thrustTransform
		gimbalRange = 4.25
	}

    !MODULE[ModuleEngineConfigs],*{}

    MODULE
    {
        name = ModuleEngineConfigs
        type = ModuleEngines
        configuration = RS-88
        modded = False
        origMass = 0.25

        CONFIG
        {
            name = RS-88
            maxThrust = 220
            minThrust = 220
            ullage = True
            pressureFed = True
            ignitions = 1

            IGNITOR_RESOURCE
            {
                name = ElectricCharge
                amount = 0.1
            }

            PROPELLANT
            {
                name = Ethanol75
                ratio = 0.5285
                DrawGauge = True
            }

            PROPELLANT
            {
                name = LqdOxygen
                ratio = 0.4715
                DrawGauge = False
            }

            atmosphereCurve
            {
                key = 0 324
                key = 1 273
            }
        }

        CONFIG
        {
            name = LAE
            minThrust = 258
            maxThrust = 258
            heatProduction = 0.88 //0.220
            ullage = True
            pressureFed = True
            ignitions = 1

            IGNITOR_RESOURCE
            {
                name = ElectricCharge
                amount = 0.1
            }

            PROPELLANT
            {
                name = MMH
                ratio = 0.499
                DrawGauge = True
            }

            PROPELLANT
            {
                name = MON3
                ratio = 0.501
                DrawGauge = False
            }

            atmosphereCurve
            {
                key = 0 290
                key = 1 220
            }
        }
    }

    !MODULE[ModuleAlternator],*{}

    !RESOURCE,*{}
}

Unfortunately, my LV design turned out to be aerodynamically unsound. Woo... Hoo... 

[USB4]

On 10/24/2017 at 2:43 PM, Mecripp said:

Looking at that model you might try and change 

 

to gimbaltransformName = RS88

and much like JadeOfMaar pointed out you might lower it to your like

EDIT- and here you can get a handing little plugin to get some of the names you might need 

 

In unity, would the gimbaltransformName= RS88 be an actual object in the model?

[Mecripp]

2 hours ago, USB4 said:

In unity, would the gimbaltransformName= RS88 be an actual object in the model?

You don't set the gimbaltransform in unity has far as I know you just pick a part of the model like what ever there calling the bell or use thrustTransform I guess you could set one in unity just don't know why if you don't have to you just need the name of the part you want to gimbal 

And looking at that model RS88 think was the name there using for the bell so the bell should gimbal and the thrusttransform is tied to the bell