Page 1 of 1

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

Posted: Tue Nov 05, 2024 8:44 pm
by 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.

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

Posted: Tue Nov 05, 2024 8:50 pm
by mmmPI
cellularmitosis wrote: Tue Nov 05, 2024 8:44 pm [*]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

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

Posted: Fri Nov 15, 2024 3:27 pm
by 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.