If you find XGoFlight is not working as expected, please read the following very carefully. If all else fails, please report a bug in the Plugins section of the Forums. Don’t forget to include your Log.txt file.
- Always check the Log.txt file for errors.
- Before submitting a bug, please disable all plugins and confirm the problem is still present. Not all plugins play nice together. For example, XPUIPC 1.9.0, which was designed for X-Plane 9, is known to cause problems with the MCPPRO module.
- XGoFlight and Sandy Barbour’s GoFlight plugin cannot be loaded at the same time. In order to use XGoFlight, Mr. Barbour’s plugin must be disabled (by changing the XPL extension) or removed from the plugins directory.
- If you load up a custom aircraft and the buttons or switches don’t seem to work, try reloading the configuration (Plugins > XGoFlight > Reload config). This can happen if a custom aircraft loads its datarefs and commands after XGoFlight parses the configuration file.
- MCPPRO: If you are experiencing problems with the MCPPRO, please check the firmware version by observing the CRS1 LCD while plugging it in. If it does not read A25, it may require a firmware update to work with XGoFlight.
- If you see an “Error 126″ notice in the XP log file, you are missing the Visual C++ Redistributable. Links to the required Visual C++ Redistributable packages are available in the Installation section.