von

Desktop, lower right corner, show hidden icons. Task Manager, left side, select Details and FSUIPC will be in the list if it is running (screenshot). Note: If you use the FSUIPC Batch file to start FSUIPC/MSFS then you need to disable (not use that) so you can choose when to start FSUIPC.

Right. I was wondering in your case you may be starting FSUIPC automatically with MSFS? So I would further ask : Can you try removing the FSUIPC edit then waiting until MSFS has fully loaded (not at e.g. the Dunes screen) to the Welcome / aircraft selection screen before starting FSUIPC to see if GSX (and other things) still have a problem or are working properly?

No, I quit using GSX few years ago. However, I do have PMDG for the test. Have you tried removing the FSUIPC edit then waiting until MSFS has fully loaded (not at e.g. the Dunes screen) to the Welcome / aircraft selection screen before starting FSUIPC?

For my first test as I previously mentioned: I just downloaded and installed FSUIPC7, Version 7.4.10 No edits to the ini file. Started FSUIPC (I do not use the FSUIPC’s Batch to auto start MSFS). Started MSFS. Took 140 seconds to get to the Welcome / aircraft selection screen. Selected PMDG 737-600 at KDTW. Took 90 seconds to load the flight. Looks good. Exited MSFS. Posted the simconnect lines in the LOG. Note : Next test with the edit in the ini file no problems in the Log. For my last test with Version 7.4.10 I rebooted the PC. Removed the edit from the ini file (back to default version 10 ini now). Started MSFS. Waited for it to load to the Welcome / aircraft selection screen Then started FSUIPC. Selected my aircraft. Exited MSFS. No problem in the Log. So, looks like the quick solution without FSUIPC edits is to just start FSUIPC after MSFS loads.

I could just forget the edits and wait for MSFS to fully load. Then start FSUIPC, correct? That way I would never have to be running startup timing tests on my two PC's.

I just downloaded and installed FSUIPC7, Version 7.4.10 No edits to the ini file. Started FSUIPC (I do not use the FSUIPC’s Batch to auto start MSFS). Started MSFS. Took 140 seconds to get to the Welcome / aircraft selection screen. Selected PMDG 737-600 at KDTW. Took 90 seconds to load the flight. Looks good. Exited MSFS. Log file information: 281 ------------------------------------------------------------------- 297 LogOptions=00000000 00000001 297 Manually started with DetectToConnectDelay=1 297 *** FSUIPC WASM module not detected - not adding WASM menu 30094 Simulator detected 92063 **** SimConnect open event not received in required time limit: Re-connecting now... 97063 **** SimConnect open event not received in required time limit: Re-connecting now... 102063 **** SimConnect open event not received in required time limit: Re-connecting now... 107063 **** SimConnect open event not received in required time limit: Re-connecting now... 112063 **** SimConnect open event not received in required time limit: Re-connecting now... 117063 **** SimConnect open event not received in required time limit: Re-connecting now... 122063 **** SimConnect open event not received in required time limit: Re-connecting now... 127063 **** SimConnect open event not received in required time limit: Re-connecting now... 129578 SimConnect_Open succeeded 129578 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 129578 MSFS version = 11.0.282174.999

One additional quick test: Try this: Do not use FSUIPC's start up batch file or manually start FSUIPC before starting MSFS. Start your PMDG flight in MSFS. Then manually start FSUIPC (with the Autosave option). Results?

I tested twice. All ok on my setup with your new version.

I sent you a Message to let you know there were problems with the FSUIPC forum. At the time I did not know if the problem was on my side or the FSUIPC server side. Maybe you could have verified at that time and then you could have contacted SimFlight seeing it is your forum. I sent a second PM because I did not get a reply to the first PM. I will give the new FSUIPC7.exe a test today. Thanks.

Image upload failed and posting in the forum failed. Still having problems with the FSUIPC server. I sent John a PM yesterday but no reply yet. Tried to send another PM msg but that also failed.

here is a screenshot: Here are screenshots. Image upload failed and posting in the forum failed. So I am trying to post again with links: https://i.imgur.com/seaQMBK.jpg https://i.imgur.com/MLe3wtw.jpg

When I quit MSFS (1.19.8) I see FSUIPC7 (7.2.9) .dmp files in this crashdumps folder: C:\Users\myname\AppData\Local\CrashDumps Are they indicating an error(s)?

I have several saved profiles for my devices e.g., CH pedals, Thrustmaster Warthog , Thrustmaster Airbus. All should use Flaps Inc, Dec. The reason I posted those images was to show what I wanted sent to the sim when I moved the switch on the Thrustmaster Warthog. Just to verify if it is ok to send images that I think would be helpful? All my profiles in the sim should be blank so fsuipc controls the functions sent to the sim. Because throttle, ailerons ect. were all working I assumed my profile was ok except for the flaps. My ini file should show I never select Flaps Up or Down. For all aircraft in all my profiles and FSUIPC I select Flaps Inc / Dec. Is that what you see in the ini file I sent? You mentioned: "Also, your flaps in/dec are assigned to different buttons in different profiles." I now went and found that the profile in use was “MSFS default” for Thrustmaster Warthog Throttle instead of the required blank profile that I had set up long time ago for FSUIPC. The Thrustmaster Joystick profile was correct (not the MSFS default). Maybe this happened after the last MSFS Update. Anyway, I selected my blank profile and now the flaps are working. Thanks for your help.

What does the ini file I sent show?

John, Here is the ini and log: FSUIPC7.logFSUIPC7.ini