Networked Configuration

XPax can be used in a networked configuration where FSX or FS9 runs on a different computer.  FSX must be the "Deluxe" version which includes the SimConnect interface installation.  For FS9, FSUIPC 3.75 (or later) must be installed which is available from http://www.schiratti.com/dowson.html.

Configuring SimConnect (For use with FSX)

• FSX Deluxe version ONLY (standard does not include the SDK or required simconnect client installation files)
• FSX Service Pack 1 update applied (http://www.fsinsider.com)
• FSX SDK installed from FSX Deluxe Disk 1 (\SDK folder setup.exe)
• FSX SDK SP1A update applied (http://www.fsinsider.com)
• The computer to run FSX (hereby named SERVER) and the computer(s) to run SimConnect add-ons (hereby named CLIENT(s)) must be appropriately configured for normal IP networking
• Firewall software must be configured to allow SimConnect communications on the port you set (we suggest port 500) – This includes windows firewall – and applies to all computers, both SERVER and CLIENT(s)
• FSX SP2/Acceleration may also be installed but is not required.  In either case, SP1 and SP1A SDK is REQUIRED for XPax to properly connect.

Step 1: Verify requirements

Step 2: SimConnect.xml

You will need two Comm sections, one global (for network connections) and one local (for local connections).

A sample recommended SimConnect.xml file is located in your XPax installation folder (Program Files\HiFi\XPax).

Copy this file to your [ApplicationDataFolder]\Microsoft\FSX folder then edit it to adjust the values shown (ApplicationDataFolder is:
For Windows XP: C:\Documents and Settings\[USERNAME]\Application Data\
For Vista: C:\Users\[USERNAME]\AppData\Roaming\):

First <Simconnect.Comm> Section (global)

For Protocol,
IPv4 should be used.
Example: <Protocol>IPv4</Protocol>

For Address,
use either the computer name or the physical IP address of this SERVER.  This MUST be correct and the same address specified in the client's simconnect.cfg file.
Example: <Address>192.168.1.102</Address>

For Port,
use any port you wish to enable for SimConnect communications.  We suggest port 500.  This port will need to be enabled in any software firewall programs you are running (including windows firewall).
Example: <Port>500</Port>

Here is an example:

Second <Simconnect.Comm> Section (local)

It is important that the local section be exactly as specified otherwise local connections may not work correctly:

Step 2: SimConnect.ini

We suggest the default values throughout:
Change console to 0 (console=0) to disable to debug console.

Step 3: Installing SimConnect client on CLIENT(s)

Step 4: Configure CLIENT(s)

MyDocumentsFolder is:
For Windows XP: C:\Documents and Settings\[USERNAME]\My Documents\.
For Vista: C:\Users\[USERNAME]\Documents\.

There is an example file located in your FSX SDK installation folder (normally C:\Program Files\Microsoft\Games\Flight Simulator X SDK\SDK\Core Utilities\SimConnect SDK\config).  We also have included a sample file in your XPaxinstallation folder.  We suggest copying this file to the appropriate location and then modifying as follows:

The values for Protocol, Address and Port must be configured exactly the same as you have configured for the server’s SimConnect.xml file global section.  We recommend the other values be left default.

Here is an example SimConnect.cfg file:
[SimConnect]
Protocol=IPv4
Address=192.168.1.102
Port=500
MaxReceiveSize=4096
DisableNagle=0

The SimConnect.cfg file needs to be set for all client computers that will be running addons that need to connect to FSX on the server.

Step 5: Test the configuration

Troubleshooting SimConnect:

If you are unable to get things working properly, please check for the following common issues:

• Standard networking not properly configured between computers
• SimConnect.xml, SimConnect.ini and/or SimConnect.cfg not properly existing or configured properly and in the proper locations
• Port not enabled via software firewalls
• Improper computer name or ip address set in the Address fields of the .xml and .cfg files
• Protocol not set for IPv4 in .xml and/or .cfg files
• SimConnect.msi installer not run on client machine