C:fs9gps variables not working on MSFS2024

[ScorpionFilm422]

GET_FLIGHTPLAN doesn’t return the arrival or departure index in 2024.
The index is -1.

[MattNischan]

I am not able to reproduce that here; if you’re using the EFB to select the arrival and departure, you will need to file the flight with ATC using the button on the route page before it will become the ATC flight plan that GET_FLIGHTPLAN reads.

Thanks,
-Matt

[ScorpionFilm422]

Sorry Matt. My bad. I forgot the step “file with ATC”. I thought the initial flight plan would be sent automatically to the ATC. Works as expected.
Thanks
Pierre

[B21]

Another detail that may or may not be necessary:

If after a PLN file load the internal API’s only show the PlannedRoute as generated by the EFB app it would be incredibly helpful to discriminate new additional waypoints that have been generated by the EFB app from User waypoints that originated from the PLN.

This is subtly different than the ‘can we still get the original idents from the PLN’ issue - it’s having a non-hack way of being able to detect the EFB app additional waypoints in activities (in our case, gliding) that can’t use those.

thanks.

[MattNischan]

@B21

new additional waypoints that have been generated by the EFB app from User waypoints

The EFB does not generate any additional waypoints. The waypoints on the EFB are 1:1 in order as to what appears in the PLN file.

Thanks,
Matt

[B21]

Wow, awesome.

Thanks.

[MattNischan]

Hello all,

The new Planned Route APIs are now documented, available at:

• JS:
  • API: JS_LISTENER_PLANNEDROUTE
  • Events:
    • AvionicsRouteRequested
    • AvionicsRouteSync
• WASM: Planned Route API

Thanks!
-Matt

[ScorpionFilm422]

@MattNischan

The legacy GET_FLIGHTPLAN call will continue to exist for backwards compatibility but MSFS 2024 addons should be upgraded to use the new route API. Because adding any additional data would be a breaking change for backwards compatibility, the data structure returned by GET_FLIGHTPLAN will remain the same with none of the additional data (i.e. it will continue to just be a flat list of legs with limited procedure support, etc).

Hi Matt,
GET_FLIGHTPLAN doesn’t return the departure and arrival waypoints as in MSFS2020 (see the first image).
GET_APPROACH_FLIGHTPLAN returns no waypoints even if an approach procedure index is defined (second image).
So these calls are not compatible.

[ScorpionFilm422]

Sorry, my bad. I used coherent ADD_WAYPOINT for the origin and destination instead of SET_ORIGIN and SET_DESTINATION.
It was working in 2020 but not in 2024.