plane icon Welcome to Microsoft Flight Simulator’s SDK Q&A Platform!

You have questions regarding the SDK? DevMode Tools? SimConnect? You would like to submit an idea for future improvements, seek help or exchange knowledge? You’re in the right place.


Please take a moment to read the platform’s guidelines before you get started!


question

Cammac avatar image
Cammac asked FlyingRaccoon edited

WASM NAV API missing way points compared to JS API

Hi,

We have had reports of missing way points when using the WASM nav API.

Please see listed points below:


- SL VOR (Inserts but should have multiple listed and did not trigger the minimal list just returned a single waypoint structure)

- INYOE

- KILLA

- TROSE (Works in 1.30.12) But reported as not working

- BK404

- BK402

- DL239

- LIBBOY

- YUNG

- ZIQOR (Works in 1.30.12) But reported as not working

- DEANO (Works in 1.30.12) But reported as not working

- SADDE (Works in 1.30.12) But reported as not working

- TRNDO (Works in 1.30.12) But reported as not working


We cross checked these results with a standalone sim connect program I identified the same issues.

We have also noted that since the AAU 1 beta more waypoints are being reported as returning not found.


Many thanks,




aircraftwasmc++
2 comments
10 |10000

Up to 5 attachments (including images) can be used with a maximum of 4.8 MiB each and 23.8 MiB total.

tracernz avatar image tracernz commented ·
1 Like 1 ·
Cammac avatar image Cammac commented ·

Would also like to add to this.

Most if not all NDBs are not returning the correct results either.

Some examples:

-UW in Edinburgh

-EME and EMW in East Midlands

-SH in the UK WOL in the UK


1 Like 1 ·
FlyingRaccoon avatar image
FlyingRaccoon answered

Hello @Cammac

We have reviewed your list of ident and in most case, data is available and correct.
Be aware that when requesting data with an ident that corresponds to multiple results, data will be returned as SIMCONNECT_RECV_ID_FACILITY_MINIMAL_LIST

That said, some of these are incorrect or missing:

- INOYE: duplicate waypoints

- LIBBO: duplicate waypoints

- KILLA: we could not find any info about this one. Do you have its coordinates or do you know if it's mentioned in any charts?

Regards,
Sylvain


10 |10000

Up to 5 attachments (including images) can be used with a maximum of 4.8 MiB each and 23.8 MiB total.

Cammac avatar image
Cammac answered FlyingRaccoon edited

Hi,

Thanks for the response.

I do not have the set coordinates for the way point KILLA this was a user reported error not an internal one that we identified.

We have implemented the minimal list correctly, and it will show duplicate way point pages for way points with same name.

For these specific way points however there is the following error - see response below this one INYOE triggers an exception first and then a minimal list. However, it triggers an exception first and therefore stops there. This must be rectified and then the original logic we have built will work.

Also please see attached image of the aircraft correctly returning a result from the minimal list for another way point.

Did you also get a chance to check out the follow up to this report related to NDBs.

Many thanks,


pl.png


pl.png (565.2 KiB)
1 comment
10 |10000

Up to 5 attachments (including images) can be used with a maximum of 4.8 MiB each and 23.8 MiB total.

Hello @Cammac

The exception you receive is a SIMCONNECT_EXCEPTION_INVALID_DATA_SIZE.
This is not triggered by the Facilities functions.

This exception can be triggered by:
SetDataOnSimObject
CreateClientData
AddToClientDataDefinition
SetClientData

This is usually caused by the structure defined on your side having padding when SimConnect is expecting a packed one as explained here:
Simmconnect I/O Error - MSFS DevSupport (flightsimulator.com)

I see you are already storing the dwSendId so you should be able to identify precisely which call triggers this exception.

Regards,
Sylvain

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 5 attachments (including images) can be used with a maximum of 19.1 MiB each and 23.8 MiB total.