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

Switching between vessels does not update maneuver node. #1565

Closed
Thomas-P opened this issue Sep 17, 2017 · 3 comments · Fixed by #2136
Closed

Switching between vessels does not update maneuver node. #1565

Thomas-P opened this issue Sep 17, 2017 · 3 comments · Fixed by #2136
Assignees
Labels

Comments

@Thomas-P
Copy link

When I switch from one vessel to another, with an active maneuver plan, the node for this maneuver isn't the one that is planned next. I have to reactivate the show maneuver in navball checkbox to update the maneuver into the right direction.

@scimas
Copy link
Contributor

scimas commented Nov 5, 2017

Just wanted to add that the manoeuvre node is also sometimes not updated (deleted) if you delete a flight plan before executing any of the nodes in it.

@scimas
Copy link
Contributor

scimas commented Dec 17, 2017

There is another related bug to this (or maybe they have a common cause). Manoeuvre node isn't updated by principia if flight plan window is not open (even if show on navball was selected before closing the window).
Not sure whether it needs a separate issue of its own.

@pleroy
Copy link
Member

pleroy commented Apr 13, 2019

Note to self: I was in this code recently and restructured it a bit in #2131. The root of the problem is that the (new) method FlightPlanner.ShowGuidance is only called when rendering the flight plan window so if that window is hidden, or the flight plan is deleted, or a different vessel is selected, the guidance node is likely to be left alone until someone clicks "Show on navball" again.

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.

4 participants