bug Why has suddenly the arrival runway become part of the missed approach procedure?

[dectenor1]

Why has suddenly the arrival runway become part of the missed approach procedure? 

This is completely wrong and messes up the flight plan and various things on the F-PLN page associated with it.

Looking at the changelog, it seems like this was done on purpose....

Edited 20 hours ago by dectenor1

[dectenor1]

BKPR35 should be part of the main route and in green not blue

 

This issue also affects things like distance remaining of the route, as it won't take into account the part from the final fix to the runway.

[Der Michel]

I also mentioned this in one of my posts. No idea what they mean with that Changelog entry. But if it is what we see here….

[Xenon341]

I copy paste to you the answer they gave on their Discord to another user with the same problem : 

 

Quote

Rich [UTC+8] — 12:45

Hi, if you're using sim-default navdata, this is a known issue specific to FS20 with recent navdata cycles. Team is looking into workarounds that can be implemented next update.

Issue,

There is a lack of cohesion between the 2 sims in terms of how the arrival runway waypoint (i.e. KEWR04L in this case) is defined in the default navdata. In FS20, the arrival runway waypoint is defined as the "first" starting waypoint of the missed approach procedures (you'll see on the FMS its in blue as well). In FS24, the arrival runway is (correctly) the last waypoint of the active flightplan, and missed approach starts only after that (you'll see on the FMS its in green).

Workarounds,

1/ This not an issue if you use Navigraph navdata (set via OIS 3RD PARTY page). Their navdata handles it correctly in both sims. 2/ If conducting an ILS, arm APPR and be vigilant to intercept the ILS while complying with charted alt restrictions.

 

[Der Michel]

2 hours ago, Xenon341 said:

I copy paste to you the answer they gave on their Discord to another user with the same problem : 

 

 

That’s not the solution. I have the problem in MSFS2024. Your quote indicates that 2020 is problematic and 2024 fine.

But to my understanding a GA is always part of the APPR. Coded is that  just in a sequence of wpts (leg types according ARINC 424). So if the sims split that part…it’s part of SDK and no hidden item.

And Navigraph as a source is still no option as the sim is still crashing with it enabled in A350.

 

Edited 1 hour ago by Der Michel