You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After talking with @b14ckyy about the matter of fixedwing auto landing and wind speed effecting the landing position. I was thinking it would be helpful to have the estimated wind direction and estimated wind speed added as flight parameters to the programming tab.
Who does this impact? Who is this for?
I believe this would help people to perhaps find a work-around to the aforementioned issue using the programming tab. Until a proper fix can be implemented at a later date.
Thanks for your consideration.
The text was updated successfully, but these errors were encountered:
I had an idea of using the estimated wind speed and direction, if applicable to the approach heading; to drive timer based throttle or elevator override conditions. To either push the nose down a little at select distances from the landing location. And add or subtract a small amount of throttle, based on the headwind and current altitude at a given position on the approach. Being permitted by setting nav_override_motor_stop = off or off_always
Don't shoot me for a theory. It would require some testing to see if the idea has merit; and it may not work.
But considering wind speed and direction has such a strong influence on fixedwing flight. I thought the addition of these flight logic parameters would be useful.
Desired Behavior
After talking with @b14ckyy about the matter of fixedwing auto landing and wind speed effecting the landing position. I was thinking it would be helpful to have the
estimated wind direction
andestimated wind speed
added as flight parameters to the programming tab.Who does this impact? Who is this for?
I believe this would help people to perhaps find a work-around to the aforementioned issue using the programming tab. Until a proper fix can be implemented at a later date.
Thanks for your consideration.
The text was updated successfully, but these errors were encountered: