MSFS2024 GET_FLIGHTPLAN waypoints ident / lat / long

Version: 1.0.7.0

Frequency: Consistently

Severity: Blocker

Marketplace package name: All of the gliders in the sim

Context:

Similar MSFS 2020 issue: MSFS2020 is ok
Bug description:
GET_FLIGHTPLAN data changed in MSFS2024 vs 2020

Repro steps:

UI Load flightplan … Coherent.call(GET_FLIGHTPLAN), only data left from the waypoints in the PLN is the lat/longs.

Background - WT have already been supportive here, which is appreciated:
As discussed on the runup to launch, JS GET_FLIGHTPLAN in MSFS2024 returns a similar JS object to MSFS2020 but the data available for each waypoint after a PLN flightplan load in MSFS2020 was { ident, lat, long } and in MSFS2024 that has shrunk to { lat, long } with a new random ident being generated and the one from the PLN file discarded

We have a lot of glider pilots now with MSFS2024 and need a more concrete confirmation whether/when MSFS2024 might be fixed to provide that “ident” (or another string) that can be passed for each waypoint through from the PLN to the GET_FLIGHTPLAN JS call (or indeed another new call that can be made from JAVASCRIPT)

We can’t migrate 10’s of thousands of lines of JS Nav Panel gauge code to the WT typescript just to read the data from a loaded PLN (I don’t think the idents are the WT info anyway) and our community is already moving quickly to run those html/js gauges OUTSIDE of the sim just so the PLN can be dropped there instead of used in the sim.

Key issue:

We need this either flagged up as “by design” in which case we’ll pivot to providing alternative support for gliding flightplans outside the sim, or have some confirmation the waypoint “ident” or an alternative string can propagated from the PLN to JS gauge as was the case in MSFS2020.

More detail on the EFB app / JS GET_FLIGHTPLAN issues, in summary the EFB app is omitting waypoints in that JS return, nothing to do with our attempt to use the waypoint ident field for gliding.

Step 1. Load this sample PLN file containing departure airport, 5 user waypoints, destination airport (remove the .xml suffix added just to post here)

North Weald Test MSFS2024 icao.pln.xml (2.6 KB)

Step 2. See the waypoints in the EFB app, as screenshot, all 5 intermediate user waypoints are correctly listed. These are custom lat/long “User” waypoints with “ICAO” values each set to 8 letters (Obviously custom lat/long waypoints don’t actually have internationally assigned ICAO codes)

Step 3. Click the “File Plan with ATC button” & close the EFB App. See the flightplan on the world map still showing all 5 user waypoints.

Step 4. Start the flight, use the Coherent console to look at the JS Coherent.call(“GET_FLIGHTPLAN”) return, which only has the first and last user waypoints in the ‘waypoints’ array:

Please note the GET_FLIGHTPLAN API return only contains TWO waypoints, not the original FIVE so it’s currently not a viable source for the flightplan info.

As mentioned above the most important thing for us is to confirm whether this is “By Design” or “Bug Logged” so we can plan accordingly.