John Dowson

No - those log lines indicate keypresses from the keyboard (KEYDOWN). See the section Gauge local variable access (L:vars), by macro in the FSUIPC6 Advanced User guide, page 39. No. That is for FSUIPC7 and MSFS2020 / MSFS2024 only. What is logged when you press that button in the VC? It is not the KEYDOWN. Your log seems to contain many PANEL_ID_OPEN and PANEL_ID_CLOSE events logged with different parameters - maybe these have been repurposed. But I cannot tell from just looking at the log file. You need to do this with the logging console window open so that you can see what is logged when you press the switches in the VC in real time. No point posting the log file - look yourself! Or look into lvars to see if any are available. I know what the master warning and caution switches and lights are - its just helpful to me if you tell me in detail what you want to do - sometimes the warning/caution lights are independent from the switches, and I am not familiar with the aircraft you are using. John

Then that must be an older version that is linked to the windows start menu. Start it again that way, check the version number, then use File->Open Installation folder to see where it is installed. Then exit and delete/remove it.

Why not? Have you tried? It is incredibly easy and explained well: So, just create a myevents.txt file (in your FSUIPC7 installation folder), if you do not already have one, and paste those entries into it, reload the presets if FSUIPC7 is running (using File->Reload Presets) and then assign your axis to those presets in the normal way, by selecting Send Preset to FS, click the Find Preset.. button and navigate to those presets (under Personal -> Blacksquare Duke Mixture) and select the the preset (or presets) to use.

That may also work for the ini A350, but you might need to update the throttle positions and maybe the controls used.... John

If mouse-macros work for other switches, it seems strange that there is not one for this. But what exactly is "Warning"? If you log Events, do you not see anything when you click this in the VC? If anything is logged, then you can use that. I don't have this aircraft so I cannot look into this, sorry. You can check to see if there are any lvars available for this - try listing the available lvars and see if any look applicable (there is an FSUIPC-added control to log available lvars). Otherwise, ask on the aircraft support forums to see if / how this can be controlled. Well, that last message was good - no scroll bars! John

I cannot see any issues with FSUIPC7, and your access violations are in the LINDA.exe. Sorry, but I cannot help with this - I have never used and know very little about LINDA. Traffic scanning is being re-started a few times but this is almost certainly due to your system being under a heavy load and is nothing to worry about. John

@one2tw Please try the attached lua script. Save it to your FSUIPC7 installation folder and have this auto-started by adding it to the [Auto] or (better) [Auto.xxx] section (where xxx is your profile name) of your FSUIPC7.ini file, e.g. Clear the assignments to the F4 and F1 keys in MSFS2020 (as these will move to full throttle and cut-off by default). I am not sure this goes into TOGA, but please test and if not, let me know how you go into TOGA and I can update. Please take a look at the script and maybe adjust if needed. The throttle positions are defined here: local throttleStates = {"Idle", "Climb", "FLX", "TOGA"} local throttlePositions = {-3225, 8131, 12131, 16384} You can try adjusting those positions as needed (and restart the script afterwards!). Note that the strings in throttleStates are just used for logging purposes. Let me know how it goes. John A380Throttle.lua

First, when pasting text, please paste as plain text so that I don't see those annoying scroll bars... A macro is a macro.... If you have instructed FSUIPC to start the macro making process and the multiline simconnect message window does not appear when you click in the area that you want to create the macro for, then either the aircraft does not support macros (not all aircraft do) or there is no macro (i.e. mouse rectangle) available in the area that you clicked. John

Your installation log shows that you installed the latest version - I am not sure why your ini file does not show that old version. Have you ran it yet? And why are you posting in this topic anyway - do you actually have any connection issues? If so, read the documentation and follow the advice. Then only post if you still have issues, and attach both your .ini and .log files. John

@Eduardo P You are using an old an unsupported version of FSUIPC7 (7.5_ - please update. Do not set those parameters unless you really need to (and those are for the OPs system and may not be valid/work for your system). Better to read the documentation and follow the advice there - see the section Auto-tuning of initial start-up ini parameters on page 11 of the Advanced User guide. John

Sorry for the delay - you posted in the wrong forum and I did not see your message until now. Please check the SDK folder (after installing FSUIPC) - there is a Python SDK there. John

The trial license is now available from the first post in this topic. John

If it is detecting a steam version and you have an MS Store version, this is because you have a UserCfg.opt file in the following location: <user>\AppData\Roaming\Microsoft Flight Simulator 2024\UserCfg.opt Delete or rename that file and re-install.

It isn't - add an exception or disable while you download...

You need to provide more information. Please explain your issues in more detail and include/attach both your FSUIPC7.log and FSUIPC7.ini files and I will take a look. Please note however that I do not use and cannot support LINDA. For LINDA support with MSFS2020, please see https://www.avsim.com/forums/topic/620944-linda-support-for-msfs-2020/. I will take a look to see if there is anything obvious or FSUIPC-related. John Later: I see you have also posted the same message on the AvSim LINDA support forum. Unfortunately LINDA is no longer being developed or supported by the developer.

Looks like MSFS2020 is also using "VK_Return" and the documentation has not been updated. I will report this to Asobo. I have corrected this in the attached (beta) version, 7.5.4a. Regards, John FSUIPC7.exe

Your ini file shows 1 auto-lua specified: and the log file shows that was started: So what is the problem? Your ini is rather strange though as there is no [LuaFiles] section - have you edited/modified this?

Ok, that is interesting...and implies the MSFS/Asobo documentation is wrong. The input string used for the return/enter key in 7.5.1 and earlier versions was just "Enter". As these input strings have changed slightly in MSFS2024, I updated FSUIPC to allow different strings to be used for the different simulators in 7.5.2, and revised all strings against the MSFS documentation. For MSFS2024 the input string for this key is now documented as "VK_Return" (see https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/SimConnect/API_Reference/InputEvents/SimConnect_MapInputEventToClientEvent_EX1.htm), and for MSFS2020 it is now documented as "VK_Enter" (see https://docs.flightsimulator.com/flighting/html/Programming_Tools/SimConnect/API_Reference/InputEvents/SimConnect_MapInputEventToClientEvent.htm). So it looks like the documentation is wrong...I will check further here and either correct again and/or raise this with Asobo, and see if they will either correct to the documentation or update the documentation. Note there was no change in this area from 7.5.2 to 7.5.3, so if its now working with 7.5.3 in MSFS2024 then that is due to an update in either the SDK or in MSFS2024. I will update again after I have tested this further. Thanks for reporting, John

I think you are misunderstanding this parameter. It does not change when FSUIPC starts - that is determined by MSFS when using auto-start. It is the time from when it starts to when it tries to connect. Please don't attach images - they are useless to me. Any issues/questions, attach your FSUIPC7.log and FSUIPC7.ini files. The former will tell you the parameters used and when it tries to connect, so look at that and check that before posting. John

But that is not a standard FS control - are you using a MobiFlight event file (G1000.evt)? If so, those are not only rather dated, but I think you need the MF WASM module installed for them to work. You should switch to using presets - check the 'Select for Preset' checkbox instead of 'Select for FS Control', and then the Find Preset... button to open the preset list. The G1000 presets are under Microsoft->Generic->Avionics and that one would be AS1000_MFD_FMS_Lower_DEC. You can also search using the MF HubHop site: https://hubhop.mobiflight.com/presets/. There are many presets available for the G1000. John

Yes, I would prefer to leave that as a reminder....!

The installation log file (which I do not need to see!) shows that you have updated to 7.5.3, but I still need to see an FSUIPC7.log and full FSUIPC7.ini file - the last one you attached is again partial and shows version 7.4.16.2, not 7.5.3. Did you run FSUIPC7 after installing? You need to do that, and for lua scripts to auto-run you need to to also have MSFS running and a plane loaded and ready to fly. Lua scripts are started after the plane has loaded and lvars/hvars have been received and are available for use. John

Why are you reposting exactly the same question that you posted 3 months ago? You will get the same answer - see And Pete has retired, and doesn't really use MSFS2020. John

Why not try reading the provided documentation? To use lvars, either use a macro or define your own preset. See the documentation for both of these. I will help if you get stuck, but I am not going to explain what is already in the documentation (and there are thousands of examples available....). John

Would be helpful if you provided more details - for example, what was it called? Maybe it has been renamed? Or maybe it no longer works? But, what I said also applies - nothing to do with me really: John