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

Flaps Increment Decrement T45C MSFS version Dino Cattaneo T45C for MSFS version 1.18 Using FSUIPC7 Buttons assignments Flaps Inc / Dec Example: from flaps Up Button assigned to Inc Flaps flaps go to full down rather than Half I e-mailed Dino Cattaneo about this problem and he replied: “For the record, there is no special code for flaps control in the T-45 - everything is handled at sim level.”

Hello Pete, I searched but did not find the zip file on my PC. I use FireFox. I also use Free Download Manager. I recently updated to WIN10 2004 You mentioned it was a very small file so maybe that is why Free Download Manager did not handle it and I got a screen refresh instead. I got the download by: right mouse click on the FSUIPC Makerwys.zip file then I selected Save file as. This brought up a screen to name, save and download the file (screenshot). Thank you for your help.

Hello Pete, Short video to show what I see. https://youtu.be/SPHfpUf7m5M

John, I was in this section: Flight plan converter, FxmlToFLT, FxmlToFlt.zip This utility, written and copyrighted by John Nunez in 2014, converts the new format "FXML" flight files into the older format "FLT" for use by unmaintained programs such as RCV4 (Radar Contact version 4). RCV4 provides restart options from saved flights but can only read the old FLT format. Make Runways utility version 4.91 MakeRwys.zip -- For P3D3, P3D4 and P3D5 , this version uses a Lorbi-SI's AddonOrganizer derivative called "LorbySceneryExport", (included with MakeRunways) to create a scenery.cfg fil it can use even when the scenery add-ons are distributed according to various XML file. Please see the document included in the MakeRunways ZIP! John, I just clicked on the zip you provided and the same thing, the page refreshed? Note : I I go to download this FSUIPC6 zip it works: FOR Prepar3D 4 & 5 (64-bit) Install complete FSUIPC version 6.0.9: Install FSUIPC6 This is the 64-bit version and is valid for Prepar3D version 4 from 4.3, and version 5.

I want to download makerunways 4.91: But when I click on the zip it just refreshes the additional programs page.

Also tried to fix (the OP's problem) in P3D forum: https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=137149https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=137149

I checked the FSUIPC v5.155 keys on my setup (P3Dv4.5HF2) and all ok.

John, I made notes from the forum posts then : "You will also need to remove and re-install FSUIPC. To do this, remove the FSUIPC5 entry at HKEY_LOCAL_MACHINE\SOFTWARE\FSUIPC5, and manually delete the F:\Modules folder." ** I backed up the entire current F:\P3Dv4\Modules folder (it has VRS TackPack data and my current fsuipc.ini files). ** Also, backed up my current fsuipc.ini file F:\modules folder (out of extra caution). ** Renamed current F:\ modules folder (in case I need it later). ** out of caution I also exported (as you mentioned) the reg key : HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4 and also exported the entire registry (a really large file). ** removed (deleted) the FSUIPC5 entry from the registry. "If you then re-run the FSUIPC5 installer, it should hopefully find your P3D installation and install in the correct place, as well as correcting your dll.xml file." Yes, FSUIPC v152 installer worked and installed ok as far as I can tell. I will use / test the new version setting up buttons in the VRS FA18E later today. The FSUIPC install log found my P3D folder : "Looking in registry for Prepar3D v4 install path: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4 Parameter"AppPath" ... >>> OK! FOUND Prepar3D v4! <<< ... AppPath=F:\P3Dv4\" Note: the FSUIPC installer did not have to look for reg entry SetupPath. And it updated my dll.xml as you said it would. Pete and John Thank for you kelp. Much appreciated.

Ok, Thanks for the follow up. I will have a look at it this afternoon.

Ok, Thanks again for the follow up. I first have to find out how to back up the Win10 registry. I will search the internet.