[2.0.24] Train overview shows surface (platform) which cannot have trains

[eugenekay]

Screenshot 2024-12-07 121216.png (418.86 KiB) Viewed 133 times

The Train Overview GUI's surface selector dropdown defaults to the "Current Surface", which may not be capable of supporting Trains.
What did you do?
- Navigate to Remote View on any Space Platform
- Open the Train Overview ("O" button)
What happened?
- Empty train dialog, because the current surface has no / cannot have Trains
What did you expect to happen instead? It might be obvious to you, but do it anyway!
- Show the Trains for the nearest Planet (in this screenshot, Nauvis)
Does it happen always, once, or sometimes?
- Any time the Remote View is on a non-Train-able surface

This is 2 extra clicks in order to get to the Train screen, when not "on" or "viewing" a Planet. It should be possible to infer which planet is closest to the current Remote View (ie, platform is Orbiting or On-the-Way), and skip showing the "Platform"'s non-existent train network.

Assuming that a Mod is capable of adding Space Trains, it would then make sense for Platforms to appear in the drop down IF AND ONLY IF there are Trains on that surface.

This is the current behavior for Planet surfaces; eg in first the screenshot only Nauvis and Fulgora have Trains; Gleba and Vulcanus are correctly excluded.

Screenshot 2024-12-07 122419.png (839.52 KiB) Viewed 133 times

In this second screenshot (taken from Vulcanus) it shows Nauvis and Fulgora (because they have Trains); AND the current surface/default of Vulcanus (which does not currently; but it CAN have trains, unlike a Space Platform).

[Klonan]

Hi,

Thanks for the report,

I don't consider this a bug at this time,
For consistency sake, the train overview will always open at the current surface