GPS WP NEXT ID variable cannot be set

[MSFS 2024] Bug Reports HTML/JS
1

Version: 1.5.27.0

Frequency: Consistently

Severity: High

Marketplace package name: N/A

Similar MSFS 2020 issue: Not reproducible on MSFS 2020.

Bug description:

Hello,

I found that GPS WP NEXT ID variable cannot be set from JS on MSFS 2024.

image
image707×195 20.9 KB

With GPS OVERRIDDEN variable set to true, it should be possible to edit all GPS variables.

Please note that Working Title systems depends on this as the WT flight plan is not synchronized with the legacy MSFS flight plan. Hence only GPS WP NEXT ID variable allows to know about the next waypoint.

There is no issue to edit other GPS variables, for example:

image
image523×129 14.8 KB

I guess there should be something wrong with setting string variables.

Also, the SDK documentation shows those variables as non-settable while they should be settable if GPS OVERRIDDEN is true:

image
image2517×730 72.2 KB

The subject has already been discussed on Working Title Discord.

Kind regards,

Romain

2

Hello @R-AzurPoly

This seems to be the result of an incomplete fix for this issue: Unable to set ATC FLIGHT NUMBER, ATC ID, and ATC AIRLINE - [MSFS 2024] Bug Reports - MSFS DevSupport
I have identified the cause and we will have someone work on a fix.

Documentation will be reviewed as well.

Regards,
Sylvain

3

Hi Sylvain,
Not directly related (tell me if I have to set another topic), but I can also report this issue (tested on MSFS2020, maybe the same on 2024):
When GPS OVERRIDEN is set to true, the coherent call RECOMPUTE_ACTIVE_WAYPOINT_INDEX modifies the GPS WP NEXT ID while it should not.

4

Yes, I think it’s worth tracking separately.

5

Thanks,

Here is the new topic: RECOMPUTE_ACTIVE_WAYPOINT_INDEX call changes GPS WP NEXT ID