-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Rendezvous readout for Time-to-launch #108
Comments
+1. I support this. I really miss this feature. Now I have to use my eye to find out when to launch. |
I would appreciate this too. However generally the new release has On Thu, 20 Oct 2016, 18:54 Péter Szabados, [email protected] wrote:
|
I've noticed since posting this that Kerbal Alarm Clock has such a feature, and given its MIT license there should be no problem integrating the code. The code is in MechJebAscentAutopilot.cs which suggest that it was originally lifted from MechJeb... |
I've added this and it's amazing. I tried getting my head around a way to distinguish 'ascending' (northward) or 'descending' (southward) launches but I'm just not familiar enough with KSP's frames of reference and calculations available to come up with a solution to that in a reasonable amount of time. So when landed and targeting something within the same SOI the time to AN/DN will be replaced with the same time. It looks like "(Launch) 2h 41m 00s" . |
I made some adjustments, the AN readout will always be the next intercept and the DN readout the one after that. The AN readout will go negative up to 1/4 rotation period since it's nicer to know the intercept was 3 minutes ago instead of 2hrs 57 minutes from now. |
For landed (or splashed) vessels, it would be nice to have a readout in the "rendezvous" category that shows when the planet will have rotated so that the vessel is under the target orbit, i.e. when we can launch directly into the target orbit.
Either:
Maybe the new readout could be "Time to Intersect", showing time to launch when landed and time to nearest AN/DN otherwise.
The text was updated successfully, but these errors were encountered: