John Dowson

But that log file you pasted shows the luas were loaded? No, not a coincidence. As I said in my previous post, the issue is that the WAPI isn't being started (it was enabled but not running). By disabling it and re-enabling it, it started running. If you can provide me with a log file showing the WAPI not being started (with the additional logging in that version I posted) then I can correct for this. It seems the root cause of this is a change in order of events from MSFS which I need to correct for. Maybe specific to the Fenix - have you tried other aircraft? It would also be useful if you could add logging for the pause state offset 0264 (Log->Offsets) as U8 in hex (with Display to 'Normal Log File' checked).

I have not heard a report yet of the WASM crashing. You also only showed a prev log for this - there must also have been a current log. And switching back to the beta version confuses things...Anyway, forget this for now as I don't think this is your issue - we can return to this if it happens again. Auto-tune did run and set quite a high value. It can do this if/when MSFS is updating, or maybe if using a complex aircraft on previous flight. If this is too high, this just means that it will take longer for FSUIPC to connect and be ready. What is happening now, is that auto-tune is running and detecting no issues, so it is reducing the detect-to-connect time by 10 seconds and will run on the next execution. This will repeat until it detects an error or gets to the minimum time set (30seconds). Once it gets an error, it will determine the times needed, set them and then finish. So, it reduces until an error is detected, then increases and finishes. As your current DetectToConnectDelayAuto is set to 300, this could take quite a while. This is why I asked you to set: InitialStallTime=15 DetectToConnectDelayAuto=60 which will most-likely give a connection error (or several), but then the times will be correctly set and the auto-tuning will finish. Looking at your latest logs, it seems that the WAPI was not started. This looks to be a strange timing issue, where the WAPI is not being started as the either the aircraft is still in the parking state or the sim is in a pause state when it is supposed to start. This will be due to the state of the MSFS and the aircraft being loaded at the time FSUIPC7 is starting things up. I need to know the state of a few things before I can correct this, so can you please try once with the attached version, which has additional logging added. Run MSFS with this installed and have FSUIPC7 auto-started. If the aircraft loads but your lua no longer load, try going back to the main menu and then start the flight again. Do they then load? Please show me your FSUIPC7.log from thjs test. Then (if luas still didn't load), exit FSUIPC7 and start it manually - do the luas then load? Please show me the log file from this test. Rename your FSUIPC7.exe (to FSUIPC.exe.7412) and use the attached version for this test: FSUIPC7.exe Then please try changing the settings to: InitialStallTime=20 DetectToConnectDelayAuto=60 StartUpTuningActive=Yes Then run MSFS again to get FSUIPC7 auto-started. Once MSFS arrives at the main menu, wait a short time before loading an aircraft. This should then set the parameters to good values for your system, which will take affect the next time you run MSFS. John

So you updated the VC++ redisributables and still it won't validate? It validates just fine here. I will PM you a key file - please save this to your FSUIPC7 installation folder, then re-run the installer. This will then pre-populate the three registration fields (name, email, key) with the details from the key file - try validating them. If it fails validation, please check any anti-virus software that you are using. It has been reported that some anti-virus software quarantines/removes (or doesn't allow to run) the registrationChecker.exe program build into the installer. If none of that applies, and you have updated your VC++ redstributables, then I have no idea why it fails validation. If you run FSUIPC7 with that key file, does is run as a licensed/registered version (e.g. can you see the Assignments menu)? John

Also, better to change the following two ini parameters in the [General] section of your ini file and let auto-tuning do its thing (keep all other parameters as they are): John

Can you please download and update to the official release of 7.4.12 - you are using 7.4.12c, a beta version, which is no longer supported. Are you using 7.4.12c with the WASM for 7.4.12? This can maybe cause issues as they are compiled against different MSFS SDK versions and also different VC++ redistributables. So please update to the latest official release, try again and then show me the updated files. Also please activate debug logging for the WAPI (Log -> WAPI -> Debug). Also, please exit FSUIPC7 BEFORE attaching files. Your FSUIPC7.log shows that FSUIPC7 was still running (i.e. no closing statements) or had crashed... And those log files show completely different time stamps - I need to see the files from the same session, and the FSUIPC_WASM.log not the FSUIPC_WASM_prev.log, which is always the log file from the previous session. Your ini file also shows some issues with controllers, but you only have two assignments: and both of these are for a T.A320 Pilot controller which you no longer seem to be using: To clean things up a bit, delete those two button assignments, and remove all the joy letter assignments, i.e. your [JoyNames] section should just contain: New joyletters will then be assigned, starting from A, and you will have a clean ini ready for assignments. John

Lua auto scripts are not started until the list of lvars/hvars has been received fromthe WASM module via the WAPI, here: Is nothing logged after the '[INFO]: Connected to MSFS' message, even if/when you keep FSUIPC7 running? Can you test again, and if your lua's don't start, exit FSUIPC7 and then attach your FSUIPC7.log file as well as your FSUIPC_WASM.log file (see Advanced User guide, WASM section, if you do not know where this log file is). Maybe also attach your InstallFSUPC7.log file so that I can check the WASM was installed correctly. As you are a new user to this forum, your upload file limit will be very low - it will increase the more you post. Try compressing the files before attaching, but if still too large you can paste the contents instead (but please paste the whole file, not an extract). John.

I have corrected what I can - please download and try the attached ini file. There are still some issues that you need to sort out: 1. You have two profiles for the Skymaster: Do you really need different profiles for the same aircraft with different liveries? Take a look at those profiles and decide which one to keep, then delete all of the profile sections for the other profile. Then corrrect the aircraft in the profile section, i.e. either: or Or, if you want to keep the two different profiles, maybe it should be a different profile for the Cessna 337 to the Carenado, e.g.: ? It is up to you to decide, but it seems strange having the same aircraft with different liveries assigned to different profiles - different liveries should not affect the aircraft controls and so you don't need to use a different profile for a different livery. 2. Your general [Axis] section has the same axis assigned to multiple controllers/devices: You have aileron, elevator and throttle all assigned to device A (Saitek Pro Flight Yoke) and C (T.Flight Hotas X), and the throttle also assigned to D (Saitek Pro Flight Quadrant). Having the main flight axes assigned to multiple controllers can cause issues, as the axis position can be sent from both controllers, causing the axis to jump. Revise those assignments and remove the ones not needed - just assign one axis to each of the main flight axes (aileron, elevator, throttle, left brake, right brake, rudder, Mixture, PropPitch) to avoid problems. So, please revise the above, make the necessary changes to your ini file and try again., Any issues, please re-attach both your FSUIPC7.log and FSUIPC7.ini files and describe the issue. John FSUIPC7.ini

That is a completely different ini file from the one you originally posted! The ini file now shows that some of your device GUIDs have changed, and rather than fix this issue you have then re-assigned to the new joy letters: You are also NOT using substrings for your aircraft profiles - this can cause issues with the assignments not being loaded when using the same aircraft with a different livery. You should use substrings for your aircraft profile names. The aircraft you are using (Aircraft="Black Square TBM 850 N851TB") does not match any profile, so will be using your general profile sections, so for axes it is using the [Axes] section. You have no assignments to a throttle 2 axis in your general profile, just to the Throttle control and on multiple controllers (A,C, D and G) although only one of these exists (G - Saitek Pro Flight Quadrant). The Throttle control should control the throttle for all engines - is this not the case? Why do you think the throttle 2 axis is not working, when you are not assigning to this? I don't understand how your ini file got into such a mess, but I will try and correct it and post an updated version later today for you to try - don't have time just now. John

If using FSUIPC6, then you need the 64-bit driver, PFCcom64.dll. You should NOT have that in your FSUIPC6 installation folder. Where is that message from? The FSUIPC PFC drivers do not come with an installer - they are just dlls that you need to put into the same folder as the FSUIPC6.exe Just download and copy the PFCcom64.dll driver to your FSUIPC6 installation folder and remove any other 32-but drivers. Any further questions/issues, please attach your FSUIPC6.log file. John

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