John Dowson

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

Of what? What have brakes got to do with this? Can you please explain what your issue is if you would like me to assist you... John

Did you try the preset I mentioned, or is that for something else? Did you not see anything in the logging console when you set the started in the virtual cockpit? You should ay least get familiar with logging to determine controls/events used, and how to search for and use presets. Both of these things are (or should be!) quite easy to use... But there is also no problem mixing assignments between MSFS and FSUIPC7. Use wharever works.

The FSUIPC7.log is created each time you run FSUIPC7, so no point saving that. If you are using on a different machine or on an update machine, then the GUID's of your devices could have changed and you will need to manually update your FSUIPC7.ini to handle this. Can you please show me your FSUIPC7.ini after it has been updated and your latest FSUIPC7.log file.

Your log shows that 9 Go Flight devices were detected, including the TQ6: However, there is something strange going on with the registry, as the TQ6 is being allocated a joystick id of 1, which is also allocated to a Gamepad F310, which itself is initially identified as an Xbox 360 controller. Do you have a xbox 360 or a gamepad F310 controller? Could you also please show me your FSUIPC7.ini - we can first try changing the id's there, bur if that doesn't work we will need to clean your registry. A couple of other things: - you are using version 7.3.15. The latest version is 7.3.16 - please update - please always exit FSUIPC7 before attaching a log or ini file. Thanks, John