You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The orbit analysis window provides long-term information about the current trajectory when it is periodic.
Knowing the properties of the next apoapsis and periapsis serves a different purpose, e.g., to quote @lpgagnon on discord,
<@lpgagnon> I want to know how close to the atmo I'm going to get in my flyby. I want to know how high I'll be before I start falling down during ascent. etc.
Note that we provide this information in map view already, in the map nodes.
In stock + MechJeb or KER, long-term and upcoming apsides are the same, so this information is available outside map view in the orbit info display.
<@lpgagnon> As @Kenira said, this is info we already get in map view; having it without having to switch is what this feature request boils down to
Since this information is already communicated to the C# side to populate the map nodes, this should only require a C# change.
The text was updated successfully, but these errors were encountered:
The orbit analysis window provides long-term information about the current trajectory when it is periodic.
Knowing the properties of the next apoapsis and periapsis serves a different purpose, e.g., to quote @lpgagnon on discord,
Note that we provide this information in map view already, in the map nodes.
In stock + MechJeb or KER, long-term and upcoming apsides are the same, so this information is available outside map view in the orbit info display.
Since this information is already communicated to the C# side to populate the map nodes, this should only require a C# change.
The text was updated successfully, but these errors were encountered: