Skip to content
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

manoeuvre node auto move while warping #2154

Closed
LuctenFinger opened this issue May 6, 2019 · 3 comments · Fixed by #2166
Closed

manoeuvre node auto move while warping #2154

LuctenFinger opened this issue May 6, 2019 · 3 comments · Fixed by #2166
Labels
Milestone

Comments

@LuctenFinger
Copy link

as the title

@pleroy
Copy link
Member

pleroy commented May 7, 2019

The title is rather cryptic, but I am assuming that you are talking about the manoeuvre node shown on the navball. If so, it is working as it should: the direction of the manoeuvre is defined based on the Frenet trihedron at the time of the burn, and that's not fixed with respect to your vessel as you advance along your trajectory (your trajectory is typically not a straight line).

If you mean something else you'll have to provide details.

Sorry, something went wrong.

@ghost
Copy link

ghost commented May 10, 2019

I guess what he means is this... The UT of manoeuvre keeps increasing
https://www.youtube.com/watch?v=RKPf_BKI6LQ

Sorry, something went wrong.

@eggrobin
Copy link
Member

@miraclemagician

The UT of manoeuvre keeps increasing

Oh, this is bad.

This is happening because, since Fáry, we take the start of the flight plan as a time base for the manoeuvres, but that keeps increasing if the past flight plan gets cut off by forgetting the history.

For now, as a workaround, set the history length to something long; the issue will only occur if the history gets cut off after the beginning of the flight plan.

Sorry, something went wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants