-
Notifications
You must be signed in to change notification settings - Fork 0
Model Matching XPlane
See Model Matching for the general algorithm, the attributes used, and the Explain Match dialog. This page covers what's specific to the X-Plane build - which currently has real, known gaps compared to the other builds (see "Known limitation" below).
Scan For Models walks your CSL (Custom Scenery Library) folders and parses each package's xsb_aircraft.txt, which declares ICAO/AIRLINE/LIVERY match keys for that CSL model. This is a fundamentally different, much lighter-weight source than the other builds' aircraft.cfg scan: xsb_aircraft.txt is purely a set of matching hints for the CSL package, not a real aircraft configuration file - it has no class code, wake turbulence category, or registration fields at all, and never did.
Known limitation: as things currently stand, the ICAO match key read from xsb_aircraft.txt is not carried through into the field the matching algorithm actually reads for ICAO type - it only ends up in a cosmetic display field. In practice this means ICAO-type/class-code/WTC-based matching does not currently work reliably for X-Plane, and every installed CSL model is classified into the same coarse typerole bucket regardless of what it actually is. This is a known, confirmed gap (not a "some aircraft won't match" edge case - it affects every scanned model on this build) and is on the list to be fixed; until then, matching on this build relies mainly on livery/title text matching rather than ICAO type/class code/WTC.
Registration: not available from CSL data at all on this build.
The same unified scorer described on the main Model Matching page runs regardless of build, but per the limitation above, the ICAO type/class code/WTC signals it would normally rely on most heavily are not currently populated for locally-installed X-Plane models - so a remote aircraft's ICAO type/class/WTC (however well those are reported on their end) can't be matched against your installed CSL library the way they can on the other builds. Matching here currently falls back mostly to title/livery text and typerole, which is weaker than the other builds - see "What matching can and can't know" on the main page for why that matters.
Models that are scenery props, static display liveries, or otherwise non-flyable are filtered out of your own installed-model list before any of this happens, via the ban list described on the main page - they can never accidentally become what a friend's aircraft gets substituted to.