Replies: 2 comments
-
I'm not sure it's only 4.0.0 that behaves strangely. Prior to 1.x (x < 8), tracking was perfect. Since then I've noticed acouple of things illustrated below:
I gave up worrying about such things in those ancient days. Missions always work, if not always elegantly. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@stronnag Thanks for confirming the issue. As you noted, WP6 on your video was a classic case of what I've observed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@breadoven @stronnag
Have either of you or anyone else experienced their models deviating to the left, as it approach's a waypoint?
I've noticed this effect with both MR and FW. Both models ran the same waypoint test mission I used with previous releases, that did not experience this effect.
Its most pronounced when the next waypoint happens to be a right turn. Because the model will veer to the left at the waypoint and then make the right turn, to head to the next waypoint.
I have
nav_mc_wp_slowdown = off
. This has always been is my preferred method.Unfortunately I don't have logs for these test missions. I only noticed the effect on three DVR play backs.
I did ponder that the models where experiencing a left crosswind. Causing the navigation control to hook the model at the last second, to make the waypoint, before the turn. But this didn't ring true on one mission, when the plane had a 150degree offset heading, two waypoints later, no more than 500m away.
Beta Was this translation helpful? Give feedback.
All reactions