rb2111 Posted October 8, 2022 Report Posted October 8, 2022 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!
John Dowson Posted October 9, 2022 Report Posted October 9, 2022 As you are using MSFS/FSUIPC7, I have moved your post to the specific FSUIPC7 sub-forum. I have not heard of this issue before... There is a maximum number is SimConnect clients, which is defined by the maxClients parameter for each connection in your SimConnect.xml. However, this usually defaults to 64, which should be high enough, but there is a long standing issue where unused connections are not returned to the pool, so frequently re-connecting clients can exhaust the connection pool. For such issues, you should increase this to 128 or higher. You can check and increase this, but I don't think this will be your issue... You could activate SimConnect logging and check what errors you get there when this occurs. You can also attach an FSUIPC7.log file generated when FSUIPC7 cannot connect and I can take a look - I don't think it will tell me much but there maybe further logging I can add/enable to get more information. John
rb2111 Posted October 14, 2022 Author Report Posted October 14, 2022 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 ***********
John Dowson Posted October 14, 2022 Report Posted October 14, 2022 Can you please post a full log. Also, what version of FSUIPC are you currently running? A full log would tell me this....if not using the latest version, 7.3.11, please update and try again... From the log extract you posted, FSUIPC can get a simconnect connection but the WAPI interface cannot, which is strange. Multiple WASM clients shouldn't be an issue, but I will check this again in SU10 and get back to you. I also see LINDA running (or being killed) and LRM as well as vPilot. Could you also try running the WASM test client when you get this issue, both when it occurs with FSUIPC and other programs, and see if that can connect or not when you get this issue with your other programs, I have attached this for your convenience. John WASMClient.exe
rb2111 Posted October 16, 2022 Author Report Posted October 16, 2022 (edited) 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 Edited October 16, 2022 by rb2111
John Dowson Posted October 17, 2022 Report Posted October 17, 2022 On 10/16/2022 at 3:43 PM, rb2111 said: As for Wasm I get this error https://prnt.sc/mEvXu46kht5A I cannot see this, but it doesn't matter for now. On 10/16/2022 at 3:43 PM, rb2111 said: Simconnect Log here https://drive.google.com/file/d/1I_jqqcyEgzHNkbpy2UUjC8s7bX3jge4H/view?usp=sharing The log is interesting...first it shows an error starting FSUIPC7: Quote 0.80836 Exe Launch Failed: GetLastError=0x000002E4 Path="D:\FSUIPC7\FSUIPC7.exe" CommandLine="-auto" Windows error 0x000002E4 indicates that the requested operation requires elevated privileges. Have you set FSUIPC7 to run with Admin privileges, or are you running MSFS with admin privileges? Note that MSFS and all clients must be ran at the same privilege level. Please check that you are doing this - either running everything with admin privileges or everything without. Running with mixed privilege levels will cause connection issues. This is also interesting from your SimConnect log file: Quote > 709.41796 [320, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.42909 [321, 1]Open: Version=0x00000005 Name="fsdt-msfs-bridge" > 709.43609 [322, 1]Open: Version=0x00000005 Name="FSUIPC.LVAR.WASM" ... > 709.45038 [323, 1]Open: Version=0x00000005 Name="FlightSimIOModule" ... > 709.45985 [324, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.47438 [325, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.48169 [326, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.49171 [327, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.50289 [328, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.51242 [329, 1]Open: Version=0x00000005 Name="Request Data" ... > 709.52240 [330, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.53389 [331, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.54376 [332, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.55002 [333, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.56012 [334, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.57024 [335, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.58604 [336, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.59536 [337, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.60991 [338, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.62224 [339, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.63421 [340, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.64270 [341, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.65183 [342, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.66092 [343, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.68128 [344, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.69150 [345, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.70384 [346, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.71374 [347, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.72739 [348, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.74287 [349, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.75307 [350, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.75918 [351, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.77210 [352, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.78536 [353, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.80084 [354, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.80875 [355, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.81599 [356, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.82529 [357, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.84346 [358, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.85323 [359, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.86456 [360, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.87750 [361, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.88710 [362, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.90064 [363, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.91256 [364, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.92436 [365, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.93223 [366, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.93799 [367, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.94811 [368, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.96006 [369, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.96951 [370, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.97892 [371, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.98814 [372, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 709.99573 [373, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 710.01032 [374, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 710.01752 [375, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 710.03079 [376, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 710.04874 [377, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 710.05993 [378, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 710.07518 [379, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 710.08881 [380, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 710.09972 [381, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 710.10823 [382, 0]Open: Version=0x00000004 Name="FenixBootstrapper" > 710.12056 [383, 0]Open: Version=0x00000004 Name="FenixBootstrapper" So 59 connections are being used by the Fenix bootstrapper, out of a maximum of 64. There are also many exceptions reported in the SimConnect log file, all from the FenixBootStrapper. Could you please temporarily remove the Fenix and try without this to see if that is causing your issue. Also check the privilege levels, as previously indicated. Thanks, John
rb2111 Posted November 12, 2022 Author Report Posted November 12, 2022 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 ?
John Dowson Posted November 13, 2022 Report Posted November 13, 2022 No, sorry - that is a question for Fenix support. John
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now