To access the forum, please use same login credentials as used into FSAerodata.

Product Compatibility List

Site Admin
Posts: 841
Joined: Thu Dec 15, 2016 10:09 am

Product Compatibility List

Post by fsaerodata »

This is a list of 3rd party products which are confirmed compatible with fsAerodata (FSAD) aeronautical database:

- VoxATC:
FSAerodata is compatible with latest VoxATC v7.42;
Please disable the option 'Default ATC Callsign' on config tool, to allow the use of real-world names instead of the old and sometimes obsolete callsigns used by the default ATC system.

Following deviations have been reported by users:

a) Oceanic centers: latest fsAerodata version fixes a previous issue where VoxATC was not able to read FSAD center sectors.
b) VoxATC has no capabilites to read different altitude sectors on same boundary; it assigns one frequency regardless of the altitude.
c) Conflict with MyTraffic sceneries: some users reported errors during initialization; problem was fixed having MyTraffic a higher priority than FSAD on scenery list.
d) "Fatal error" message displayed due a conflict with addons that use old ICAO designator; please disable the option "ICAO Identifiers" in the options menu.
e) At non-towered airports, VoxATC request user to comunicate with Traffic Advisory comms using generic freq. 135.475 instead of freq in database. Update: Issue has been fixed on cycle 1901.

Please run VoxATCIndexer tool after updating your flightsim aeronautical database, to avoid errors during VoxATC initialization.

- Pilot2ATC:
The ATC tool is compatible and is able to read the ARTCC sectors updated by fsAerodata. Please read Pilot2ATC User's Manual for more information.

- Pro-ATC/X:
Application runs fine together with fsAerodata.

- Aivlasoft EFB: fsAerodata is not compatible with EFB v2. The ILS data cannot be displayed on map.

- Little Navmap flight planning and moving map tool is fully supported; airspace, approaches, SIDs, STARs and navaids are displayed correctly.

- FS Commander limitations: fsAerodata is not compatible; airport entries are duplicated on search window ( our product adds an airport layer with approaches that replaces obsolete data, following FSX/P3D SDK standard; FSC reads this layer as a new airport, hence the duplicates shown). FSC does not read fsAerodata entries.

- Plan-G: SIDs and STARs procedures reported as errors when Plan-G builds database; they are not listed or displayed on map. Duplicated entries when showing airport information.

- UTLive The AI Traffic tool is fully compatible.

- 3rd party airports (e.g. Orbx, Aerosoft,...) :
fsAerodata does not modify or disable any add-on's data due to licensing restrictions.
FSX and Prepar3D up to v4.5 HF1:
Following fsAerodata navigation data is updated: comm freqs, approaches, ILS and ILS/DME data, enroute navdata. External content not updated (they are normally part of add-ons navigation data): runway headings, terminal NDBs and terminal waypoints. Obsolete navdata from external content will show up on navigation map or GPS; it's a visual effect, but the product cannot disable them.
Altitude adjustement bgl files from external add-ons may avoid updating runway designators or airport names.

Prepar3D v4.5 Hotfix2 and higher:
fsAerodata has to be placed below any 3rd party airports or sceneries, to avoid elevation issues.

FSAD updates several ICAO designators to the real world conditions, but still some publishers use the old FSX/P3D designators on their sceneries(Orbx, Aerosoft,..). As a result, there may be conflicts when FSAD is active (airport runway sinks or floats over terrain); please disable option "ICAO Designators" on FSAD Config tool, and re-run database update.

Some users have reported elevation issues when using Orbx Vector in conjuntion with FSAD. Please check any elevation conflicts running the specific tool provided by Orbx Vector.
Jose L. Rubio / FSAerodata
Follow us on Twitter
Follow us on Facebook