Running FMGS on a dedicated machine: SimConnect

There is a new feature in Jeehell FMGS version 46.0. If you take a look at the whatsnew.txt found in the FMGS install folder Jean Luc has listed this new, but inconspicuous feature:

-Reworked installer package. Particularly, added an option to run FSX/P3D on a remote PC from FMGS server (seems to help reduce FPS hit in some cases)

This is huge — for the first time, the complete FMGS package can be run on a separate computer from FSX/P3D (visual generator). This simplifies the setup allowing you to dedicate a single computer, or multiple computers with FSX/P3D without FMGS using any CPU cycles. We all know how CPU intensive FSX/P3D can be so running the program on a separate system is a fantastic option.

How do you run FMGS on a dedicated machine? Using simConnect (a feature of FSX/P3D) this is possible. There is a comprehensive step by step guide to setup SimConnect here. The instructions are overly detailed so I have listed a simple step by step guide to get Simconnect working on Windows 10, and Prepar3D:

  • Install Simconnect on the FMGS and FSX/P3D computer. You can find the installer SimConnect.exe at the Prepar3D v3 Install Location\redist\Interface\FSX-SP2-XPACK\retail\lib folder.
  • On the P3D computer — go to the folder C:\Users\Your User Name\AppData\Roaming\Lockheed Martin\Prepar3D v3 and edit the file SimConnect.xml. Create the file with the following content:
 <?xml version="1.0" encoding="Windows-1252"?> 
<SimBase.Document Type="SimConnect" version="1,0"> 
 <Descr>SimConnect Server Configuration</Descr> 



Replace the ip field with the address of the P3D computer. You will need to setup FMGS and the P3D computers with network static address for them to find each other. Use a port of your liking.

On the FMGS computer (the dedicated computer) create a file C:\Users\Your User Name\Documents\Simconnect.cfg

In the config file you will need to have the following:

 Again switch out the ip address field for your P3D computer, and the port number for the one you specified in SimConnect.xml.
Setup FMGS\Configure.exe on both computers specifying the ip address of the computer running FMGS server, and the computer running FSX/P3D.

Thats it! You no longer have to deal with a remote USB or 3rd party utility programs because FMGS is smart and can translate all elevator, aileron, and rudder input axis remotely to your visual generator over the network.


The Flight Simulator (Feb 2017) now runs on a dedicated FMGS computer – an Intel 2500k processor overclocked to 4.0 Ghz. The computer is able to simultaneously run 3 LCD displays, an MCDU, Interface Board, and Joystick boards which handle the push buttons on the pedestal and sidestick commands. P3D runs on another computer over the network.

4 thoughts on “Running FMGS on a dedicated machine: SimConnect

  1. I got a simconnect config OK. However, all joystick are plugging into FSX (Visual) PC.
    FMGS server runs on a Laptop. How to make FMGS Config recognize axis which plugged to FSX’s PC?


    • All joysticks and USB must reside on the computer running FMGS Server and the FMGS config application. FSX or P3D can then run on a remote computer using simConnect. Alternatively you can use a remote USB program (Google) if you want to run the periphery on a different computer from FMGS server.


  2. Does this mean, that I would have to connect not only Joysticks, Tillers and Pedals to the dedicated FMGS Server but also any other Hardware like OVHD, MIP, Glare, Pedestal?


    • Only controls configured by FMGS_Config need to be run on the same computer. This includes the sidestick; elevators, ailerons, rudder inputs, spoilers, PFD/ND/ECAM/weather dimmer. You can run all your other hardware on other client computers, just as long as widefmgs is setup and you install the appropriate hardware driver.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s