Run FSX on one PC and charts or tools on another using your local network, SimConnect or a companion bridge, with firewall fixes and setup steps.
Run FSX or FSX: Steam Edition on the main PC and place the chart or utility on the second PC, connected to the same local network. Static charts need no link; live maps and tools need either the program’s companion bridge on the FSX PC or a correctly configured SimConnect network connection.
Which connection method should I use?
Use no connection for static charts, a companion bridge where one is offered, and direct SimConnect only when the tool specifically supports it.
| Requirement | FSX computer | Second computer | Connection |
|---|---|---|---|
| PDFs, web charts or reference material | FSX only | Browser or document viewer | None required |
| Live moving map | FSX plus the tool’s connector | Main chart or map application | Connector’s network protocol |
| SimConnect-compatible utility | FSX with network SimConnect enabled | Utility and its required SimConnect runtime | IPv4 address and matching port |
| A second copy of FSX following the aircraft | FSX plus synchronisation software | Another FSX installation | Specialised simulator synchronisation |
A companion connector is usually the least troublesome choice because it handles FSX locally and sends only the required data across the network. Little Navmap is a common example: our separate-PC Little Navmap and Little Navconnect instructions explain that arrangement in detail.
How do I use a companion bridge on the FSX PC?
Install the small connector beside FSX and run the full chart or utility application on the second computer.
- Join the same local network. Connect both computers to the same router. Wired Ethernet is preferable, although ordinary non-guest Wi-Fi is adequate for most map data.
- Give the FSX PC a stable address. Find its local IPv4 address with
ipconfig, then reserve that address in the router if possible. The address will normally begin with a private range such as192.168or10. - Install the correct component on each machine. Put the connector or bridge on the FSX computer and the main interface on the second PC. Installing both parts remotely is a mistake we see often.
- Allow the applications through the firewall. Permit FSX and the connector on trusted Private networks. Permit the remote tool to make outbound connections. If the connector uses a specified port, the port shown on both computers must match.
- Load a flight before testing. Start FSX, enter the cockpit, launch the connector and then connect from the second computer using the FSX PC’s local IPv4 address.
You do not need to install a complete second copy of FSX just to run a chart application. The connector should also remain on the main computer; it needs local access to the simulator.
How do I configure FSX SimConnect over a network?
Direct SimConnect requires a server configuration on the FSX PC and matching client details on the computer running the tool.
- Check what the utility expects. Some programs use direct SimConnect, while others require their own bridge and ignore generic SimConnect network files. Use the runtime supplied or specified by the utility because several SimConnect generations can coexist.
- Find the active FSX configuration folder. For a normal boxed installation this is usually under
%APPDATA%\Microsoft\FSX. FSX: Steam Edition may use that folder or%APPDATA%\Microsoft\FSX-SEwhen installed alongside boxed FSX. The correct folder is the one containing the activeFSX.cfg. - Configure the FSX endpoint. Back up any existing
SimConnect.xml, then add or amend an enabledSimConnect.Commblock using IPv4, global scope, the FSX computer’s LAN address and an unused port. Preserve existing communication blocks used by local add-ons. - Configure the remote client. Enter the same address and port in the utility, or create
SimConnect.cfgwhere that particular program expects it. Typical client values identifyProtocol=IPv4, the FSX PC underAddressand the matchingPort. - Restart and test. Restart FSX after changing
SimConnect.xml, load a flight and then open the remote client. Configure one tool first before adding more networked utilities.
Do not copy the same configuration file blindly onto both PCs: SimConnect.xml defines the FSX-side listener, while SimConnect.cfg tells a client where that listener is. Some utilities replace the latter with connection fields in their own settings.
Why will the second PC not connect to FSX?
Most failed connections come from an incorrect address, a blocked application, mismatched ports or editing the wrong FSX: Steam Edition folder.
| Symptom | Likely cause | Fix |
|---|---|---|
| Connection refused or timed out | Bridge is not running, firewall is blocking it or ports differ | Start the bridge locally, verify both port values and allow the applications on the Private network profile |
| It worked until the router restarted | The FSX PC received a different address through DHCP | Update the client address and create a router reservation for the FSX computer |
| The tool connects but shows no aircraft | No flight is loaded, the wrong simulator provider is selected or the connector is running twice | Enter an active FSX flight, select FSX in the tool and leave only one connector instance running |
| FSX: Steam Edition ignores SimConnect.xml | The file was placed in the inactive FSX or FSX-SE profile | Locate the folder containing the FSX.cfg that changes when FSX settings are saved |
| The utility reports that SimConnect is missing | Its required client runtime is absent | Install the SimConnect runtime supplied or explicitly required by that utility; do not assume another runtime is interchangeable |
| Connections fail only over Wi-Fi | Guest isolation, access-point isolation or a VPN adapter is interfering | Use the normal home network, disable the VPN for testing or connect both PCs by Ethernet |
If a computer name fails but its numeric IPv4 address works, use the address. Name discovery is not required for SimConnect. Opening router ports to the internet is also unnecessary and unsafe; this traffic should remain inside the local network.
How do flight plans and chart files reach the second PC?
Live simulator data and ordinary files are separate, so SimConnect does not automatically transfer every chart or flight plan.
Open static charts directly on the second PC. For an FSX .PLN file, export or copy it to that computer, or use a trusted Windows shared folder with read-only access where practical. Some planning tools can retrieve or send a route through their connector, but that depends on the application rather than FSX itself.
Can I run VATSIM software on the second PC?
A supported network or remote mode is required; moving an online client to another computer does not make it detect FSX automatically. Our FSX online-flying setup and network checks cover the SimConnect and firewall points involved. If the chosen client does not support remote operation, keep it on the FSX PC and move only charts or planning tools.
Can SimConnect display FSX graphics on the second PC?
SimConnect sends simulator variables, events and position data; it does not stream the cockpit or scenery image to another computer.
For an extra cockpit panel, a monitor connected directly to the FSX computer is usually simpler. Running another FSX instance that follows the main aircraft is a different task requiring synchronisation software, compatible installations and any applicable licensing. Our library has an FSX utility for synchronising aircraft movement between computers, but that should not be confused with a normal chart-client connection.