Jump to content

Recommended Posts

Posted

hi there,

just found another bug, please have a look. (SID RID6C at eddf), latest navigraph cycle 1606.

Picture 1: Gap in LEGS page between SID (RID6C) and the nect waypoint ODAVU

Bildschirmfoto 2016-06-04 um 16.48.12.png

Picture 2: I intend to remove the gap, this is what the route now looks like

Bildschirmfoto 2016-06-04 um 16.48.17.png

hopw this helps

Posted

Hi and thanks for the report.

I think the weird route in pic 2 is caused by the plane not being able to make the second waypoint after the bypass. To cure this, try to put RIDSU right after ODAVU or reduce the speed at ODAVU.

This is a classical "double bypass" situation, where the FMS has a tough time. We will improve on this eventually. Just for grins: The real FMS will lock up on a "triple bypass" situation (where it can´t make three waypoints in a row), so you have to be careful with the way you code procedures or enter waypoints.

Cheers, Jan

 

  • 2 weeks later...
Posted (edited)
On June 5, 2016 at 2:35 AM, Litjan said:

The real FMS will lock up on a "triple bypass" situation

In theory, ours will handle any number of sequential bypass situations...I think the real FMS might be a memory limitation.    This is a known bug that, as Jan says, can be cleaned up with some route editing most of the time, but I still want to clean it up a bit.....its a challenging section of code in bypass situations and I need to address it slowly and carefully.  Interceptions after bypasses are the most complex code in the entire LNAV....but we'll get there.

-tkyler

Edited by tkyler
  • Upvote 2

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...