Search the Community
Showing results for tags 'client'.
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
Hi! I try read the 0x0AF4 offset (Fuel weight as pounds per gallon; size: 2) and the simulator write, the fuel weight is 6.7 Lbs/Gal, the Client read in 6 Lbs/Gal. It's my code: Offset<double> fuelWeight = new Offset<double>("fuel", 0x0AF4); How I can read the real weight value in double/float/decimal? The double result is Which type should I use to work in correctly? Thank you!
I'm running P3D v3.4 and STB (versions unknown but they are the latest after a check) on a server / client setup. I'm using a utility that checks the departure time for Ai aircraft and if that time is more than 90 mins ahead it deletes them. Well, they don't get deleted immediately but they are removed from the gate they occupy and placed within the 40nm 'bubble' in P3D. Several minutes later they are deleted. I'm doing this because when I arrive at airports like LPPT all the terminal gates are occupied by Ai and many won't be departing for several hours. But the problem is STB is not updating its display to reflect these changes. I even closed the client and server applications and started them again a minute later. The same Ai aircraft were shown on STB but they didn't actually occupy the gate STB showed them at. Can you offer any reason why this is happening please? Shouldn't STB refresh its data many times a minute? What is the default refresh time? The server runs on a i7 4770K and the client on an i5 so plenty of processing power.
NEVER MIND. I kept looking and found a bad installation of WideClient. Reinstalled and we are running again. I have been running FSX SE under Windows 10 and FSC9 on the same computer with good success. Then I purchased WideFS7 and ran FSC9 on my laptop (also W10). It worked fine the first couple of times fine (and without any extra sharing and mapping). Now it will not connect (the #2 message). I followed the instructions and shared and mapped the folders per the FSC documentation. Still won't connect. I then mapped my primary computer's C: drive. Still won't connect. I ran the DB manager from my client computer and that was successful. When running FSX it says WideFS7 is running and "waiting for clients." WideFS log shows connecting to client computer okay. I've worked and researched for many hours and just can figure out what is wrong. Your help will be appreciated. What other information do you need, if any? And one more thing, I am on a wireless network which seem to work okay before. Steven