John Dowson

K-type variables are events/controls. Simulator variables, or simvars, are a-type variables. All events (i.e. k-type variables) are available, either for assignment via the UI, or in lua you can use the ipc.control function. The number for the TOGGLE_EXTERNAL_POWER event is 67090 (see the file Controls List for MSFS Build 999.txt in your FSUIPC7 documents folder for a list of controls with there corresponding event number. You don't need to use lua, you can just assign to it. If you want to use lua, it would be ipc.control(67090, 1) or you can use the calc. code directly, i.e. ipc.execCalcCode("1 (>K:TOGGLE_EXTERNAL_POWER)") John

And how did you solve it then? There is really nothing I can do about such an issue. No idea what could cause this - this is either a windows issue, or possibly caused by trying to install into a windows protected folder. This is NOT an issue with the installer. Maybe check the Event Viewer to see if any error are logged for the installer.

@Luigi Martinelli Forgot to say, can you use the latest beta please which has additional logging. Can you also make sure that you have the following logging set (and no other): Buttons & Keys, Events & Extras. Note also that your issue is actually different from the one reported here and should be in its own thread (or one of the other threads with similar issues) - this thread is really for when FSUIPC stops working during a flight. Your issue is (or seems to be) that your buttons are not working when you start a flight. FSUIPC7.exe

No - re-installation achieves nothing. These are the correct files this time, but unfortunately don't show much. From the log, you manually started FSUIPC7 when you had the F117 Knighthawk 84-827 loaded (no profile for this aircraft, so will use the general assignments). Looks like when this was loaded, FSUIPC wasn't function correctly (threads not started, no buttons presses logged, but keys are logged). What was the state of MSFS when you started FSUIPC7? Was it in the main menu or another menu (which), or was the aircraft loaded and ready to fly? You then loaded the Cessna 172 after 5mins 37seconds: and then everything seems to start ok: And everything seems normal from then. Were your buttons not working for the Cessna 172? Your log file does show one error: Error 2 implies that the file does not exist at that location. Is there a reason why you are using a keyboard hook with FSUIPC7: ? And why are you running the HidDemo lua script: ? Can you also please exit FSUIPC7 before attaching logs - you attached this one when FSUIPC7 was still running. And as you are using profiles-in-separate files, I will also need to see the profile ini files for the aircraft that you are using when testing, so please attach those. There is certainly something strange going on as I do not understand why things weren't started when you started FSUIPC7 and had the F117 Knighthawk loaded. I will need to se some more logs with additional logging. Can you please add TestOptions=x800 to the [General] section of your FSUIPC7.ini file. Also, please respond to my questions. Correct that error with your DynamicLOD.exe not starting, and provide me with another set of files from a test when MSFS auto-starts FSUIPC7. Select your aircraft and get ready-to-fly. Then wait 30 seconds or so, then test your buttons/axis. If they do not work, exit FSUIPC7 and restart it, Wait until everything is loaded (again 30 secs or so), then test again. Do they now work or not? Exit FSUIPC7, then attach your FSUIPC7.log, FSUIPC7_prev.log, FSUIPC7.ini, and the profile file of the aircraft used, if that is in a separate profile. I am finishing now for the day. I will look at your updated files once attached, either tomorrow or Monday. John

No - this log is from a manual start: I do not understand why you are having such difficulties. When you get the issue that PACX is not connecting, exit FSUIPC7 then attach the FSUIPC7.log file, not the FSUIPC7.prev.log file. However, if you restart FSUIPC7, then it is the FSUIPC7_prev.log file that you need to attach. Why not just open the log and take a look at it before posting? This will tell you if it is a manual or auto-start by looking for a line like that one posted above. John

Maybe check the security properties of the installer - right-click and select properties. The security tab should look similar to this: Check that it has the correct permissions. John

When you double-click it, a message should pop-up asking you if you want to allow an app from an unknown publisher to make changes to your system. You have to agree to this and then the installer will run. If you do not see such a box, then check your task bar (for a shield - it may be iconised). If it is not there, then check the Windows Event Viewer to see if anything is reported there. You must run the installer from an account that can have elevated privileges. If none of this works, I can't help you I am afraid. Try google, e.g. https://support.microsoft.com/en-gb/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d https://www.makeuseof.com/tag/try-windows-software-wont-install/ https://answers.microsoft.com/en-us/windows/forum/all/program-installer-wont-open-on-windows-11/b9a0a715-b829-4c21-a920-ce7fe4cd6e71 https://forums.tomshardware.com/threads/exe-installer-files-wont-run-on-my-computer.1757906 I am sure your answer lies there somewhere... John

I also have no idea why either ,and no idea what you are doing. If you want help, please answer any questions I ask and explain clearly what you are doing. The installation of FSUIPC is straight-forward and should not be difficult: 1. Download the latest Install_FSUIPC7.zip file from www.fsuipc.com 2. unzip the file 3. open and read the Installing and Registering FSUIPC7.pdf document and also take a look at the README.txt 3. Double-click the Install_FSUIPC7.exe file, which will start the installation process. If there are any problems, check any anti-virus software that you have running to see if it has blocked or quarantined anything, and if so either add an exception to allow the installer to run, or disable your anti-virus software before downloading/extracting or running the installer, whichever part is being blocked.

In both cases ( @EisernUnion & @superrodrigues753), something is creating lvars every few seconds. When new lvars are created, the WASM will detect this and push out the new (complete) lvar list out to clients. This involves dropping all existing CDAs (Client Data Areas, the memory areas that MSFS provides to share such data between MSFS and clients) and re-creating them. This is happening 3-10 times a minute (or more) in both cases. I created a lua script that mimics this behavior and set it running in an MSFS session that I had been running for over 2 days without any issue. Doing this, I still didn't get a WASM crash, but I did get an MSFS crash! And the FSUIPC_WASM.log file was over 2GB, but still didn't show any issues. I don't understand why lvars are continually being created, or what is creating them. It could be the aircraft itself, or an add-on that you are using. If you list the lvars, the ones recently created will be the ones with the highest id - lvars are listed in id order in the FSUIPC7.log file when you do Log->Add-ons->WASM->List Lvars. Maybe try listing them and see if you can determine what is creating them from the names. I suspect GSX but could be another add-on or the aircraft itself (don't have the Fenix so cannot check this, or GSX). FSUIPC7 does have to continually re-scan for lvars at initial start-up of a flight, as many lvars are created quite a while after the flight session starts. However, I don't think lvars created long into a flight can be of much use to the user (especially for assignments) - they are probably for use by the add-on or aircraft that is creating them only. Therefore I am going to add a new WASM ini parameter LvarScanPeriod, set to a default of 600 seconds (10 mins). This will be the period, after the aircraft is loaded and ready-to-fly, during which the WASM will scan for lvars, and after this the periodic scanning for lvars (with period defined by LvarScanFrequency ini parameter) will stop. Note that if you create an lvar via FSUIPC using the lvar creation facilities (NOT via calc code!) , the new lvar's name/value will still be automatically pushed-out to FSUIPC7, and the client can always request an lvar scan either manually (add-ons->WASM->Reload), via lua ( ipc.reloadWASM()) or via a control (Reload WASM). I have also noticed that a new MSFS SDK has been released, 0.24.3.0. I will also rebuild everything against this SDK for this release. Not sure what the changes to the SDK are yet, but I will take a look. I would expect to release this next version sometime next week. I will still be interested in trace logs and any other information you can find if you get the WASM crash with that version I posted above. Regards, John

👍

Double-click on what? If you are double-clicking the FSUIPC7.exe (after installation) and that does not start FSUIPC7 (you should see a splash screen) Have you installed FSUIPC7? if so, please show me your installation log. If you cannot run the installer, then you probably need to update your VC++ redistributables. I'm sorry but I cannot help with this - if you have extracted the zip file you downloaded, then you should be able to open the README.txt in any editor. If you cannot do this, it is a windows issue on your machine that you need to resolve - I cannot help with this. I have attached the README.txt. And please give your posts an appropriate title - FSCUIPC7 (sic) means nothing, and a title of FSUIPC7 would apply to every post in this forum, as this IS the FSUIPC7 support forum. I will update it this time. John README.txt

Create a preset for this in the myevents.txt file (create this if it doesn't exist), then assign your button to the preset. It is pretty straightforward - why don't you just give it a go? Read the section Using Calculator Code Presets on page 49 of the Advanced User guide. If you have anu issues, post again and I can help further. John

I do not understand why you are posting. Do you actually have a question?

So what is the issue? That means you are good to go - click next or skip and finish the installation process and you are good to go. Any issues with installation and/or registration, please see the provided installation and registration guide. John

Very strange - never heard of that issue. Anyway, glad its now working. John

Yes - error 2 is not really an error and shows PACX was running and connected. Unfortunately you attached your log file for when you restarted and PACX connected ok. I need to see the log file from when FSUIPC7 is auto-started and PACX fails to connect. Please show me/attach that the next time it happens. If you restart FSUIPC7, then the previous log file will be renamed to FSUIPC7_prev.log. John

Why are you still using a trial license? The trial license is meant for you to try FSUIPC for a period of a few weeks or so. After that, if you don't want to purchase, you should either delete or use the unregistered version. Ok. That log file is useless. Also, when it next happens, can you also attach the FSUIPC_WASM.log file and any events you see related to FSUIPC. Also, please check the MSFS console for any messages relating to the FSUIPC WASM. Was the first flight/session a long one? i.e. how many hours (approx) and how many flights? What other add-ons are you using? Do you use GSX?

I am not familiar with the 787 - where is this button located? Is there even such a button? I have read this: With VNAV active, pushing the IAS/MACH selector enables speed intervention See https://www.avsim.com/forums/topic/640784-airspeed-intervention-unstable-approach/

Can you check in the Windows the Event Viewer please and see if there are any events related to FSUIPC (under Windows Logs -> Application) and if so save the event and show it to me/attach it. So this has happened in the past? Was this reported? The next time it occurs, can you please show me the log file from both when FSUIPC freezes, and also when you restart and it stops responding. Your ini file is pretty empty - looks like you are not using FSUIPC for anything except auto-save.... John

Not offhand. There is a preset for altitude intervention: AUTOPILOT_PUSH_ALTITUDE_INTERVENTION This uses the hvar H:AS01B_FMC_1_AP_ALT_INTERVENTION You could test to see if there is a similar hvar for the speed intervention. Try executing the calculator code (Add-ons->WASM->Execute Calculator Code) (>H:AS01B_FMC_1_AP_SPD_INTERVENTION) and maybe also try: (>H:AS01B_FMC_1_AP_SPEED_INTERVENTION) to see if any of those work. If so, you can define your own preset. Otherwise, you can try inspecting the behavior of the button using the MSFS development tools - see https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/ Also you can try logging Input Events (Log -> Input Events), press the Speed Intv button and see if anything is logged, and if so use that. I can take a deeper look at some point, but probably not for at least a few days. John

To be clear, for this you should check Select for Preset, and choose AS530 RightLargeKnob Left - either directly from drop-down menu (will take a second or two to populate) or via Select Preset.. button. John

This is not necessary. You do not need to install/use the MobiFlight WASM module if using FSUIPC7. Do you need to use MobiFlight? i.e. do you have any home-built equipment that requires its use? If not, you should remove this from your WASM community folder and try again. All you should need to do is download and install FSUIPC7. This contains a MobiFlight events.txt file - it is pretty recent and should not need to be updated, but you can update this if there are new MF events not in the current one. You should be able to assign to these events/presets and they should work via the FSUIPC WASM module. Ah, this is what you are doing wrong. You are assigning to the MF events, not the presets. If you assign directly to MF events, you will need to install/use the MF WASM module. However, it is FAR better and easier to use presets instead. To do this, Select for Preset, then click the Find Preset... button and locate the required preset and use this. The MF add-on event functionality (and the event file functionality in general) are an older method of control and should really no longer be needed, as everything is far easier using the presets, and the MF presets in particular. All add-on custom events will now have a preset equivalent that you should use instead. So, remove the MF WASM module from your community folder. Then change your assignments from using the MF events to using presets, and remove any *.evt files from your FSUIPC7 installation folder. Any issues, please attach your FSUIPC7.ini and FSUIPC7.log files and I will take a look. John

The files you are attaching don't make sense: From your prev.log file: From your (latest) .log file: From your ini file: Are they all from the same folder? They should be, but I do not understand how your log files can show a different version than your ini file. Please run MSFS again with FSUIPC7, then open your installation folder (File->Open Installation Folder...). That will be the location of your log and ini files that I need to see. And PLEASE at least check your files before posting them - if they are not from 7.4.12 or later, don't post them as they are useless to me. John

Looks like you are experiencing a WASM crash, the same as @EisernUnion. Can you please download and use the updated version of FSUIPC7 + WASM posted above and set the log level to Trace in the WASM, and re-attach your files the next time you get an issue. Your log files will be very large and will probably be to big to attach even when compressed. If so, try using one of the free file transfer services, e.g. FileTransfer.io John

I do not provide links to older versions - only the latest version is supported. Please show me/attach your FSUIPC7.log file (from 7.4.12, not 7.4.11). John