ferram4 changed the topic of #RO to: Welcome to the discussion channel for the Realism Overhaul (meta)mod for KSP! Realism Overhaul Main Thread https://goo.gl/wH7Dzb ! RO Spreadsheet http://goo.gl/Oem3g0 ! Code of Conduct http://goo.gl/wOSv2M ! | Maximal & soundnfury's RP-1 Race Into Space Signup: http://bit.ly/2DEVm2i [15:01] <soundnfury> Straight Eight Stronk (and) RP-0/1 is basically "Space Agency Spreadsheet Simulator"
SirKeplan has quit [Quit: Konversation terminated!]
SirKeplan has joined #RO
SirKeplan has quit [Quit: Konversation terminated!]
SirKeplan has joined #RO
_whitelogger has joined #RO
SirKeplan has quit [Ping timeout: 190 seconds]
SirKeplan has joined #RO
egg|zz|egg has quit [Ping timeout: 190 seconds]
ProjectThoth has joined #RO
_whitelogger has joined #RO
SirKeplan has quit [Ping timeout: 200 seconds]
Addle has quit [Ping timeout: 200 seconds]
Addle has joined #RO
_whitelogger has joined #RO
Mike` has quit [Ping timeout: 190 seconds]
Mike` has joined #RO
ProjectThoth has quit [Quit: +++out of cheese error+++]
Bornholio has quit [Read error: Connection reset by peer]
Bornholio has joined #RO
Senshi has joined #RO
BasharMilesTeg has joined #RO
oeuf has joined #RO
BasharMilesTeg_ has quit [Ping timeout: 202 seconds]
egg has quit [Ping timeout: 202 seconds]
Shoe18 has quit [Quit: Connection closed for inactivity]
Senshi has quit [Read error: Connection reset by peer]
xShadowx|2 has quit [Ping timeout: 190 seconds]
schnobs has quit [Ping timeout: 200 seconds]
egg|zz|egg has joined #RO
<Starwaster>
wow, Kerbals-on-ladders seems pretty solid now... I have one of the round pods rolling around on the ground with a Kerbal klinging to the outside and it's pretty stable
<Starwaster>
even with phys timewarp
ferram4_ has joined #RO
ferram4 has quit [Ping timeout: 190 seconds]
egg|zz|egg has quit [Ping timeout: 190 seconds]
egg|zz|egg has joined #RO
<github>
[RealismOverhaul] raidernick opened pull request #1938: RN fix titan iv dec mass (master...master) https://git.io/fxFLB
<Mike`>
does anybody know why the AJ10-104 (ablestar engine) has such a bad testflight-reliability? Its ignition-reliability is 6 times as bad as its "predecessor", the AJ10-142
<soundnfury>
Mike`: maybe that number dates back to before an ignition failure ate all your ignitions
<Mike`>
ah, so that was different back then. it's from feb 2016.
<Mike`>
but that would make sense i guess.
<soundnfury>
(I'm personally of the opinion that that was a BAD tf change)
<soundnfury>
(but no-one listens to me)
<Mike`>
:D
<Bornholio>
because real life, cite it and you are good
<Mike`>
no idea, i guess it's realistic though, because if it just doesn't ignite on first try, you would immediately try it again, and if it does ignite, i guess that incident wouldn't even make it to the public as a failure?
<soundnfury>
Mike`: when SpaceX have had ignition failures / T-0 shutdowns on the pad, they haven't always recycled immediately
<soundnfury>
same goes for RocketLab
<Mike`>
oh sure, on the pad that's different i guess, because you have time to do stuff, but on an upper stage you can't just wait and inspect stuff, you have to get the thing going. :)
<soundnfury>
Admittedly it might've been different in the Sixties when they didn't have nearly so much telemetry and computer monitoring etc
<Mike`>
Bornholio, in case that was an answer to my question, i chgecked the wikipedia launch list and only saw one ignition failure out of 15 flights, plus at least one of those contained a restart
<Mike`>
the exact number of restarts would be nice
<Mike`>
in any case, that data would lead to a better reliability
<Mike`>
soundnfury, do you know by chance when this TF change was made? i guess i could just check the TF release notes or source history though
* soundnfury
shrugs
<soundnfury>
ISTR it was after I changed RF engines to always allow ignition when attached to launch clamps (which was intended to make parallel staging more justified)
<soundnfury>
(i.e. if your LR105 failed to ignite, you could just recycle the launch. Now you can't; thanks, TF.)
<Mike`>
i found this from march 2016: "ShutdownEngine failure now also removes all ignitions from the engine. They are restored is the failure is repaired."
<soundnfury>
yeah but repair in TF is broken :P
<Mike`>
repair was removed later if i read that correctly
<soundnfury>
anyway, what _now_ happens is that it disables the "Activate Engine" KSPAction
<soundnfury>
(though you can still fire it through action groups ;)
<Mike`>
hehe
darsie has joined #RO
Bornholio has quit [Read error: Connection reset by peer]