Jean-Claude

Thank you for this clarification John.

As a follow-up and for your information, after trying your suggestion, I still could not re-establish the settings of my previous PC on the new one. I ended up with a mix bag of Go-Flight saved settings that could be re-used in full (and that saved me a lot of time!), but all axis had to be reset individually and this for each aircraft. Something I cannot understand is why when I select Axis, I cannot get out of the "Aircraft specific" mode, in other words, if I have loaded the CJ4 and want to set the yoke and rudder values for all airplanes, I cannot untick the aircraft specific box (it is grey), hence I have to reset those axis for each plane individually instead. I believe this is probably the consequence of having all my previous aircraft saved with values that cannot be used with the new setup although my flight hardware remains the same. If I delete the saved aircraft, I will/may loose my Go-Flight modules as well.

Thank you for your help John, it is really appreciated. I suspect that the way (order) each piece is connected to the PC via their respective USB is probably the cause of these swaps! I will try nevertheless to reorder them, if I can, following your instructions. No specific drivers for the PFC devices. Again many thanks, I will report after I try.

Thank you for your prompt reply and your offer to review my files, here they are as attachment as requested. With kind regards. FSUIPC7.ini (new PC) FSUIPC7.ini (old PC) FSUIPC7.log (new PC)

I re-installed MSFS to a new PC and installed FSUIPC7. I would now like to transfer all my FSUIPC data contained on my previous PC to the new FSUIPC.ini file. I copied and paste the KEYS and AXES of my previous PC FSUIPC.ini file to the new one. However, in MSFS when I click on the FSUIPC "aircraft specific", my list of add-on is there, but when I select a specific add-on, none of my controls settings work. Is there another procedure to achieve this please? Thank you.

If Microsoft allows it, simply put the related links as part of your instructions: ... Un-install all previous versions of Microsoft Visual C++ Install the following two packages: X86: https://aka.ms/vs/17/release/vc_redist.x86.exe X64: https://aka.ms/vs/17/release/vc_redist.x64.exe And for those smart enough to understand what this is all about, add the link to the page (as you have done in your instructions). Thank you and best regards.

Because when you go to that Microsoft page (your link) none of the download link listed has the name of the one you need to download! Not to mention a verbiage of which I have a very limited understanding if any... i.e.: So I went ahead and downloaded the first two and, apparently, FSUIPC is now operational, thank you. I will now need to retrieve all my settings saved on my previous computer. Thank you anyway for your product, I can only guess how upsetting it must be for you to rehash so often the same things, you are in a very specialised area producing software meant for most simmers but with only a few being able to squeeze the entire substance of your brilliant work, my usage of FSUIPC is very limited but so helpful. With best regards.

I am having a similar issue, I bought a new PC and re-installed every programmes with no problem whatsoever, the only important difficulty I am facing is FSUIPC cannot run because of this VCRUNTIME.dll. I read the instructions in FSUIPC, went to the Microsoft forum first, read the instructions, then downloaded the necessary 2015 files and installed them. Restarted the PC. No success, FSUIPC wont start. On this new PC (with Windows 11 Home edition), I noticed that already installed are Microsoft Visual C++ 2010 (32 and 64 bits), 2013 and now 2015, 2017 is not there, when going to the download page, only versions up to 2015 are available (I must say that I am somewhat confused by the complexity of the presentation which is less than clear for non-initiated like me). There is also a 2022 version which I installed as well, to no avail. I uninstalled FSUIPC, re-installed, registered and everything is OK, except that when I click on the FSUIPC exe file, I am still getting this message of error. Would you be so kind to please clarify the road ahead with the understanding that you are talking to an old computer illiterate person who was a pilot (hence my interest for simulators) but not a programmer! I thank you for your assistance.

Thank you John, I will re-download FSUIPC to retrieve this file.

I have exactly the same issue which started only after WU8, I never had that in one year. I run W11 and would like to have access to the ReadMe file supposed to be located in my FSUIPC folder but cannot find it (I have the latest version of FSUIPC released in March). I do have plenty of documentation such as the manuals but no ReadMe file. Would you care to please confirm the exact name and location of that ReadMe so that I may resolve this issue. Additionally, on at least one occasion, I started MSFS but FSUIPC was not started automatically, I had to do it manually from the exe file. Thank you.

Thanks for your understanding Pete! It is always a pleasure to get the impression that a client is read carefully or listened to... Internet age I guess. Not mine anyway. Happy landings!

Thank you for the bold capitals in your message indicating I did something wrong, which I was fully aware of, even though English is not my native language and I have been posting since 2003 on this forum. When I tried to sign-in on this forum yesterday, my password was rejected (although it remained the same), and finally my account was blocked, until I reactivated it with a new password. I was then presented with a selection of options to post my question, but "Support" was not part of them... Hence my frustration and deliberate "mistake". So I should have been the one using bold capitals in red in my post!!! My "contribution" shall stop there.

As per title, each time (I really mean systematically) I close P3D, I am getting this error message showing the faulty module as "FSUIPC.dll unloaded", in my "view all problem reports". If I had no other problems, that would be fine, but each time I have a real P3D issue to analyse. I have to first eliminate one by one my FSUIPC BEX64 messages for each of my previous flights, and to do that I have to open each and everyone of my P3D error reports so as to know which one is the real culprit. When typing BEX64 in the search I did not get any return so it would appear my case is isolated. Has this been reported before and can a cure be found please? My FSUIPC version is 5132, I am using Windows 10 Home with the latest updates, and P3Dv4.3.2925520. Thank you. Jean-Claude

Many thanks Thomas, this is most helpful!

I have used FSUIPC with FS9 and FSX for years, but with my recent installation of P3Dv4 and FSUIPC 5, I cannot use the "key mapping" for my GoFlight modules (I have ten of them) as I did with the previous two sim and FSUIPC versions. When I select the relevant page on FSUIPC "Buttons & Key presses" and press any GoFlight button, they are not identified by FSUIPC. All my GF modules are correctly installed and identified by Windows 10 64 home edition in the Device page, and configured in the GF latest software 2.28.0. For example the 2 GF166 radio modules, the landing gear module, the GF TQ6, the transponder, two sets of 8 switches and one set of push buttons work flawlessly with P3Dv4. However, I would like to "map" my autopilot module and one set of rotary buttons but failed to do so because of this apparent communication problem with FSUIPC 5. Could you please guide me to resolve this please? Jean-Claude