John Dowson

I have no idea why it cannot install the documents. Are you changing the default installer options? i.e. why is it skipping the hvar files? Please attach your InstallFSUIPC7.log file.

@alexanderluzajic Can you PLEASE read my comments - I am not going to respond to you here, please use your original topic. And I responded to your response., in your original topic.

You do not seem to be using FSUIPC for much - just one button assignment, and one lua running for all aircraft (A320ParkBrake). You have two profiles. but both of these are empty. Your log shows that you have a very long start-up time for MSFS. You have DetectToConnectDelayAuto set to 5 mins (300 seconds) but this still doesn't seem to be enough: From this log, you should set DetectToConnectDelayAuto to 490. Apart from that, your log shows that you didn't start a flight until over 17mins after starting FSUIPC7, and it looks like there was no response from the WASM and so no lvars were loaded and your lua auto wasn't started. I am looking into this issue, reported by many, so please be patient. There will be a new release in the next day or two, John

I have no idea what you mean. Please take care to explain your issue, and provide your files that show the issue - the FSUIPC7.log and FSUIPC7.ini files. Many people are having issues when FSUIPC7 is auto-started. If you exit FSUIPC7 once it is auto-started and then manual start FSUIPC7 does it work? If so, then it is the start-up parameters that are causing the issue. Read the section on this in the Advanced User guide, and post your files here, together with an explanation of your issue and I will take a look. Settings are NEVER lost - they will be in your ini file. They may not be loaded though, and that can be for many reasons, but the usual culprit is using an aircraft that does not match the aircraft names in your profile, as you have not edited them to use substrings for matching. But I cannot tell you anything from a rant/post without showing any supporting information. John

I presume it is this one: If so, please post in that topic. If so, I have already responded there - have you read that response? I have no idea why people are having such problems with the installer - there has been no change in the installer for a long time (over a year), except for the files that it installs. Do you have an InstallFSUIPC7.log? If so, show me that. But PLEASE use the topic you created for your issue, and not post in topics for other issues which are not the same. And make sure you run the installer from Windows Explorer, not in WinRar.

I am just letting you know that I cannot do anything about this until you supply me with the files I need to investigate. There is no point in you posting again until I have these, I have been waiting to see this since your original post. If you want me to look into this, provide the files/information I need. Otherwise there is no point posting about this issue. You started this topic for your issue, I asked for the files to investigate - since then I have been waiting for the correct files.

But what solution? Killing the installer via the task manager is not a solution to this problem - it just stops the installer from completing. Did you do anything to actually resolve this issue? When you validate your license, does the installer hang once the validation success message has been displayed? If not, and you previously had this issue, what did you do to correct this?

Your lua script looks ok. That is because they are NOT events (or k-type variables). They look to be Input Events (or B-type variables). Try listing Input Events - are they listed? You can use Input Events like other events - either assign to them directly (by checking Select for Input Events), and in lua you can use the ipc.execInputEvent function. Please see the Advanced User manual on Input Events, and the FSUIPC Lua Library manual for details on lua library functions for Input Events. John

Sorry, but there is nothing I can do about this issue - there is nothing wrong with the installer. The only thing I can recommend is to update your VC++ redistributables, as described in both the README.txt and in the Installation and Registration guide. When you click Register, is the FSUIPC7.key file generated? That is what this button does - it validates your registration details and generates the FSUIPC7.key file. There may be an issue with this if trying to install into a windows protected folder (e.g. under Documents or Program Files). If this is the case, choose another non-windows protected folder. And please be aware that if you have already registered once, and you have a valid FSUIPC7.key file, you do not need to register when you re-install. Just click Skip - no need to re-register. Other than that, there is nothing more I can say about this issue. John

Please do not posts requests in the User Contributions sub-form - this is for contributions only. It does say NOT for support requests. What version of FSUIPC are you using? I will move your post... Should be relatively straight-forward. To get started, check-out some of the other lua sound plugins available: John

That is interesting... Does that add-on continually create lvars by any chance? I think there could be issues with FSUIPC7 when using add-ons that continually create lvars, due to the way FSUIPC WASM pushes newly created lvars out to FSUIPC7. I will add a fix for this (as detailed in my comments above) in the next release. John

But why? Re-installing will do absolutely nothing. I know, you have said this already. I am still waiting to see a log file from you when PACX was NOT working, i.e. when FSUIPC7 was auto-started. I do not understand the difficulty you are having in providing me with this file. I have no idea why it is not connecting and cannot help you if you do not show me this file. John

First, you posted in the main support forum. For all FSUIPC7 issues, please use the specifc sub-forum for FSUIPC7. I have moved your post. If you want help, you have to explain what your issue actually is. Just saying it doesn't work or you are unable to use an aircraft doesn't help. And I also need to see your files - your FSUIPC7.log and FSUIPC7.ini files, with a description of what is actually not working. There are also several other similar support requests that I am currently looking into. Also, if FSUIPC7 is being auto-started, try exiting it and then re-starting it. Do you then get the same issues?

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