Engines Deactivate After Being Decoupled

[Davidian1024]

It seems that sections that are being decoupled have their engines disabled immediately.  Even if they still have plenty of fuel.

Sometimes I want them to keep running.  Is this expected behavior?  It doesn't seem right to me.

[EvelynThe Dragon]

1 hour ago, Davidian1024 said:

It seems that sections that are being decoupled have their engines disabled immediately.  Even if they still have plenty of fuel.

Sometimes I want them to keep running.  Is this expected behavior?  It doesn't seem right to me.

I am uncertain what you mean by this. Can you explain further? Which engines? On which part of the craft?

[Davidian1024]

I think I may have figured out what's going on.  I've only seen it happen with methalox engines, but I think it's any engine with a throttle.  If you decouple a section with an engine while that engine is running, the ending seems to turn off.  So for example, a methalox based booster.

I attached a probe core to one of these sections and before decoupling I switched control to that probe core.  What seems to happen is the throttle gets set to zero at the moment of decoupling.

If I set that part to have an independent throttle I can get it to keep running the engine after decoupling.

[JoeSchmuckatelli]

On 4/21/2023 at 7:19 PM, EvelynThe Dragon said:

I am uncertain what you mean by this. Can you explain further? Which engines? On which part of the craft?

Two problems in one; Every separation the engine shuts down - and every separation turns off the probe.

It's just like when undocking and the ship you switch from (that you left in SAS lock, or something) is now drifting uncontolled.