Another RP-1 issue: RP-1 suppresses ship:control:fore when manual RCS fore works. #2970
Labels
bug
Weird outcome is probably not what the mod programmer expected.
Comments
Dunbaratu
added
the
bug
|
I'm thinking we need a better approach to this whereby kOS reads the control locks and only excludes those that are locked. |
|
Is kOS the one causing the lockout here though? |
|
It is, yes. In the top of If any RP-1 control lock is set, kOS completely disables control. |
|
yes this is done by kOS #2546 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Arrrgh. When you don't have sufficient avionics, RP-1 allows pilot-input manual RCS fore and aft axis to still work (so you can fire an ullage-needing engine on a spin-stabalized probe), but RP-1 is suppressing kOS's set ship:control:fore to xxx. - only allowing actual manual keyboard or joystick input to fire RCS fore and aft. Mechjeb's annoying "RCS responds to throttle when main engines not active" is the supposed way around it but that's not right for using some other scripting system.
Thus I can't ullage my engine for ignition in my spin-stabalized first lunar orbit probe.
ship:control:foreis a get-only field that can't be set, and there is noship:control:foretrim, and there is noship:control:pilotforeto set.The text was updated successfully, but these errors were encountered: