November 15, 20205 yr I'm new to Linda, so please forgive me if I talk nonsense. I would like to program a button for the VRi MCP I to switch from 'Managed ALT' to 'Selected ALT' (MSFS Airbus/FlyByWire Mod). I used the Linda console to find the control code 68067 that would trigger that. The only way I found to use that control code was editing the fsx-alpha.lst and fsx-numeric.lst files, but the readme says they should not be modified. The code works and I can finally switch from managed to selected altitude with the MCP panel. What's the proper way to do this, if the fsx-*list files should nat be altered? Would like to do that with a few other controls, too... Edited November 15, 20205 yr by ScotFlieger
November 15, 20205 yr Welcome to LINDA and thank you for your comment. LINDA support to MSFS2020 is limited by the lack of information from Microsoft. I am on the lookout for any improvements. The supplied list of MSFS Controls is unchanged from the days of FSX. I am not aware of any published changes to these for MSFS2020. Should you have a source I would welcome a look. Andrew Gransden Scotland, UK LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew
November 15, 20205 yr Author Don't have a source, but I found the following codes with the console tracer to switch the Airbus between managed and selected modes for speed, altitude and heading. Parameter "2" always sets managed and "1" sets selected. Works for me at least... 68065 HEADING_SLOT_INDEX_SET 68066 SPEED_SLOT_INDEX_SET 68067 ALTUTUDE_SLOT_INDEX_SET
December 18, 20205 yr Tom, how did you use the console tracer to identify these codes? This could be a very good way for us to get the whole/most of the MCP panel to work in the meantime (until Microsoft/Asobo release the Lvars).
January 1, 20215 yr I managed to make the above controls work with the FCU Combo Airbus without editing the fsx-alpha.lst and fsx-numeric.lst files, just appending the below lines of code in the lib-msfs.lua file in the autopilot section function Autopilot_Heading_SET () ipc.control("68065", 1) end function Autopilot_Heading_MANAGED () ipc.control("68065", 2) end function Autopilot_Speed_SET () ipc.control("68066", 1) end function Autopilot_Speed_MANAGED () ipc.control("68066", 2) end function Autopilot_Altitude_SET () ipc.control("68067", 1) end function Autopilot_Altitude_MANAGED () ipc.control("68067", 2) end Then they can be used to map the corresponding events of the rotary knobs on the FCU using the Airbus logic (push = managed, pull = set) Would be indeed useful to check the other "hidden ipcs" of MSFS to complete the mapping. I will look at the next one (68068) which is the Vertical Speed control to see whether I can operate the corresponding knob the same way. Happy new year! Edited January 1, 20215 yr by ydelta
January 1, 20215 yr @ydelta thank you for your work on this. I have tested your suggestions and they work fine for the Asobo A320 Neo. I will incorporate them in the next release. Happy new year. Edited January 1, 20215 yr by ScotFlieger Andrew Gransden Scotland, UK LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew
January 1, 20215 yr You are welcome Andrew, I use them with the A32NX mod by FBW and they work fine too. I am now looking at the VS mapping and it looks a bit more tricky to trigger the set/managed states as for the other knobs The VS_SLOT_INDEX_SET control (ipc 68068) does not work as expected, I am still testing workarounds and keep you posted
Archived
This topic is now archived and is closed to further replies.