bcars

Hi John: I think I have it resolved. I was using Notepad.exe as a test as RunReady it would not close, nor would wideClient. Watching ProcessExplorer, it seemed that when Notepad.exe was launched from WideClient, there were 2 subprocesses. One Notepad with no window title, and a 2nd with a window title. This would bear out your previous comments as well as the TechnicalDocument that if subprocesses, it would not work. Interesting when I run notepad from command line or from FileExplorer Open file with Notepad, only a single instance shows in ProcessExplorer. I changed to use a different program ( VisualSlickEdit) and ran vs.exe as Run1/Close1 and that seemed to work(both vs.exe and wideClient closed) I then added Notepad back as RunReady1 and it closed VS.exe but not notepad nor WideClient. Seems that if a Run1/Close1 it works fine. I then put my RunProsim.exe back in(no change to program) and it indeed closed and wideClient closed. So with FSUIPC with AutoShutdown=Yes and WideClient as AllowShutdown=App it is working. I ran several tests to re-confirm. In all cases, if wideClient does not close on its own ( from the DCBA message) Manually closing wideClient does still not close the Run/RunReady programs. Puzzling. I guess we can close this as working as coded, not necessarily as designed 🙂 Thanks for taking the time to add your suggestions and thoughts.

Hi John: One issue I found was that in wideClient I had specified autoshutdown instead of allowshutdown, so things were acting line allowshutdown=no. Didn't really matter. I tried the following combinations: Also used Process Explorer to watch the processes. The RunProsim does get launched as a sub process of WideClient. FSUIPC WideClient Result autoshutdown=Yes allowshutdown=yes as expected, 2nd pc shutdown allowshutdown=App Wide client shutdown, but program kept running allowshutdown=AppOnly neither wideClient nor program shutdown autoshutdown=Apps allowshutdown=Yes Wide client stays running, program closes allowshutdown=App program closes, wide client keeps running allowshutdown=AppOnly program closes, wide client remains open In all cases, (including case where allowshutdown is No) there is never an entry in the wideclient log that shows the program being terminated. (even when wide client closes it) As a test, I tried notepad.exe with same results (???) It launches different batch file on close. The startup Batch file invokes a monitor that waits until the Prosim system module has completely initialized and is ready to accept connections, before it launches the rest of the Prosim modules that handle the various display and ios component. (similar to the RunReady concept in fsuipc) The program is the exact same exe on both FSUIPC7 version and the WideClient version. Puzzling 🙂 Enjoy your Holiday. WideClient2.zip

Hi John It is a single process. A program i wrote. It launches a batch job( cmc /c) to startup prosim. When it closes, it launches a 2nd batch job. Pretty simple, Has config that has the name of a program or cmd to launch at startup, and one to run when it closes. As I said, the same process runs fine on fsuipc7 on sim computer. You could substitute Notepad as the program for wideclient. I'll try kill or last

Using MSFS2020 (Steam MSFS version = 11.0.282174.99) and Fsuipc7(Version 7.5.4) on primary pc,, WideClient (version 7.16) on 2nd pc I have setup the main fsuipc [wideserver] with AutoShutdown=Yes ( or Apps) and the wideclient with autoshutdown=yes ( or app, or appOnly) On both fsuipc and wideclient I have setup to run a program when MSFS is ready: [Programs] RunIf1=READY,HIDE,CLOSE,D:\Prosim737-V3\RunProsim.exe wideclient.ini [User] .... RunReady1=D:\Prosim737-V3\RunProsim.exe CloseReady1=Yes ( or Yes, D:\Prosim737-V3\RunProsim.exe On the fsuipc7/msfs PC everything works fine. The program gets started at the appropriate time ( msfs ready) and closes when MSFS is shutdown On the wideclient PC the program gets start at appropriate time, however it never gets closed. Running wideclient with debug I can when wideclient gets the shutdown signal from the wideserver, however it doesn't do anything with it. It doesn't close the started program nor does it close the wideclient window. I have to manually close the wideclient window(, then it closes the launched RunReady program. (WideClient log excerpt.... 797 e:\apps\visualstudioprojects\fsuipcwpfautoprosimmonitor <M1:L0:C1:H310> 797 E:\Apps\VisualStudioProjects\FSUIPCWPFAutoProsimMonitor\runprosim.exe <M1:L0:C1:H310> .... 91625 Received shutdown offset code = DCBA <M1:L1:C1:H311> 91625 FS closing down (param=DCBA), disconnecting <M1:L1:C1:H311> 91625 ********* Interim performance summary ********* <M1:L1:C1:H311> 91625 Total time connected so far = 76 seconds <M1:L1:C1:H311> The wideclient window now shows not connected ( trying to reconnect) and continues in that mode until I close the wideclient window. I must have some sort of configuration mismatch or setting that is not correct, but have tried several combinations. Even tried using a CloseAppsHotKey Logs and ini settings attached. WideFS-NoShutdown.zip

Pete: Thanks for the quick response and explanation. I had previously read the documentation on the PFC axis and how to assign values to the PFC virtual axis, however, I can't seem to find how to assign those to an axis/joystick in FSUIPC. Assuming the 3bb4 is simulated axis Y, how do I associate axis Y, Joystick X so I can assign that to the brakes and calibrate. Virtual buttons are not a problem, so do I need to assign those manually in the .INI file. Regular Axis assignment and calibration requires FSUPIC to be able to 'scan' the axis. Maybe what I am trying to do is not possible -- assign Shift B to simulate pressing the toe-brakes on virtual joystick X axis Y,Z ( just using symbolic values for the joystick and axis here just to distinguish a given joystick and given axis ( would probably be Y, Z ) Likewise, my goal was to have the single KeyStroke set values in two different variable ( might have to use LUA here ? ) Or can this be done via direct INI editing.

Pete: I am using FSX with Accelleration Pack and Prosim737. I have Saitek Jet pedals/brakes calibrated and working in FSUIPC. The Prosim package looks at the offsets 3416 and 3418 for the left/right brake pressure in order to disarm the autobrake. This, too, works fine. On my test machine, I don't have joystick for rudders/brakes and have to rely on the Keyboard. My problem is that the FSX Brakes ( period "." ) or assigning a switch in FSUIPC to brakes does not seem to update those two variables and so Prosim is not seeing the brake pressure (it uses a value > 2000 to detect brake pressure). These offsets are read only so I experimented by trying to have a Key set the values ( 0x0BC4(S16)=0x3F00 and 0x0BC6 and set to 0x00000000 on keypress release, but it doesn't appear to update 3416 or 3418. This is the same offset that the default FSX Brakes (keyboard period) Uses (I am monitoring offsets to screen) What I notice is that if I have FSUIPC set the fixed value of x3f00 into 0bc4 that it sets the value, but then when I release the key, instead of immediately setting to zeros it gradually releases pressure to zero? So it is acting as if I had pressed and held the period, then released the key. I also tried using offset 0C00 and 0C01 to no avail. So my question is What causes offsets x3416 x3418 to be updated other than axis controls? Is there a way to simulate the brakes axis using a simulated joystick or some other way to influence the brake pressure values. Thanks Bruce

Pete: Windows XP / FSX / Registered FSUIPC / WideFS I am having a problem trying to use a USB Joystick axis from the client pc. From FS machine, Using the Buttons+Switches menu, I can see and assign joystick buttons from the remote client, however I cannot get it to recognize any axis (from axis Assignments) I have calibrated the joystick with Windows Game Controller on the client PC. I checked the logs and I can see the button scan and send from the client and the server receives it (this is confirmed by the Menu on FS showing button 5 from joystick 2000 (1st client) However I don't see any traffic for Axis. Am I missing something in doc, or are joystick axis on remote clients not supported ? (only buttons )

I just tried the following and it works fine with the PMDG 737. I assigned the Mixture 1 Rich to the On position and the Mixture 1 Lean to the off position.This DOES start the fuel flow at 20% N2, and can also be used to idle/cutoff to stop the engines. However, the Idle/Cutoff switch on the PMDG 737 throttle quadrant does NOT actually move (only if you mouse click the control) However, it does not matter what position that switch was in..(Unless you physically click it, it doesn't move). I happened to use the two independant throttle controls on a spare Saitek AV8R joystick to simulate the Fuel Cutoff/Idle toggles of a normal 737 throttle quadrant for engine 1 and 2. I assigned the Z axis to Mixture 1 Rich with a null zone such that when passing through 3/4 travel (0 ) it sets it to Mixture 1 Rich, when Leaving that zone, it sets the Mixture 1 Lean. Works like a champ.

Pete Sorry, I mistyped when I said WideView server, what I meant was the WideFS server. When your server opens a Port, and you do NOT specify a specific interface (ip address) or you specify ANY (the default), then the socket is bound to the port on ANY address that is on the machine (local computer) That means if you have 192.168.21.100 , and 192.168.22.100 (two nic's whether on the same subnet or not) your Port (9000 ) would be bound to both. IF, however, you specify a specific address on the socket bind, then the socket/port will only be bound to that Specific address. This is how you can have mutliple HTTP servers on the same machine both listening on port 80, but on different Interfaces. So when you define the socket and specify the port, you can also specify a discrete IP addess

Windows XP Pro, FSX, FSUIPC 4 I have multiple network interface cards installed. One is for my local network and allows access to the internet as well. I do not allow file/printer sharing on this interface and it is firewall protected via Router ACL. The 2nd interface is for the protected FlightSim network. This is where I will run Project Magenta, but don't want its required File shares to be available from the other subnet. I have WideFS server on the FSX machine and WideFS on two other machines to drive PM components. I want to restrict the WideView Server to listen on ONLY one IP address (not all addresses as is the default , I believe ) I have configured WideFS client to point to the WideFS server(FSX machine ) and this works fine, but I don't want the WideFS ports to be available on the Other interface. Is there a hidden (hint) config parm I can add to the fsuipc.ini file for WideFS interface=192.168.x.x ???