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
This stat seems like it should be really useful for predicting SOI changes, but as far as I can tell the number it returns is always too high - sometimes by quite a lot.
To demonstrate: manually set up an encounter with the Mun, then run the following command in the KOS terminal:
add node(time:seconds + ETA:transition, 0, 0, 0).
Go to map view and focus on the Mun. Compare the ETA reported by the stock UI for the encounter to that of the new maneuver node, and you will see that they do not match as they should.
When I tried this a second ago, the node was placed about 5 minutes after the actual transition; that is the closest I have seen it. Earlier tests averaged a separation of more like 20 minutes, but sometimes it is off by hours.
The text was updated successfully, but these errors were encountered:
This stat seems like it should be really useful for predicting SOI changes, but as far as I can tell the number it returns is always too high - sometimes by quite a lot.
To demonstrate: manually set up an encounter with the Mun, then run the following command in the KOS terminal:
Go to map view and focus on the Mun. Compare the ETA reported by the stock UI for the encounter to that of the new maneuver node, and you will see that they do not match as they should.
When I tried this a second ago, the node was placed about 5 minutes after the actual transition; that is the closest I have seen it. Earlier tests averaged a separation of more like 20 minutes, but sometimes it is off by hours.
The text was updated successfully, but these errors were encountered: