John Dowson

This will be due to your browser - clear your browser cache and try again. The links are correct and point to 7.4.12. Or try the download section of this forum - all links point to the same downloadable zip file. What do you mean? If you are having problems registering your key file, then please see the documentation. - the Installation and Registration guide.

No, this is certainly not necessary. The ini file is only read by the FSUIPC7 application and has nothing to do with the installer. @vanislepilot should also try using substrings for your aircraft profile names. For example, change: to This will then match all PMDG liveries, or all aircraft that contain the substring 'PMDG 737-700' in the aircraft title. You should do this for all you profiles (i.e. use substrings for the aircraft names), and you should shorten an aircraft name added to a profile each time you add an aircraft to a profile. This will then allow the profile to be loaded when using the same aircraft with other liveries. John

You log file is generated automatically, and is available in the same place as your ini file - in your FSUIPC installation folder. If you do not know where this is, you can use the File -> Open Installation Folder... menu option. You can drag and drop files to the paper-clip section to attach them, or click the Choose files link. But you should at least be familiar with the basics of FSUIPC. I provide extensive documentation - at least familiarize yourself with the User guide. Did you check your assignments in MSFS, as well as the assistance options, as advised? John

No you don't - his problem was that he never received his registration details via email. Please see the provided documentation - the Invalid Key Problems section of the Installation and Registration guide. 99.99% of all such issues are caused either by 1. user error (putting in the wrong details) 2. not having the correct VC++ redistributables oinstalled Once you have read the documentation and updated your VC++ redistributables, if you still have an issue then post your order number here (do NOT post your key details) and I will check your registration details. Note I have done this many many times and have NEVER found an issue with user registration details. John

Sounds like something is resetting the elevator axis, whether this is your axis assignment or something else. Can you please activate logging for Axis Controls and generate a log file showing your issue, and then attach that as well as your FSUIPC7.ini file. Please also check to see if the elevator or any elevator controls are assigned in MSFS, and also check the assistance options as these can sometimes do strange things. As you are a relatively new forum user, you will have quite a low upload limit for your files. You can try compressing/zipping them, but if they are still to large you can email them to me (jldowson at gmail.com where at is @). John

Ok, thanks for confirming. No need for the log files. Not sure why others are reporting issues with this fix. John

Ok, thanks for checking and reporting back. Yes please - I would like to know that that (temporary) fix also works as @vanislepilot and @tango3000 reported that this didn't work, but did not provide any log or ini files so that I can check this. I suspect that they were not adding that ini parameter correctly, but I need to see the files to see if there is an issue. John

Have you read the documentation on auto-start, or read this thread? I have now explained the changes to the auto-start in v7.4.12 many times now...once again... The default auto-start mechanism in 7.4.12 has changed from using the MSFS EXE.xml file to using the FSUIPC MSFS.bat file or the MSFS desktop link to that file installed by the FSUIPC7 installer. If you are not using the MSFS.bat file or MSFS desktop link to start MSFS, then FSUIPC will NOT be auto-started. If you are using that file/link, then I do not know why FSUIPC7 isn't starting - check the MSFS.bat file and find the FSUIPC7 start-up line - does that look correct? Try pasting that line in a cmd terminal - does that work or report an error? If you cannot get the auto-start via the MSFS.bat file working, just switch top the EXE.xml method. To do this. re-run the installer and in the component selection page open the auto-start options, deselect the first option (MSFS.bat) and select/check the second option (EXE.xml). This will then revert to the EXE.xml method of auto-start which was the default in earlier versions. John

Then read this post and show me the required files.... THERE IS NO POINT POSTING FOR THE SAME ISSUE IF YOU ARE NOT GOING TO ATTACH FILES SO THAT I CAN INVESTIGATE No - I need to see what your issue is with the latest and ONLY supported version. I can provide the previous version, 7.4.11, if absolutely needed, but I need to see what the issue is with the latest version first, and for this I need to see log and ini files as stated.

I would still like to see log and ini files with IgnoreDevice added, as specified above, as this should fix this issue. I have also corrected this in the attached, i.e. this should work without adding IgnoreDevice. John FSUIPC7.exe

No! I don't understand how you can say/think this if you have read the auto-tuning section... what is not clear about this: i.e. adding that parameter will completely disable autotuning. To force auto tuning to run: i.e. just add that!. I am not sure why this is not obvious from the documentation... I don't know why I have to say this every time, but I cannot help you if you do not show me your files. I need to see both your FSUIPC7.ini and FSUIPC7.log files, the latter with logging for Buttons & Keys and Events activated. For anyone else that has issues, PLEASE always include these files or I cannot help you - it will be the first thing that I ask for. John

Well, the image you attached looks suspicious as it looks like you are running it from the zip archive. There is nothing wrong with the installer- the document it is trying to extract is probably already open. You should be able to skip this, but better to close any FSUIPC7 documents before installing.

Please check for similar issues before posting - see There is a temporary fix there which I am pretty sure should work but nobody has yet posted back. I also have a patchd version ready-to-go for this issue, but I will not release this until someone has reported if the fix works or not and provides their log and ini files so that I can check. Please use that post for this issue - I am locking this one now. John

Are you running the installer from within the zip file? You need to extract the zip first, then run the installer.

No. Older versions are not supported or available. What exactly is your issue? Have you read this post?

If you want a key or button assignment to toggle an Input Event value, the best way to achieve this is to add the Input Event to an offset, using the new [InputEventOffsets] ini parameter section, and then assign to the offset byte togglebits control,. So, to add an input event to an offset in your C510.ini profile, add the following to your C510.ini file (below using offset A000): And then assign to the FSUIPC-added control Offset Byte Togglebits with an offset value of A000 (change as needed) and a parameter of x1 (i.e. toggle first bit, to toggle between 0 and 1). See new section Adding Input Events to Offsets on page 52 of the Advanced User guide. John John

Generally yes, as that is in an offset area designated as free for general use. But you can only add it there as either a byte or word (2-bytes), and not as a double-word (4-bytes) or double floating point number (8 bytes) due to offset boundaries (i.e. the address ends in a 6, so you cannot use it for 4 or 8 byte values). As this is an enum, you can add it as an unsigned byte. Yes, but that won't wok for buttons either as the format is wrong - you have an additional/unneeded comma after the offset condition., and you have comments but no comment designator. Please consult the Advanced User guide if you have issues like this - it should be obvious if you read this. For example, on P24 of the Advanced User guide: Is that not obvious? Please always at least consult the manuals before posting, and also check/search the support forums for similar questions or issues. If you get an ERROR logged, then check your syntax against the manuals. John

The preset code here is this: i.e. it uses and lvar, not a b-var. This code was given to show a hack that you can use to introduce a l-var to control a b-var. You then use this lvar in the calc code to control the b-var in the xml code. As I said, this is a hack. You cannot directly control b-vars via calculator code.l

I am pretty sure you have ask this several times already, and I have already responded... What files are you talking about? Different files are read at different times, and when it comes to the ini file, different sections are read at different times. BUT, why not just maje it easy for yourself, and assume that everything is read when FSUIPC6 is started. So, if you want tyo change anything, exit FSUIPC7, make the change, then restart FSUIPC7. There should never be a need to restart MSFS. You can restart FSUIPC7 at any time, and it should reload pretty quickly. This really depends on the section, as different sections are read at different times. I am NOT going to go into details with this. You can use the reload buttons in the ui panels for axis, button and key assignments to reload the assignment sections. If you are not sure (or it is not documented), assume that the parameter is read only at start-up. Loaded when an aircraft matching the profile aircraft names is loaded, or when the profile is loaded and you click on one of the reload buttons in the assignments panel. The events.txt, myevents.txt (and offsets.txt) files are only read at FSUIPC7 start-up. If you want to reload them, then exit and restart FSUIPC7. John

Please also attach your FSUI{C7.log file when attaching your FFSUIPC7.ini file, as I need to see basic information, such as which aircraft you are using... Your FSUIPC7.ini file is pretty empty, and shows that you only have a few axis assigned, and only for use with one specific aircraft ('Black Square B60 Duke N43DH'): You have also assigned using 'send direct to FSUIPC calibration' but have not calibrated your assignments. If assigning with this, you should also calibrate your assignments. Please also check your MSFS assignments. If assigning in FSUIPC, you need to make sure that the same axis/button is not assigned in MSFS. Best to create an empty profile for your controllers in MSFS if assigning in FSUIPC. Any further questions/issues, please attached both your .ini and .log files, and activate logging in FSUIPC to show your issue (i.e. for problems with axis assignments, you should activate logging for Axes Controls). John

It would help if you could activate logging for Buttons & Keys, as asked for. I think you just need to give FSUIPC more time to load and initialise things. You should not attempt to do anything until MSFS and FSUIPC are fully initialised, which in your prev log is here: i.e. over 4 minutes after FSUIPC is started. The next time you think things are not loaded/not working, take a look at the log and see if those lines are logged, and if not just wait until they are. You need to be more patient. You can possibly reduce the DetectToConnectDelayAuto ini parameter so that FSUIPC tries to connect earlier, but this value has probably been arrived at via auto-tuning. You can also try activating auto-tuning again, as this parameter can be set too high if auto-tuning was performed when MSFS was updating. See the section on Auto-tuning in the Advanced User guide. Your files also show some device confusion, with devixe with id of 0 being acquired three times: This can be due to phantom xbox controller entries: Are you using such a controller? If not, then please try the attached ini file where I have corrected for this and shortened your aircraft names to use substrings. So please try this, and if any issues please explain and re-attach both your FSUIPC7.ini and FSUIPC7.log files. John FSUIPC7.ini

The community-driven effort for determining presets is let by MobiFlight, and all presets are available here: https://hubhop.mobiflight.com/presets/. I just provide the MF presets (via the events.txt file). You should use the HubHop site for all discussions/requests/ets for presets, not here.

You should have received an email with your license details, If you did not, you can raise this with SimMarket via their support service - see https://secure.simmarket.com/customerservice.php Your license details will also be available from your SimMarket account, so you can get them from there, and register them at the end of the installation process. You will not see the Assignments menu if you have not registered your license.

How do you know this? Can you please attach a log if you have issues, with logging for Buttons & Keys activated, and maybe also Events.

You either haven't given FSUIPC enough time, or the aircraft name does not match the one(s) you have in the [Profike.xxx] section of your profile. Are you using aircraft name substrings? Check your ini, and ALWAYS check your logs before posting. Note that when you first run v7.4.12 it should auto-tune the start-up parameters, but these will not take effect until the next time FSUIPC7 is auto-started. Please see the section on auto-tuning in the Advanced User guide. John