John Dowson

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

This usually indicates that something else is needed - a H or L var, or maybe an Input Event. I don't have the DIGITAL DAKOTA WORKS DC-3 / C-47 so can't really help with this, sorry. Try listing the lvars and input events to see if anything looks applicable. Otherwise, you can inspect the battery switch using the MSFS behaviors windows to see how it works and try and replicate that - see https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/ (for MSFS2020) or https://www.badcasserole.com/uncovering-input-events-using-the-msfs2024-model-behavior-dialog/ (for MSFS2024). Alternatively, ask on the MF MSFS2020 discord channel to see if anyone can provide a preset for you. There should be no issue with switches that have more than one position, but toggle controls will not work with such switches - or may only control the movement between two positions. All aircraft are different in MSFS2020/2024 for most controls, especially add-on aircraft, and you need to determine what works for each aircraft, John

Please update to the latest version of FSUIPC7 - v 7.5.3 (only the latest version is supported). If you still have issue, please show me/attach the full .log and .ini files, not edited extracts. John

FSUIPC6 should certainly compatible with P3Dv4.5 (latest version), but I haven't actually used or tried this in quite a while... Can you show me your FSUIPC6.log and FSUIPC6.ini files please, and give a more detailed explanation of something that isn't working. You may need additional logging, but I need to undettsand what the problem is first. John

That is old and no longer relevant. But what have key assignments got to do with this? I am confused about both the title of this topic and what your actual issue is... Do you mean that you have a physical button assigned to control a virtual button, but this is not working? And if this is assigned in MobiFlight, why are you reporting this here rather than with MobiFlight? I only support FSUIPC, not MobiFlight. Sorry, but no idea what this means either - what Help document? What is a 'key button press', and why should this ' be acknowledged through to the gauges/ displays'? If using FSUIPC, please explain more clearly what your issue is and what this has to do with FSUIPC.

Thanks for updating with the answer!

I just provide the MF presets file as is, exported from their HubHop site - I have no control over the contents. If the name has changed, you will have to update to use the new name. And if you have any questions on why this changed (and not the Lever1 presets), then ask on the MF discord channel. John

Oh, they are FSUIPC7 log files - please do not rename them! One for MSFS2024 shows FSUIPC connected and working properly, the other for MSFS2024 shows also connected and working, but attached when FSUIPC7 was still running - not sure why you attached that. You should always exit FSUIPC7 before attaching files. The "message (2).txt" file shows issues with FSUIPC7 connecting to MSFS2020. What you need to do is to tune the start-up parameters. As you are using the same FSUIPC7 installation for both MSFS2020 and MSFS2024, you will need to tune these to the one that takes the longest (MSFS2020) and then fix them so that they are not changed by MSFS2024. See the following FAQ entry for details (or check the FSUIPC7 Advanced User manual, which has further details): Strat by setting/changing the following ini parameter in the [General] section of your FSUIPC7.ini file: InitialStallTime=0 StartUpTuningDoneVersion=-1 DetectToConnectDelayAuto=60 The first entry will instruct FSUIPC to wait indefinitely for the first connection attempt and not time-out. The second will disable auto-tuning so these parameters will not be changed again by FSUIPC. The third parameter is the delay between when FSUIPC7 detects MSFS running and when it tries to connect, and it is this that you will need to adjust for your system, Try with 60, but time the period between when you see the FSUIPC7 splash-screen and when MSFS2020 arrives at the main menu, and then set this parameter to that time. John

The easiest way to do this is to define your own presets, using the myEvents,txt file (you need to create this file as it won't exist by default - see the section Using Calculator Code Presets on page 50 of the Advanced User guide). Add the following to this file (once created): //Aerosoft/CRJ 550-700-1000/Autopilot ASCRJ_AUTOPILOT_ALTITUDE_INC#(L:ASCRJ_FCP_ALT_SEL,·Number)·10·+·(>L:ASCRJ_FCP_ALT_SEL,·Number)·(L:ASCRJ_FCP_ALT_CHANGE,·Number)·++·(>L:ASCRJ_FCP_ALT_CHANGE,·Number) ASCRJ_AUTOPILOT_ALTITUDE_DEC#(L:ASCRJ_FCP_ALT_SEL,·Number)·10·-·(>L:ASCRJ_FCP_ALT_SEL,·Number)·(L:ASCRJ_FCP_ALT_CHANGE,·Number)·--·(>L:ASCRJ_FCP_ALT_CHANGE,·Number) Once added, you can use the File -> Reload Presets menu item to load them. But looking at the provided presets, there are already some provided for altitude inc/dec: ASCRJ_FCP_ALT_SEL_DEC#(L:ASCRJ_FCP_ALT_CHANGE, number) -- (>L:ASCRJ_FCP_ALT_CHANGE) ASCRJ_FCP_ALT_SEL_INC#(L:ASCRJ_FCP_ALT_CHANGE, number) ++ (>L:ASCRJ_FCP_ALT_CHANGE) Don't they work? If not, you should submit the working ones to Mobiflight (via the HubHop site). John

Does FSUIPC see your hardware? i.e. does it recognise the buttons/switches in the assignment panel? FSUIPC will only recognise HID joystick type devices natively.

But if FSUIPC is not starting/running, no log file will be created. Your log just shows that you manually started FSUIPC7. You can try moving the FSUIPC7 entry up so that it starts before the other entries - I have done this for you in the attached file if you would like to try it. John EXE.xml

Ok - but you initial post said ' especially for Airbus aircraft in the 2020 simulator', which to me means Asobo aircraft, You should always specify the aircraft provider as how you assign/control for the same aircraft from different providers can be (and is usually) very different. I can take a look at the FBW380 (later or tomorrow) but I don't have the Inbuilds so cannot help with that one. What version of the FBW A380 are you using (stable or development)? That is also important to specify when using FBW aircraft.

Did you fix this? If not, please show me/attach your .ini, .log and .JoyScan.csv files and I will take a look. John

It shouldn't be an issue as they have different GUIDs. Glad you managed to sort this out yourself! John