[2.0.14] Platform hub "moving from / to" signals don't stop when you pause thrust

[cellularmitosis]

If you pause thrust while mid-journey between planets, the platform hub continues to emit the "moving from" and "moving to" signals, even though it is stopped.

The platform hub should not emit those signals when space travel is paused.

As far as I can tell, there is currently no way to detect "should the platform be moving? / should we fire the thrusters?" (or in my case, "should we produce fuel on-demand?").

Things I've tried:

• Using the "velocity" signal requires that you are already moving, which creates a chicken / egg problem if you only produce fuel on-demand.
• You can't use the "moving from" / "moving to" signals, because those fire even when you pause the ship (i.e. you'd produce fuel even when the ship is stopped).

Producing fuel on-demand is useful, because it allows folks to implement thruster metering (to get high efficiency) without having to use combinator clocks.

[mmmPI]

[*]Using the "velocity" signal requires that you are already moving, which creates a chicken / egg problem if you only produce fuel on-demand.

can you develop on this ?

to me it seems you are always moving anyway even if you pause thrust in the middle of flight due to the slow drifting of -10km or + 10kms ? i was able to use the Velocity signal to produce fuel on demand because of this

[boskid]

Thanks for the report however i am going to move this to Not a bug.

Primary reason why it works like that is to give details where on the space map the platform is currently on. I tried to do this by adding new signal type, a space connection so a single signal would be sufficient to say where platform is (either it would be a space connection to show on which connection platform is, or a space location to show on which endpoint a platform is) however this idea was rejected and i was told to do it this way by providing separate signals for both ends on the current space connection. Moving from/to signals are implemented in a way that they are consistent with icons on the progress bar under the minimap when looking at the space platform. Since they are showing space platform as being on the connection, the signals are also sent.

[Ansible32]

Are you going to add a new signal? If the current signals are the only signals available, I think I would prefer that when the platform triggers traveling to a new planet, "moving from/going to" update regardless of whether or not the platform is moving. (We can use velocity for that.)

Although a new signal that signals where the platform intends to move would probably be ideal. (So we would have moving to, moving from, and maybe "directed to" or something like "set heading" "heading" or "heading to."

[Muche]

These ideas/suggestions seem relevant: Space platforms: output "moving to" signal even with zero thrust, Space Platform Control/Speed QOL Improvements, Signal Monitoring of thruster fuel levels and Platform hub paused state, Read distance from/to planets from the space platform hub.