RCS Propellant bug, did anyone ever fixed it?

[IGNOBIL]

In real life there are RCS systems that use bipropellant, the shuttle used so.

The Vernor engine uses it, but only works with one thruster, basically, I'm doing a 5 point RCS and can't put it working on bipropellant.

Ive read the RCS tutorial, I've got it working pretty fine on monopropellant or oxidiser, but thats not what I'm aiming for, is there any workaround on this?

Cheers

The config as is just with oxidiser:

PART

{

name = NAU_RCS

module = Part

author = IGNOBIL

mesh = Model.mu

scale = 1

node_attach = 0.0, 0.0, 0.0, 1, 0, 0.0, 1

// --- editor parameters ---

TechRequired = specializedControl

entryCost = 4200

cost = 1400

category = Control

subcategory = 0

title = NAU LFO RCS

manufacturer = NAU Aerospace

description = The NAU LFO RCS. These motors are linked to RCS controls, but are powered by a Fuel+Oxidizer mix, making them significantly more powerful than MonoPropellant-powered RCS thrusters.

// attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollision

attachRules = 0,1,0,1,1

// --- standard part parameters ---

mass = 0.02

dragModelType = default

maximum_drag = 0.01

minimum_drag = 0.01

angularDrag = 0.1

crashTolerance = 50

breakingForce = 50

breakingTorque = 50

maxTemp = 3400

fuelCrossFeed = True

PhysicsSignificance = 1

// --- rcs module parameters ---

MODULE

{

name = ModuleRCS

thrusterTransformName = RCSthruster

thrusterPower = 2

resourceName = Oxidizer

resourceFlowMode = STAGE_PRIORITY_FLOW

atmosphereCurve

{

key = 0 230

key = 1 260

}

}

Edited February 1, 2015 by IGNOBIL

[FreeThinker]

aren't there already several mods that allow bipropellant RCS, even allowing multiple types of propellants?

[IGNOBIL]

I remember having one, but can't seem to find it anymore, don't know on which pack it was.

Thats why I made my own!

[undercoveryankee]

The ModuleRCSFX plugin (http://forum.kerbalspaceprogram.com/threads/92290-0-90-ModuleRCSFX-v3-5-19-Jan-15 ) is the most mature way to do RCS configurations that have bugs in stock.

[Core21]

from the vernor engine cfg:

MODULE

{

name = ModuleRCS

thrusterTransformName = RCSthruster

thrusterPower = 12

resourceName = LiquidFuel

resourceFlowMode = STAGE_PRIORITY_FLOW

PROPELLANT

{

name = LiquidFuel

ratio = 0.9

DrawGauge = True

resourceFlowMode = STAGE_PRIORITY_FLOW

}

PROPELLANT

{

name = Oxidizer

ratio = 1.1

resourceFlowMode = STAGE_PRIORITY_FLOW

}

atmosphereCurve

{

key = 0 260

key = 1 140

}

}

As you can see there are two PROPELLANT nodes that are missing in your config.

Maybe that is the problem.

[IGNOBIL]

from the vernor engine cfg:

MODULE

{

name = ModuleRCS

thrusterTransformName = RCSthruster

thrusterPower = 12

resourceName = LiquidFuel

resourceFlowMode = STAGE_PRIORITY_FLOW

PROPELLANT

{

name = LiquidFuel

ratio = 0.9

DrawGauge = True

resourceFlowMode = STAGE_PRIORITY_FLOW

}

PROPELLANT

{

name = Oxidizer

ratio = 1.1

resourceFlowMode = STAGE_PRIORITY_FLOW

}

atmosphereCurve

{

key = 0 260

key = 1 140

}

}

As you can see there are two PROPELLANT nodes that are missing in your config.

Maybe that is the problem.

Yes that was my first approach, but it only works with one thruster, if you have multiple only one of them will work... weird, it's only the last in unity, but if you use that with another at same time both work...

[kujuman]

Yes that was my first approach, but it only works with one thruster, if you have multiple only one of them will work... weird, it's only the last in unity, but if you use that with another at same time both work...

The Teflon bar RCS prototype included in the newest boxsat pack is a bipropellant http://forum.kerbalspaceprogram.com/threads/91616

It has three thrusters on each block, and each thruster will fire...mostly. On the only orbital test of them I've done so far they sometimes are not responsive at all, though this may be because I'm playing with RT2 and all sorts of other things. When the block works at all, all the thrusters on it work.

[PDCWolf]

Multi-propellant RCS configs don't work for stuff that has more than one thrust point (that's why you can for example convert the linear rcs to linear ion rcs but not the 4 way rcs block)

[Starwaster]

There is a definite bug with the FX in the RCS module that is visual only. The bug is that RCS thruster effects don't always appear when they should. So make sure that the problem that you are seeing is not just a graphical issue.

Instead of a ground test, put it in orbit and turn off reaction wheels. Then use RCS to translate. Make sure that RCS is properly balanced so as not to invalidate the test. If RCS really doesn't fire properly then you'll rotate instead of translate. (which is why the test requires balanced RCS)

If you run into a situation where RCS isn't firing then verify your propellant names are correct and properly spelled. I've had no problems setting up multiport RCS with multiple bi-propellant configurations.

[IGNOBIL]

Multi-propellant RCS configs don't work for stuff that has more than one thrust point (that's why you can for example convert the linear rcs to linear ion rcs but not the 4 way rcs block)

Thanks, I'll download and check the code.

Starwaster, it's not visual. I've checked

[NathanKell]

Starwaster, it's not visual only. I confirmed it in .24.2 and it's sat unfixed since. It sucks fuel but doesn't apply thrust at the transform (or show FX) other than one direction. This is one of the bugs ModuleRCSFX was (re)built to fix.

[IGNOBIL]

Yeah, been there done that, moduleRCS fix didn't cut it