rb2111

Hi, Sorry for the delay. It was the Fenix bootstrapper, I turned it off and it all springs to life! Interesting I tried it on my other machine and the bootstapper only uses 1 sim connect connection. Any ideas why mine is using so many ?

Hi John, Please find attached the sim connect log and fsuipc log. I appear to have the issue today where FSUIPC wouldnt connect. I started the program manually and disabled the running of those programs as you said. Logs below: ********* FSUIPC7, Version 7.3.11 (5th October 2022) by John Dowson ********* MS Store installation detected: Checking for FS path in 'C:\Users\Rhys\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt' FS path found = D:\Microsoft Flight Simulator\ WebSocket server found: D:\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe Windows 10 Home 64 Bit reported as Build 19043, Release ID: 2009 (OS 10.0) Reading options from "D:\FSUIPC7\FSUIPC7.ini" Checking the Registrations now ... User Name="Blanked for privacy (Can supply to you John)" User Addr="Blanked for privacy (Can supply to you John)" FSUIPC7 Key is provided WIDEFS7 not user registered, or expired 156 System time = 16/10/2022 14:33:14 156 FLT path = "C:\Users\Rhys\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\" 172 Not allowing calibration when not assigned with 'Send direct to FSUIPC Calibration' 297 ------------------------------------------------------------------- 312 Preset file 'D:\FSUIPC7\myevents.txt' not found [info only] 312 8041 Calculator Code presets have been loaded and are available for use 390 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 406 FS path = "D:\Microsoft Flight Simulator\" 406 ---------------------- Joystick Device Scan ----------------------- 406 Product= GoFlight YOKE 406 Manufacturer= GoFlight Technology Inc. 406 Vendor=09F3, Product=0029 (Version 0.1) 437 GUIDs returned for product: VID_09F3&PID_0029: 437 GUID= {D78B4A80-3948-11EA-8002-444553540000} 437 Details: Btns=13, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255 437 Product= AVA FLIGHTSIM 437 Manufacturer= Leo Bodnar 437 Serial Number= B43835 437 Vendor=16C0, Product=05BA (Version 1.36) 437 GUIDs returned for product: VID_16C0&PID_05BA: 437 GUID= {D7ACB530-3948-11EA-800F-444553540000} 437 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U4095,V4095,X0,Y0,Z4095 437 Product= <not readable at this time: maybe device disconnected?> 437 Vendor=1A86, Product=E026 (Version 0.0) 437 GUIDs returned for product: VID_1A86&PID_E026: 437 GUID= {F262D910-737E-11EB-8001-444553540000} 437 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1,Y1,Z0 437 GUID= {F2630020-737E-11EB-8002-444553540000} 437 Details: Btns=8, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1,Y1,Z0 453 Product= Saitek Pro Flight Rudder Pedals 453 Manufacturer= Saitek 453 Vendor=06A3, Product=0763 (Version 1.1) 453 GUIDs returned for product: VID_06A3&PID_0763: 453 GUID= {D7A4ED00-3948-11EA-800B-444553540000} 453 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 453 Product= FootSwitch1-F1.8 453 Manufacturer= PCsensor 453 Vendor=0C45, Product=7404 (Version 0.1) 453 GUIDs returned for product: VID_0C45&PID_7404: 453 GUID= {B24D2850-5186-11EA-8001-444553540000} 453 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 453 ------------------------------------------------------------------- 4844 WARNING: Joystick ID 3 is duplicated in Registry 4844 WARNING: Joystick ID 3 is duplicated in Registry 4875 Device acquired for use: 4875 Joystick ID = 2 (Registry okay) 4875 2=GoFlight YOKE 4875 2.GUID={D78B4A80-3948-11EA-8002-444553540000} 4875 Device acquired for use: 4875 Joystick ID = 0 (Registry okay) 4875 0=AVA FLIGHTSIM 4875 0.GUID={D7ACB530-3948-11EA-800F-444553540000} 4875 Device acquired for use: 4875 Joystick ID = 5 (Registry okay) 4875 5=2 axis 8 button gamepad 4875 5.GUID={F2630020-737E-11EB-8002-444553540000} 4875 Device acquired for use: 4875 Joystick ID = 1 (Registry okay) 4875 1=Saitek Pro Flight Rudder Pedals 4875 1.GUID={D7A4ED00-3948-11EA-800B-444553540000} 4875 Device acquired for use: 4875 Joystick ID = 3 (Registry okay) 4875 3=FootSwitch1-F1.8 4875 3.GUID={B24D9D80-5186-11EA-8002-444553540000} 4875 ------------------------------------------------------------------- 5047 LogOptions=00000000 00000001 5047 Simulator detected 347812 === Hot key unregistered 347812 === Stop called ... 347812 === Closing external processes we started ... 348328 === About to kill any Lua plug-ins still running ... 349234 === About to kill my timers ... 349453 === Restoring window procs ... 349453 === Unloading libraries ... 349453 === stopping other threads ... 349453 === ... Button scanning ... 349453 === ... Axis scanning ... 349453 === Releasing joystick devices ... 349453 === Freeing macro memory 349453 === Removing any offset overrides 349453 === Clearing any displays left 349453 === AI slots deleted! 349453 === Freeing button memory ... 349453 === Closing my Windows ... 349453 === Freeing FS libraries ... 350453 === Closing devices ... 350453 === Closing the Log ... Bye Bye! ... 350453 System time = 16/10/2022 14:39:05 350453 *** FSUIPC log file being closed Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps Maximum AI traffic for session was 0 aircraft Traffic deletions 0 aircraft Memory managed: 6 Allocs, 5 Freed ********* FSUIPC Log file closed *********** Simconnect Log here https://drive.google.com/file/d/1I_jqqcyEgzHNkbpy2UUjC8s7bX3jge4H/view?usp=sharing As for Wasm I get this error https://prnt.sc/mEvXu46kht5A many Thanks

Hi John, Thank you. So I have checked the log and when it works fine there is no errors but when I have all the simconnect things I speak about open I get the below: 1361750 -------------------- Starting everything now ---------------------- 1361750 Starting WAPI... 1361750 [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.9.0 (WASM version 0.9.0) 1372187 [ERROR]: Failed on SimConnect Open: cannot connect: E_FAIL 1372187 **** No SimConnect events or states being received! Re-connecting now ... **** 1372359 SimConnect_Open succeeded 1372359 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 1372359 MSFS version = 11.0.282174.999 1372359 Initialising SimConnect data requests now 1372359 Maximum number of custom events available is 1024 (defined by ini parameter MaxNumberOfCustomEvents) 1372359 User Aircraft ID 1 supplied, now being used 1372406 Aircraft="Airbus A320 Neo Asobo" (using AIR file folder name 'Asobo_A320_NEO' for profiles) 1372422 User Aircraft ID 1 supplied, now being used 1372422 Aircraft="Airbus A320 Neo Asobo" (using AIR file folder name 'Asobo_A320_NEO' for profiles) 1372453 Starting WAPI... 1372453 [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.9.0 (WASM version 0.9.0) 1382906 [ERROR]: Failed on SimConnect Open: cannot connect: E_FAIL 1382906 System time = 14/10/2022 01:25:14, Simulator time = 20:25:26 (00:25Z) 1425766 MSFS no longer running - exiting 1425766 === Hot key unregistered 1425766 === Stop called ... 1425781 === Closing external processes we started ... 1425781 About to KILL process "\Device\HarddiskVolume2\Program Files (x86)\Landing Rate Monitor\LRM.exe" 1425781 About to KILL process "\Device\HarddiskVolume2\Users\Rhys\AppData\Local\vPilot\vPilot.exe" 1425781 About to KILL process "\Device\HarddiskVolume2\FSUIPC7\LINDA.exe" 1426281 === About to kill any Lua plug-ins still running ... 1426437 === Closing global Lua thread 1427203 === About to kill my timers ... 1427406 === Restoring window procs ... 1427406 === Unloading libraries ... 1427406 === stopping other threads ... 1427406 === ... Button scanning ... 1427516 === ... Axis scanning ... 1427625 === Releasing joystick devices ... 1427625 === Freeing macro memory 1427625 === Removing any offset overrides 1427625 === Clearing any displays left 1427625 === Calling SimConnect_Close ... 1427734 === SimConnect_Close done! 1427734 === AI slots deleted! 1427734 === Freeing button memory ... 1427734 === Closing my Windows ... 1427734 === Freeing FS libraries ... 1428750 === Closing devices ... 1428750 === Closing the Log ... Bye Bye! ... 1428750 System time = 14/10/2022 01:26:00 1428750 *** FSUIPC log file being closed Minimum frame rate was 17.0 fps, Maximum was 24.2 fps Average frame rate for running time of 60 secs = 23.1 fps Maximum AI traffic for session was 0 aircraft Traffic deletions 0 aircraft Memory managed: 8 Allocs, 6 Freed ********* FSUIPC Log file closed ***********

Hi All, To start with I wanted to explain that I don’t think this is an issue with GSX itself and more one of simconnect. I discovered this problem however as a result of that error in GSX saying that it is not running when the program itself clearly is, from a bit of troubleshooting (including a combination of running the sim and coautl as admin) I have discovered the problem appears to be with sim connect and more specifically how many programs are using it. I fly with FSUIPC, VPilot (for vatsim) and GSX. Interestingly I’ve found that trying to use all these 3 at once doesn’t work for me, if I for example fire up FSUIPC and VPilot, both connect fine but when I used GSX I get the error that Coautl isn’t running. If I close one of those say FSUIPC then GSX connects fine and loads in, when I then go to start FSUIPC again it says it can’t connect to the sim. The same occurs with VPilot, I can run GSX and FSUIPC fine together but VPilot can’t detect the sim, close one of those 2 programs and hey presto VPilot detects the sim and connects. I’ve not noticed this before SU10 but I only purchased GSX after SU10 was released so can’t say if it’s a problem post update or not. Does anyone have any ideas or experienced the same issue ? It’s almost like simconnect is reaching a limit with the programs that it can talk to, I have a very good PC with high end GPU and CPU so not a system limitation problem. Any help would be great!

Does this require any additional tools to work ? am I missing something 😄 I have the PMDG and FSUIPC running, I have set the preset as above yet the control doesnt move. If I however set it via the rotorbrake fuction than the parameter it works. Do I need an extra program or something to have it work with the preset ? @John Dowson@adnanso