John Dowson

There are two methods to get P3D to use FSUIPC - either using an add-on xml file or by using P3D's DLL.xml. By default, the installer uses the first method. If having issues with this, then you could try using the 2nd method, by unchecking the add-on.xml component when selecting the components to install. However, you shouldn't need admin privileges for the add-on.xml. This is created in an FSUIPC6 sub-folder of the Prepar3D v5 Add-ons folder (or v4 for P3Dv4), which is usually created by P3D under the user' %USERPROFILE%\Documents folder. So, first check that folder exists. I have also attach an example add-on.xml (you will need to change the Path to point to the location of your FSUIPC6.dll: add-on.xml Further details on this can be found here (for v4, v5v is the same except for the folder name): https://www.prepar3d.com/SDKv4/sdk/add-ons/add-on_packages.html If using the DLL.xml method, the DLL.xml file is created (or updated if it already exists) under the user' AppData\Roaming\Lockheed Martin\Prepar3D v5 folder. The format of this file is defined here: https://www.prepar3d.com/SDKv4/sdk/add-ons/add-on_configuration_file_formats.html That folder should be for the add-on.xml file only (is it there?). If you installed FSUIPC6 in that folder, please re-install (this will uninstall the current installation first) and select a non-windows protected folder (i.e. not under Documents and not under Program Files or any other windows-specific folder). Once you have done that, check the add-on.xml file is correct. If it is and FSUIPC isn't loading, switch to using the DLL.xml installation method. You can attach the InstallFSUIPC6.log file for each each installation type (add-on.xml and dll.xml) id you continue to get issues and I will take a look. John

You have assigned a single axis to THROTTLE_AXIS_SET_EX1 and THROTTLE2_AXIS_SET_EX1. This is not correct - either assign to THROTTLE_AXIS_SET_EX1 only, or assign to both THROTTLE1_AXIS_SET_EX1 and THROTTLE2_AXIS_SET_EX1. The assignments in the referenced post were for using two separate throttle axes, one for throttle1 and one for throttle2. If you are only using one axis, you will only have one assignment. Not sure why you have an FSUIPC profile called FSUIPC - you should change this or remove it. Change this to This will catch more variants, i.e. when using other liveries. Any further issues, please attach your full FSUIPC7.ini file rather than pasting extracts. Thanks, John

First, it looks like the GUIDs of your JAY Rudder and Redbird Alloy YK1 changed at some point, You re-assigned to these devices again when this happened. You don't need to do this - it is easier/quicker to update the [JoyNames] section to handle such changes. You don't have to do anything now, but remember this next time - or post your ini here and I can update for you. For now, I have cleaned your ini to remove these missing devices and the assignments to them - please use the attached ini: FSUIPC7.ini For the CRJ, you need to assign with 'Send to FS as normal axis' and use the Throttle1 Axis Set Ex1 and Throttle2 Axis Set Ex1 controls/events. You should create a specific profile for this - i.e. in the axis assignment tab, check the Profile Specific checkbox, create a new profile (you can import current axes assignments into the profile), and then clear the throttle assignments and then assign to those controls. You should then go to the calibration tab, again check the Profile Specific checkbox, and then re-calibrate the throttles on page 3. Once that is done, you should be able to calibrate further in the EFB, if needed. I can't see how throttle1 and throttle2 can be different as the assignments and calibration are the same. However, I suggest you also create another profile for the 737, as many controls are also very different for this aircraft. If you have issues with the throttle then clear your current throttle assignments and assign again using 'Send to FS as normal axis' and use the Axis Throttle1 Set and Axis Throttle2 Set controls. Again, after assigning go to the calibration tab and check the Profile Specific checkbox and check the throttle calibration. If you still have issues, please attach your updated FSUIPC7.ini file. John

Please first check that there is an FSUIPC7.key file in the installation location (and this hasn't been renamed to FSUIPC7.key.txt, which sometimes happens). Try with both key files - the trial one and the one containing your license (the one I sent you via a PM). Any issues, please show me / attach your FSUIPC7.log file. For all auto-start issues, please see

I gave instructions in the message I sent you - the FSUIPC7.key file goes in your FSUIPC7 installation folder, the one you selected during installation, and where the FSUIPC7.exe resides...

Correct trial license has been uploaded, but you may as well try the licensed I PM'ed you.... John

Corrected - sorry about that. John

That is not the trial license...I mistakenly uploaded the exe rather than the key file,.. correcting now, will be available in 5 mins or so....

No, sorry - I will correct.....

I have checked your key details and they are fine here. There are only two reasons that I know of in many years of people reporting this issue: - you are not entering all 3 parts of your key details correctly - the VC++ redistibutables are not installed or up-to-date Please double-check both, and also try the trial license, The trial license will not validate in the installer, but if you get issues running FSUIPC using the trial license then this is a sure sign that you have issues with your VC++ redistributables. I will also PM you a key file that contains your key, but please try the trial license / key file first and let me know if FSUIPC runs ok when using that, John

Please let me know your order number and I will check it - do NOT post your license details. In the mean-time, you can use the trial license, available here. I always recommend that you should try the trial license before purchasing, especially for new users to FSUIPC. John

The license has been updated, valid until 1st March 2023. John

For offsets, please see the FSUIPC7 Offset Status document - the state and use of offsets is shown in that document. As 0x7C50 is also used for setting lvars, activating hvars and executing calculator code, the prefix is needed so that FSUIPC knows how to interpret the following string. Cheers, John

The preset is only listed for the dev version (see https://hubhop.mobiflight.com/presets/), so yes, switch to the dev version and try with that,,, John

What version of the A320 are you using? That preset is listed for the A320-Dev version only... John

I cannot see any preset being logged there - as the documentation states: Also, most presets to not include spaces (but some do!) - they use underscores '_'. These are replaced by spaces to display in the FSUIPC drop-down menus. So, this one: 208594 LUA.3: WT CJ4 AP ALT VAR DEC should be P:WT_CJ4_AP_ALT_VAR_DEC You can see the correct preset name in the events.txt file (or look in the MF Hun Hop site). John

This is not necessarily the case. Please follow the provided instructions and install the latest COMBINED redistibutable packages, as documented. John

As I said yesterday morning: John

I am sorry you feel that way, but I don't understand why you say this. Do you think I should accept any question in any post and in any sub-forum? The forums are not only for asking questions, but also a repository of previous questions people have asked to together, hopefully, with the resolution of the issue. This can then be used by others who encounter a similar issue, and if a post is properly titled and in the correct sub-forum then this can be found more easily... I am spending almost all of my time on support these days, and around 70% of support requests have been asked before - and usually not just once but many times. The more I can reduce support, the more time I can spend on improving the software - and documentation. Maybe even one day I will get time for some recreational flying - it seems that I only fly these days fir testing or support issues.... I am (always!) trying to reduce the time I spend on support but this seems impossible - it seems that hardly anyone consults the documentation before posting, and even fewer people search the forum for similar issues. All I am trying to do is to help people to use the provided resources how they are intended to be used, and for the good of all. I do not mean to give offense or to be rude. And I can appreciate that new users to FSUIPC and to the FSUIPC forums sometimes (mostly!) don't understand how the forums work, and so I have to continually explain this to newcomers. But I do not expect to have to do this to people who have used the forum many times before.... There is also a sticky-topic in the main forum called READ BEFORE POSTING FSUIPC PROBLEM REPORT, not that anybody reads that either.... John

License is per user, so no need to buy twice. John

I'm away in 10 mins for the weekend - I will update the license on Monday morning... Also see the section on handling VRInsight devices in FSUIPC in the Advanced User guide, and also the separate document on lua plug-ins for such devices. You may not need LINDA, but maybe easier if it has an existing profile you can use. John

Are you using FSUIPC in a commercial and/or multi-user environment? The FSUIPC license is for a single user only (multiple installations allowed). For all other license requirements, you need to contact me to discuss requirements. I would suspect so...FSUIPC is meant to be installed for a single user. Please clarify how you are using FSUIPC and P3D - and what type of P3D license you have (is it a commercial license)? Probably better to discuss this via PM/DM. John

Of course this is the wrong place - what does your question have to do with the PMDG 737 Leds for A/P P/RST, A/T P/RST, FMC P/RST, that this topic is about? I am not going to answer your question here (or even read it fully). Please find a relevant topic, and if you cannot find one then create a new topic with a relevant title. I will delete your comment (and my response) from this topic in a few days. You have over 44 posts already and so you should really know how and where to post by now.... Note also I am away this weekend, so will not be responding now until Monday. John

Your registration key is the one in the SimMarket email, and also available from your SimMarket account. All three fields of the registration details (name, address, key) must exactly match the ones specified in your purchase email and SimMarket account - best to copy and paste your details. If you have entered the details correctly, then it could be that your VC++ redistibutables need updating. You can download the latest combined redistributable package from the following site: https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist It is recommended to uninstall any of the 2015, 2017, 2019 or 2022 VC++ redistubutables that you already have installed (using the Windows App management panel), and download and install/run both the x86 and x64 packages from that link. John

Just looked at your log file. Brake controls/events are logged as this is what FSUIPC is seeing - doesn't mean that they are assigned in FSUIPC. Every event that is used/seen by simconnect is logged, depending on the logging you have activated in FSUIPC. As you have logging for Axes Controls activated, that is what is logged. If you are trying to determine the events for buttons and switches, you should turn off/uncheck logging for Axes Controls, and set/check logging for Events. Your log also shows no presets loaded: Did you delete or not install the events.txt file? This is the file that holds the MF presets. You can either download it from https://hubhop.mobiflight.com/presets/ using the Export Presets button (you need to create an account, if you don't already have one, and login to be able to do this). Alternatively, re-install FSUIPC7 with the events.txt file. John Later: you can use the attached one - save it to your FSUIPC7 installation folder and restart FSUIPC7 and you should see 9509 presets: events.txt