John Dowson

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

No point changing any parameters if FSUIPC7 is not starting - they are for tuning the connection to MSFS. For all suto-start issues, see the FAQ section (or one if the several hundred posts where this is reported, that refer to the FAQ entry) where ALL information on auto-start issues xan be found.

That should be possible, either with direct assignments or if not then via a lua script. I think the default key assignments for throttle inc/dec in MSFSare F2 and F3. Did you assign for that or were these the default assignments? Have you tried the same in the Asobo A310? I am currently on holiday until next week (see post above) and so cannot really advise further or take a look until I return. But I am not that familiar with the Airbus/A310 - does it have fixed detents for these positions? I thought the throttle in the A310 was a full range throttle, and if that is the case (i.e. no fixed detents) then I would need to know the throttle position/percentage for each of those positions (CLOIMB, FLEX and TOGA). John

See

Ok, thanks for the update. Your install log did show that it did not detect your MSFS2020 installation: The installer looks for the UserCfg.opt file for each MSFS version to determine if it is installed or not, which should be in a specific location for both Steam and MS Store versions. If this file can't be found, it won't detect that version. It is strange that the UserCfg.opt file for MSFS2020 was removed though... John

Why not just update? It only takes a few minutes... Otherwise check the documentation or search this forum...I am sure this has been asked before... I think the OpenOnStart (or similar) ini parameter set to Never may prevent this, but I am not sure... I am on holiday now until next week, and can check further then. John P.S. Please use the FSUIPC7 sub-forum for all questions/issues with FSUIPC7. I have moved this post.

The GUIDs of your devices have most probably changed. To resolve this, you need to update the [JoyNames] section in your FSUIPC7.ini file. New letter entried will have been added to that section. You need to copy the GUID strings from the new entries and use those/paste them in the original letter entries, then delete the new letter entries. Do this when FSUIPC is not running. If you attach your ini file, I could do this for you. But I am now on holiday and cant do this until next week (difficult on a phone!), so please try yourself. Any issues, attach your ini and I will take a look when possible. John

Then MSFS2020 was not detected. Please show me / attach your InstallFSUIPC7.log file. You should ALWAYS attach this if you have installation issues.

I don't understand why you keep messing around so much with your devices and creating such a mess. Looking at you registry, you have all these entries: and the log file is reporting duplicate ids: You need to do exactly the same as I suggested the last time this occurred - clean your registry and update the GUIDs to the new ones on your assigned JoyLetters, and remove the other entries. Sorry, but I just don't have time to look at this in any more detail at the moment (and I am on holiday from the 2nd - 7th April). I can help again sometime later next week, but I am just too busy to look at this in detail at the moment. Go over the last post and try and understand what you did to resolve it the last time. Report back after the 8th AApril if you require further assistance.

Ok, that probably changed with the SU1 update - that offset holds the version number (major*10 + minor) as received from the FS. I will update the documentation to reflect this. Thanks for reporting. John