Manuever burn delta V off by factor of 2

[NathanKell]

Using RO and Ven's Stock Revamp Skipper configured as RL-10A-1, it appears that RemoteTech flight computer decreases the "delta V remaining" counter twice as fast; when I tell it to burn 1000m/s it burns 500 (but shows the countdown 1000->500).
Note that I have expended solids in my stage (ullage), is it possible it is including their thrust and assuming it counts in (they provide roughly the same thrust as my RL-10).

If that is the case, do check if an engine has fuel before decrementing delta-V remaining by its thrust...

[pjf]

I don't know if I've encountered this or not. I had RO cut out after 7m/s into a 30m/s burn. I have expended solids, but not in the current stage (they're all in stage 1, which I never activate; it's reserved for action groups). However if the stage 1 engines or any active but exhausted engines are countered towards the thrust total, then that would explain the behaviour I've seen.

Images immediately before and after the burn: before, after.

[Peppie84]

Hi,
i can reproduce this bug with the O-10 monoprop engines and a fresh copie of ksp (0.90,0.25).

• Download the test Vessel Test-Vessel
• activate infinite rsc/fuel
• make a orbit
• add a new maneuver and execute via flightcomputer

[pjf]

@Peppie23 : Hmm, looking at your craft file it's just using the monoprop engines, there's no engines with expended fuel or anything else, is there? That would seem to discount the "RemoteTech thinks there's more thrust than really exists" theory.

Delighted it can be reproduced with a simpler set-up than my own, my mod stack can be imposingly large. :)

[tgharold]

My suspicion is that Remote Tech's Flight Computer does not deal well with the case of burning off a large fraction of your mass. For instance, I have a satellite which is about 90% fuel mass and I need to burn off 1/4 of that in a single maneuver node with an engine of only 0.25 TWR. Initial acceleration of the vessel starts at around 1.3 m/s/s, and gradually increases to 2.0 m/s/s through the 20 minute burn.

The Flight Computer correctly calculates that it is a 20 minute burn, but instead of using the API information it seems to do its own calculation. As a result, on long burns of > 10 minutes, I have to finish up the burn by myself because the FC only performed about 80-90% of it.

[Peppie84]

Hi,

i think we have two issues here:

1. NathanKell's reported issue
2. Not accurate executed maneuvers

I would like to treat NathanKell's issue here on this thread and open a new thread for the not accurate maneuvers.

@NathanKell Can you please try to reproduce your issue with this dll (please backup your current): https://www.dropbox.com/s/41th5tpjpmuatbx/RemoteTech%23243_debug_dll_only.zip?dl=0

But you are right. We loop through all ModuleEngines and ModuleEnginesFX parts and we calculate the thrust if they only be ignited. So i changed the condition to check the required propellant and also if an engine is flamed out.

[NathanKell]

@Peppie23 sure. .25 or .90? I will use just RT+FAR and test with the current head and with your dll. That make sense?

[Peppie84]

Yea thats ok. Please use .90

[NathanKell]

Roger.

[Peppie84]

Merged into 1.6