Input Actions - MobiFlight/MobiFlight-Connector GitHub Wiki
MobiFlight provides different options as Input Actions when a user triggers an input event, e.g. by pressing a button, turning an encoder or potentiometer.
Input Events
- Button - onPress
- Button - onRelease
- Encoder - on Left
- Encoder - on LeftFast
- Encoder - on Right
- Encoder - on RightFast
- Analog Input - onChange
For these events, the following actions are available:
Microsoft Flight Simulator
[!TIP] This is the preferred method of interacting with Microsoft Flight Simulator 2020 and 2024.
The preset list contains thousands of known events for flight simulator. For popular aircraft chances are the event you want to trigger is in the dropdowns. Use the search box and dropdowns to find the one you need.
To enter custom event code check the Show Preset Code
option.
You can use simple replacements such as @ for the current input value from an analog input (e.g. potentiometer), and you can reference placeholders defined for the config on the config reference tabs. MSFS RPN expressions are also supported.
MobiFlight - variable
You can store values in MobiFlight variables when a user triggers an input event.
Settings
- Type - Number or String. Number stores value for variable as number; String stores value for variable as String.
- Name - The name of the variable. There are no restriction or conventions. Names are case-senstive, e.g. "myVar" is not the same as "MYVAR" or "myvar"
- Value - the value that you would like to store. You can use replacements, e.g. @ for the current input value (makes sense for the potentiometer), and you can reference placeholders defined for the config (on the config reference tabs). The value field also supports expressions.
MobiFlight - Retrigger Switches
The retrigger input action allows you to send all current switch states from all connected boards to MobiFlight which will then execute all actions for these events. This is helpful when your cockpit state and the state of your switches got out of sync. After retrigger, the states should no be in sync again.
FSUIPC - Offset
[!IMPORTANT] If you fly with Microsoft Flight Simulator 2020 or 2024 use the Microsoft Flight Simulator action type instead. For PMDG aircraft in MSFS see the FSUIPC - PMDG - EventId action type.
This input type requires FSUIPC and works for all simulators that have FSUIPC support (FSX, P3D)
You can set a value of an FSUIPC offset. The options are very similiar to the ones that are described in the section of the FSUIPC settings for the (Output) Config Wizard.
The main difference is, that you have the "value"-field where you specify the actual value that shall be written to the FSUIPC offset. You can reference the current value of the offset "$" and can use the expression engine syntax for complex calculations.
Settings
- Load preset - select a preset from the list and click
use
-button to load the values into thebase settings
- Base settings - the differnt values that describe a FSUIPC offset:
- Offset
- Value Type - This can be either
Int
(integer),Float
orString
, use the information from the FSUIPC Offset Status doc - Size in Bytes - use the information from the FSUIPC Offset Status doc
- Mask value with - some offsets require a bit mask, e.g. lights
- BCD mode - some offsets require this mode, e.g. frequencies
- More options
- Set Value - the value that you would like to store. You can use replacements, e.g. @ for the current input value (makes sense for the potentiometer), and you can reference placeholders defined for the config (on the config reference tabs). The value field also supports expressions.
FSUIPC - EventID
Settings
- Load preset - select a preset from the list and click
use
-button to load the values into theCustomize Settings
area - Customize Settings - the differnt values that describe a FSUIPC EventID:
- EventID - the EventID, use the information from the FSUIPC Offset Status doc
- Para - some EventIDs allow for parameters
Parameters support
expressions
where@
is the current input value, and also other placeholders ($,#,etc.)