MSFS Limitations

A few main features of EFBv2 are unfortunately limited when using MSFS. This is because of the different design principles of MSFS compared to the previous simulators like P3D and FSX. Please read carefully the limitations described hereafter.


As MSFS continues to evolve, newer versions of MSFS will be available in the future. We will test each new version and if necessary we will adjust the content of this page.

Ground Layout

Ground layouts are available in the EFB Database for each airport. However we cannot display tarmac layouts (Aprons), as due to the nature of the present MSFS Ground Polygon compilation this would enlarge the database by almost 100%. This would slow the database building process as well as the data transfer with the Client(s) to unbearable delays.


Weather can still not be read from the Simulator due to the fact that the weather system in MSFS is not open to third party tools. To bypass this please select "Real Weather" as the weather provider. This can be done in the Client settings (tab 'Global').


AI Traffic is visible, but the definitions are not yet clear. We display what FSUIPC7 is supplying but there is no specific information available in the SDK. It can however still be activated/deactivated by the usual soft keys and/or option buttons.

Flight plan

Flight plan handling is similar to the well known default GPS Flight Plans in FSX/P3D. A flight plan can still be created externally by PFPX, SimBrief or similar. A flight plan can also be created using the EFBv2 functionality.  Once an EFBv2 flight plan has been created this plan can be loaded from the so called 'World Map' in MSFS. 

Automatic transfer to the default GPS system (using FSUIPC7) after the flight plan has been changed in EFB, is unfortunately no longer possible due to changes in MSFS with SU11 / AAU1. 

Add-on Airports

Detecting whether an airport is an add-on or default airport is not always possible, therefore the 'circle around the asterisk' on the world map is not 100% reliable.

This is especially true for airports purchased via Marketplace Online Store. Most of these Add-On airports feature user-specific encrypted files instead of the usually 'open' BGLs. Encrypted files make it impossible to read the required ground layout information and therefore EFB cannot depict the ground chart of such an Add-On airport. If the data files are encrypted, only the default Ground Chart will be available.