-
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
Suicide burn seems to only take vertical speed into account, not horizontal #39
Comments
Non-vertical suicide burns are much more complex calculations to consider. See this reddit thread for some discussion on the matter. |
That's essentially what I thought. I guess my issue is that it is marked as generic suicide burn information, not explicitly vertical. I slammed into the Mün twice before I figured it out. (Not that I mind killing my horizontal velocity before the suicide burn, I've grown accustomed to burning retrograde at a low periapsis beforehand, it just took me a bit to realise that the KER data was poorly labeled.) |
I've edited my copy of KER to use the following calculation:
With that plan, it's easy to calculate your desired suicide burn height. (much easier than solving the full differential equation) Note that it will always overestimate the desired height, so there's an automatic safety margin built in. Also notice that (unmodded) KER gives you an incorrect value for horizontal velocity. (it calls the correct function, but KSP returns the wrong number) I've changed that to sqrt((surface speed)^2 - (vertical velocity)^2) in my copy. |
That's a fairly reasonable way to do it... and I always wondered about the horizontal velocity part. I mean, it should change a little due to the fact that the planet(oid) is not a flat plane--so the reference "horizontal" plane changes as you move over/around it--but it changed a lot more than that, which was super noticeable when you were doing a near-vertical descent. |
I don't have any screen shots at present, but I'll gladly take some as this has bit me in the ass before.
The text was updated successfully, but these errors were encountered: