Remaining airway bug

Hello Team, I already wrote a post about the bug I noticed on the airways, it
is here: https://devsupport.flightsimulator.com/t/3882 Today, I found
another bug that is related, probably the same reason, and I can explain an
easy way to reproduce it. I was trying to set a route from FLM to MOL along
airway J24 and it appeared to be impossible. Here is what I did:

  • From the FLM waypoint (ICAO "VK5 FLM "), I request the airways.
  • I get 6 airways in which FLM is present: J134, J24, J43, V44, V517 and V57. J24 is the one I want to fly to MOL.
  • If I list all the waypoints of airway J24, I get: OAKLE, BIGAL, MOL, FAK, RUSSL, HCM. MOL is part of it, that is fine, it is the waypoint I want to fly to, but FLM is not!! How can I add all the waypoints from FLM to MOL? And how can MSFS tell me FLM is in J24 and not list them among the J24 waypoints? Isn’t it illogical?

I must say that if I use another airway, such as J134 for example, FLM is in
it. But it is not on J24… If it was not in J24, why do I get J24 in the
airway list in which FLM is? I made the same test with HICKI and HGO, which
are also part of J24, and I have the exact same problem. I think there is a
bug here, or I missed something in the way I request the airways… Can you
please tell me if you reproduce this? Thanks, Eric

@Arzop FYI

Hello @ericmarciano I assume you are still witnessing this on avionics based
on the JS flight plan manager ? Can you tell us which aircraft/avionics you
are using to reproduce the issue and possibly repro steps in case we are not
familiar with this avionics. Regards, Sylvain

Yes Sylvain, I use the JS flight plan manager, which works perfectly except
this problem. In this case I use the facility loader and invoke the
getAllAirways function. I use an aircraft that is currently under development
so you don’t have it to reproduce the bug. I tried with the standard 747 and
when I create a route with FLM, then MOL, it shows J24 as the airway from FLM
to MOL, so it seems to work. It does not work like my aircraft:

  • In the 747, you enter FLM, then you enter MOL and the FMC detects they are both part of airway J24 but it does not automatically add the route waypoints between FLM and MOL, as shown on the LEGS page.
  • In my aircraft, you enter FLM in the FMC, then enter J24 and the FMC expects the entry of the waypoint to which you want to fly on airway J24. In my case, it would be MOL, but it does not work. For the example, I show you here how it works with J43 from FLM to ANEWA, and you can see all the intermediate waypoints between FLM and ANEWA are added automatically, shown on the LEGS page. It works with airway J43, I can’t understand why it doesn’t with J24.

I may use the Facility Loader the wrong way, any help would be appreciated.

Hello Have you had a look at our 747 FMC JS scripts in " asobo-vcockpits-
instruments-b747-8\html_ui\Pages\VCockpit\Instruments\Airliners\B747_8\FMC"
?
You can also use the CoherentGT debugger provided with the SDK to debug how
the flight planner in our case. Regards, Sylvain