G1000 Simulator v1.3.2 Setup Guide

Unpack Application Directory

Extract the zip file downloaded from the Simgeneering.com website. This contains the FIP G1000 Emulator v1.3.2 application and all associated data. The extracted directory can be installed in any location.

Install Java JRE

FIP G1000 Emulator v1.3.2 is a Java application. To run it, you must have the Java Runtime Environment (JRE) installed. It is necessary to have both 64-bit and a 32-bit (x86) versions of JRE 8 or higher installed on your computer to run the FIP G1000 Emulator v1.3.2 software and to connect it to the flight instrument panel and flight simulator drivers. At the time of writing, 32-bit (x86) and 64-bit versions of JRE 8 are available from https://www.oracle.com/java/technologies/javase-jre8-downloads.html.

Edit Configuration File

In the application folder of the FIP G1000 Emulator v1.3.2 you will need to set some variables in the configuration file, “config.xml”. This contains all the configuration variables needed to run the application. You may need to change the variables listed below according to your flight simulator installation.

<SIMCONNECTDLLLOCATION>

This is the folder that contains the SimConnect.dll library that was installed with your flight simulator software. Use a double backslash \\ between each folder level.

For FSX Steam Edition the folder path is probably: “C:\\Program Files (x86)\\Steam\\steamapps\\common\\FSX\\”

For MSFS 2020 Steam Edition the folder path is probably: “C:\\Program Files (x86)\\Steam\\steamapps\\common\\MicrosoftFlightSimulator\\”

<SIMCONNECTVERSION>

This indicates whether the installed SimConnect.dll is a 32-bit or 64-bit version. Use “32” for a 32-bit version or “64” for a 64-bit version.

<DIRECTOUTPUTDLLLOCATION>

This is the folder that contains the DirectOutput.dll library that was installed with your flight instrument panel driver software. Use a double backslash \\ between each folder level.

For FSX Steam Edition the folder path is probably: “C:\\Program Files (x86)\\Logitech\\FSX Plugin\\”

For MSFS 2020 Steam Edition the folder path is probably: “C:\\Program Files\\Logitech\\DirectOutput\\”

Flight instrument panel drivers can be downloaded from: Logitech’s FIP pages

<DIRECTOUTPUTVERSION>

This indicates whether the installed DirectOutput.dll is a 32-bit or 64-bit version. Use “32” for a 32-bit version or “64” for a 64-bit version.

<SIMDOCPATH>

This is the file path to the folder where flight plans are stored by your flight simulator software. Use a double backslash \\ between each folder level.

For FSX Steam Edition the folder path is probably: “C:\\Users\\<USER>\\Documents\\Flight Simulator X Files\\”

For MSFS 2020 Steam Edition the folder path is probably: “C:\\Users\\<USER>\\AppData\\Roaming\\Microsoft Flight Simulator\\”

<JRE32LOCATION>

This is the folder that contains the 32-bit (x86) JRE application: java.exe. Use a double backslash \\ between each folder level. However for this variable do not include the double backslash \\ at the end of the folder path.

For JRE v8 32-bit the folder path is probably: “C:\\Program Files (x86)\\Java\\jre1.8.0_291\\bin”

<JRE64LOCATION>

This is the folder that contains the 64-bit JRE application: java.exe. Use a double backslash \\ between each folder level. However for this variable do not include the double backslash \\ at the end of the folder path.

For JRE v8 64-bit the folder path is probably: “C:\\Program Files\\Java\\jre1.8.0_291\\bin”

<SHELLLOCATION>

This is the folder that contains the Windows cmd.exe application, normally “C:\\WINDOWS\\system32\\”. Use a double backslash \\ between each folder level.

<USERKEY>

This is the key for the licence for the FIP G1000 Emulator v1.3.2 software. Normally this will be set when the software is downloaded from the Simgeneering.com website and should not need to be changed.

Download Databases

The database files contain all the geographical and aviation data for the multi-function display (MFD) module. These need to be downloaded separately from the FIP G1000 Emulator v1.3.2 software, using the software interface. See the following video: