Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Not fully SDK compliant aircraft.cfg?

Featured Replies

Nothing serious (I think), but…

When flying online (just using FSHost) it was sometimes mystical why some of my mates where only able to recognize me as a Cessna instead of a B736 or so. I checked therefore the aircraft.cfg in order to identify the data that might be used to trigger the correct information and I found some stuff that really surprised me.

 

According to Microsoft’s SDK each aircraft container should have a section [General] containing the main type related information: type, model and performance data. PMDG’s implementation looks perfectly okay for me:

 

[General]

atc_type=BOEING

atc_model=B73n // (depending on the model n=6…9)

<..snip..>

 

The model identification is in accordance with ICAO and in compliance with the SDK, too (I think my buddies do neither have a B736, B737 nor a B739 in their hangar). Surprisingly I found the same data in each section of [fltsim.x] where it should not appear and partly with non ICAO compatibel content:

 

atc_model=737-n00  // (depending on the model: n=6…9), not following ICAO type coding!

atc_type=BOEING

 

In the best case those data are ignored (I don't really know), however they should not be there. If ever a final update of PMDG's NGX series is planned I suggest to put it on the list in order to leave the redundancy away.

 

Does anybody know about the way the aircraft.cfg is really computed? As far as I understand, first in the row are all the container common parts, including [General]and then the variants listed in the [fltsim.x] sections. I would be interested as well to know which data are really used by simconnect in order to decide which aircraft should show up. The SDK remained a secret for me in this case.

 

 

By the way, following Microsoft’s suggestion another parameter should be used in a different way (even if I have doubts that any part of the application takes care of it). Instead of ui_typerole=737-600 it should be (suggested by MS for their default B738) ui_typerole=”Commercial Jetliner”.

 

-----------

[OFF TOPIC] I tried to write this in a ticked (twice) and ended up with - nothing :huh: . There was no visible response of PMDG's software after hitting "next" to finalise the input. And yes, cookies are enabled.

 

 

 

EDIT: Sorry for double posting but I got a "server not available" error after my first try.

Regards,
Axel

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.