How to use FSUIPC7 on a 2nd / client PC

[MrSwan]

Hi John, thank you very much for sharing your knowledge. I'm just getting started on this simulation thing. To use P2ATC on a laptop networked to a PC with MSFS, do I need the paid version of FSUIPC7 or is the free version enough?

[John Dowson]

5 hours ago, MrSwan said:

To use P2ATC on a laptop networked to a PC with MSFS, do I need the paid version of FSUIPC7 or is the free version enough?

You need the paid version as you need the assignment functionality. Please try with the trial license (available in a topic at the top of this sub-forum) before you purchase.

John

[AFR7796]

On 12/9/2021 at 6:39 PM, John Dowson said:

It is now possible to run FSUIPC7 (v7.2.13 and later) on a client PC, that is, a 2nd PC where MSFS is not installed. This should allow FSUIPC clients to be ran on the client PC and allow them to communicate to the FS without the need for WideFS/WideClient. Note that this DOES NOT replace or duplicate the functionality provided by WideFS. When FSUIPC7 runs on a client PC, it will maintain its own offset area distinct from that of the offset area used by FSUIPC7 on the FS machine. However, most offsets should contain the same data, as they are populated by the data received from the FS, but be aware of this if/when writing to user offsets (e.g. using lua).

Note also that you do not have to have FSUIPC7 running on the FS machine to run FSUIPC7 in the client machine.

The following functionality in FSUIPC7 will not work (or is not available) in FSUIPC7 when ran in a client machine:
    - no installer - you need to manually install/copy FSUIPC7 to the client machine
    - no possibility of sending key presses to the FS (key presses CAN be received)
    - no auto-start or auto-connection
    - ....

To have FSUIPC7 running on a client machine, please follow the steps indicated below.

 

1. Configuring SimConnect on the MSFS computer
Locate your MSFS2020 SimConnect.xml file. For steam installs, this should be under
    <Your User Account>\AppData\Roaming\Microsoft Flight Simulator
and for MS Store installs under:
    <Your User Account>\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

Open the file in an editor, and add a Global (remote) IPv4 port by adding the the following entry:

where Your Local MSFS PC Address is your 'internal' network IP address, not your outward-facing IP. To find this, open Command Prompt on the MSFS Computer, type "ipconfig" and look for the "IPv4 Address" listed under your active internet connections.

You can also change the port number, but this MUST match the port number defined in the SimConnect.cfg in your client PC (see below). Note that you also may need to open this port in any firewalls that you may use (although I did not have to do this when I configured in my LAN).

 

2. Install FSUIPC7 in the client machine
To install FSUIPC7 on a client machine, create an DSUIPC7 folder (preferably not under Documents, Program Files, or any other windows-protected folder) and copy across the following files from your MSFS computer:
      FSUIPC7.exe
      FSUIPC7.key (if using a registered version)
You can also copy across your FSUIPC7.ini file, but it may be better to start afresh with this in your client PC.

 

3. Configuring SimConnect on the Client computer
To configure SimConnect on the client PC, create a file called SimConnect.cfg in your FSUIPC7 folder on the client machine with the following contents:

where Your Local MSFS PC Address is the same address as used in the client configuration (and the port also must, of course, be the same as the one used there).

 

4. Configure FSUIPC7 to run on the Client computer
If you have copied across your FSUIPC7.ini, open this in an editor and removed any unwanted assignments/profiles.
If you have not copied across your FSUIPC7.ini, run FSUIPC7 once and exit - this will create a default FSUIPC7.ini file for you.
Open this file in an editor (e.g. Notepad++).

Under the [General] section, add the following ini parameters:
    RunningOnClientPC=Yes
    UseSimConnection=0

and under the [WAPI] section (if using the FSUIPC7 WASM module on the MSFS computer) - create if necessary, also add the following:
    UseSimConnection=0

And that is all!

To use FSUIPC7 on the client machine, you must manually connect once MSFS is up and running.

For any issues or questions, please use/comment on this topic.

John

 

Hello everyone,

 

 My name is Thomas, I am new to the forum and if I am writing to you it is because I have a problem using FSUIPC on my second computer.

 

 In fact, I have two computers, one which runs MSFS and my B737 homecockpit and the other PC, which serves as an instructor station.

 

 I would like to use this computer to prepare my flights with PFPX. To do this, I have to use TopCat to send my flight plan to the first computer where it MSFS with the help of ProSim737 and PSU server but, TOPCAT asks me to use FSUIPC, so I found your message and I I tested and nothing. I have exactly the same message as @mcduffrobert and I don't know how to resolve this problem. I opened the ports on 7421, I deactivated the firewalls and still nothing. When I look in the log, it says that the software is looking for a file in the wrong folder. This file is a .cfg

 

 Good day,

 

 Yours truly.

 

 AFR7796

[John Dowson]

11 hours ago, AFR7796 said:

I have exactly the same message as @mcduffrobert and I don't know how to resolve this problem. I opened the ports on 7421, I deactivated the firewalls and still nothing.

So FSUIPC7 on the client PC cannot connect to MSFS? Did you configure your SimConnect.xml file correctly? Can you please attach your FSUIPC7.log and FSUIPC7.ini files as well as your SimConnect.xml file please and I will take a look.

11 hours ago, AFR7796 said:

When I look in the log, it says that the software is looking for a file in the wrong folder. This file is a .cfg

What log file? What cfg file?