G3X Touch Overview
Introduction
The G3X Touch package was written to preserve as much of the real unit's extensive customizability as possible within the sim. It can be configured in a multitude of ways to fit a particular airplane installation. Our goal is for developers of G3X Touch-equipped planes to be able to use the package included in MSFS "as-is" while taking advantage of the provided API to tailor it to their specific needs - without ever needing to fork or copy the codebase.
Customizing and Extending the G3X Touch
There are two primary avenues to adapting the G3X Touch to a specific airplane:
The first avenue is the panel.xml configuration file found in the airplane's panel/ folder. panel.xml is already used by the sim's BaseInstrument system to define some basic options for JS/HTML instruments. The G3X Touch extends this API to allow developers to configure a plethora of options that span all aspects of the avionics.
The second avenue is the Plugin API. The G3X Touch allows developers to inject plugins to add support for plane-specific features that would be too complex and/or cumbersome to be defined in an XML file.
For more details, please refer to the following pages:
External Navigators
In the real world, G3X Touch units are often paired with external navigators such as the Garmin GNS or GTN-series navigators to provide IFR flight planning and additional navigation capabilities such as VNAV and RNAV approach (glidepath) support. The sim G3X Touch also supports pairing with external navigators. In order for this to work, both the G3X Touch and the external navigator(s) need to be configured correctly. This configuration process is described in detail in the G3X Touch External Navigators page.