John Dowson

👍

Can you make sure that you are not running the installer from a windows protected folder. Also please try running the installer from a command prompt window - are any errors reported when doing this? Can you also try running FSUIPC7 to see if it can run correctly. Create a folder (e.g. C:\FSUIPC7) and download the latest FSUIPC7.exe from Then just try running it to see if it runs. If so, exit and manually create a FSUIPC7.key file in the same folder - details on the format of this file can be found in the Installing and Registering FSUIPC7.pdf document (which is included in the installer zip file). Then run FSUIPC7 again and see if you have access to the registered facilities (e.g. assignments). If that works ok, I can provide you with the additional files you need (WASM and Documentation).

I have updated to 23H2 now and the installer is working as expected here (although I am now having some strange issues with my displays...). Ok, so it is the installer framework that is causing this - FSUIPC6 and FSUIPC7 use the same framework, but not FSUIPC5. If this is a new PC, you will need to install the latest combined (2015, 2017, 2019 & 2022) VC++ redistributables, available from https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022. Install both x64 and x86 versions. Can you please install these and try again.

Yes, and you (most probably) loaded a different variant, so it did not match that full aircraft name in your profile, so the profile wasn't loaded and therefore you didn't have your assignments. You have no general axis assignments, and only 3 general button assignments, so you would have had no (or hardly any) assignments when you load any variant that wasn't the one in your profile. That is how profiles work....

Change this: to this: You also have various profile for the PMDG 737: You really don't need so many profiles for the same aircraft, different variants. and any new variant you try will need another profile to be created, or to be added to an existing one. You just need one profile: or possibly two if you have different assignments for the 700 variant vs 800, but usually not necessary. Choose one profile (not necessarily the 'PMDG 737 FSUIPC7' one - you should choose the one which is most complete), and try using that for all variants. Of course, you can use separate profiles if you so wish, but no need if it is just a livery change. Your profile aircraft name should be a substring of the actual aircraft name that catches all variants of the aircraft you want to use with that profile. Please see the User guide on how to use profiles. John

So it sounds like a problem with the aircraft name in your [Profile.xxxx] section. You should adjust these after creating to use substring matches, to catch all variants, rather than using the full aircraft name that FSUIPC adds.

Your log looks ok. You are getting these errors: As you are trying to use calculator code/set lvars before they have been loaded. You need to wait until the WAPI has started before you can do this, which is happening quite a bit later: Looks like the Comanche is also very slow at creating its lvars - you are getting a lot of reloads: And as for your issue of missing assignments, this is usually due to using an aircraft with a different livery/name that doesn't match the one in your profile section, which is why I asked to see your FSUIPC7.ini file. Please show me/attach that. John

What problem? Version 7.3.25 contains a memory corruption bug, which is fixed in the latest beta, which is why I have asked you to test with this. I am finishing now, will take a look at your logs tomorrow. John

Also maybe try the latest beta to see if you get the same issue - just download the FSUI{C7.exe and use it to replace your current one (or just rename your current FSUIPC7.exe so you can easily switch versions), available from John

Can you please attach your full FSUIPC7.log file - you can zip/compress it if is too large. Also attach your FSUIPC7.ini file. Looks like there is a problem/issue with the WASM/WAPI, but I need to see your complete log file. Also attach your FSUIPC_WASM.log file - see the WASM section in the Advanced User guide if you don't know how to find that file.

Yes, very confusing...I do not understand how it can not run and also not report any error or exception anywhere. Without any information, it is very difficult for me to advise what to try next. I have not updated to 23H2 yet. I can't see how this can cause issues, and would have expected many more support issues if this was the case. but I will update to this version over the weekend. Do you not see anything at all in the task bar when you attempt to run the installer? Do you see anything running in the Task Manager? Have you tried running the installer after a clean reboot? Maybe also try moving the installer to a different folder. What is the size of the installer, in bytes, from the properties page? Should be 41,426,470 bytes, You can also try running the compatibility troubleshooter from the Compatibility tab of the Properties page, and maybe also running the installer in compatibility mode (for windows 8 I guess). Can you try downloading and running the installer for FSUIPC6 to see if you get the same issue (the installer is the same as for FSUIPC7). This will uninstall FSUIPC5, but you can uninstall FSUIPC6 after it is installed and then re-install FSUIPC5 and nothing should be affected. If all else fails, you could install manually - I can provide instructions to do this if/when necessary.

Can you check the Windows Event Viewer (under Windows Logs -> Application) to see if there any events related to the installer, and if so show me those. Are you sure that you have extracted the files from the zip archive, and are not trying to run the installer from directly within the zip file? You can also try updating your VC++ redistributables (instructions are in the Installation and Registration guide, under Invalid Key Problems section), although I doubt this will help. If you aren't even seeing the UAC approval dialog box, the installation process has not yet even started. The only thing that can prevent this would usually be anti-virus software. Are you sure that you are only using MS Defender? There should be no issues with this - most, if not all, users will have this running, including me, and this should not give any issues. What version of Windows are you running under?

No need to run as admin, but when you run it windows should display a User Account Control dialog box asking for permissions for the installer to make changes to your device. If you don't see this. check your task bar to see if this window is iconised. Also, if you are running any anti-virus software, check that is not blocking the installer and if so disable (while installing) or add an exception so that the installer can run. John

No - I will update the documentation for the official release. But there is just one additional function: ipc.execInputEvent(name, param), where name is the name of the input event (string) and param is the parameter (number/double float). As an example, to move the left condition lever in the King Air to low idle, use ipc.execInputEvent("FUEL_1_Condition_Lever", 1 ) (change the parameter to 0 for high idle and 2 for cut-off). ipc.execCalcCode("2 (>A:BUS LOOKUP INDEX, Number) (A:CIRCUIT CONNECTION ON:45, Bool)") or ipc.execCalcCode("2 (A:1:CIRCUIT CONNECTION ON:45, Bool)") Isn't this all pretty obvious?

Did you try increasing the LvarScanDelay further, and if so, did this prevent the CTD? I have now added further locking in the WAPI to try and prevent this - please try the latest beta available in this thread: If you still get the same issue, can you show me a log file from a CTD when you have WAPI Trace logging as well as Lua Plugins logging (not separately!!) and Event logging activated. The file will be large and may need zipping. John

They are not available in the current release as they are very new. All MF presets are stored in the events.txt file, in your FSUIPC7 installation folder. I only update this file on a new release. If you want to use newer presets that are not available in the events.txt file installed by FSUIPC7, you can always download this file from the MF HubHop site and use it to replace the one in your FSUIPC7 installation folder. Note that you have to be registered and logged-in to your HubHop account to download this file. I have attached the latest version below, but please download and update this yourself the next time. John events.txt

For avionics power switch. you can use the ELECTRICAL_Avionics_Bus_1 input event, with a parameter of 1 for pwr, 0 for off. For the battery switch, you can use the input event ELECTRICAL_Battery_1, with a parameter of 2 for EMER, 1 for Off and 0 for On. Why can't you just use those rather than messing around with the bus connections? As for external power, how would you do that in the VC? If this is via ground services, I am not sure this can be implemented, unless it is possible to assign a key combination for this (in MSFS).

As to the question that is the title of this topic ('How to use SimVars / Events 2 indicies in Lua'), you have already given the answer - you would use the RPN calculator code and send it via ipc.execCalcCode. Can you perform each of these activities in the VC (i.e. what buttons/switches/etc do you ? If so, how? Have you tried the following Input Events: ? Not sure what they do, but maybe worth playing around with. Note that just because these are logged without a parameter, it doesn't necessarily mean that a parameter is not needed. And also remember that some input events have still not been exposed for external use, but more should be available in future SDK updates. You can check using the MSFS dev tools yo see what other Input Events are avalalable, and also how they work if they look appropriate. Other than that, I cannot really help you much with this. FSUIPC provides the tools to enable you to control an aircraft, but it is up to you to decide how these are used. I know very little about how the electrical systems work or are implemented for any specific aircraft (and don't understand how the system.cfg relates to the events/code that you would use to control the aircraft). You should maybe try asking these questions on the aircraft support forums. I can take a look in more detail at some point, but I do not have time for this at the moment. I still have quite a bit of work to do on the next release (Input Events), but can maybe take a deeper look once this has been released. Please update if you get any further with this or have further information (what UI/VC controls do you want to replicate?).

Run the installer again. The details from your key file will be used to populate the registration dialog - try validating them. If they validate ok, you made a mistake when entering them. If they don't validate correctly, you need to update your VC++ redistributables. John

You can use your old/existing FSUIPC7.key file when you re-install - no need to re-register. However, if it previously worked, it should still work. You are either entering it incorrectly, or your VC++ redistributables need updating. But if your FSUIPC7 key validates ok, then your VC++ redistributables should be ok. See the section Invalid Key Problems in the Installation and Registration guide. Also remember, if you are using a different name and/or address for your WideFS key than the ones for FSUIPC7, you have to check the appropriate box and enter the name and address you are using for WideFS. If you still get the same issues when you have checked all of the above, please let me know both your FSUIPC7 and WideFS order numbers and I can check them here for you. Do NOT post your key details. John

First, as stated in the beta announcement topic, for any issues in this beta release, please post in the beta release thread/topic. The issue was that the function call was always returning a failure even though it had succeeded. I have corrected this now, and the beta release has been bumped to 7.3.26d. John

The display library is for WideClient only. If not using WideClient. you probably want to use ipc.display. However, the SimConnect text display functions are no longer working in MSFS. You may see something, but it is not reliable and the underlying functions have been deprecated. For displaying information in a window from lua, you should use the Wnd library. John

For testing values, use '==' not '=', e.g. if avstate == 0 then .... A single '=' is used for assignment, not conditionals.

Please see John

Please see John