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.

With MobiFlight 9.4 you can now copy an input action from one tab to another

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 Input Actions are available:

MSFS2020 - Custom Input

This input type only works for MSFS2020

This action requires the installation of the latest WASM module.

You can provide the code in the text box that shall be executed by MobiFlight. The code can have a maximum length of 255 characters. There is no syntax check.

You can use simple 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).

Expression syntax is not possible to prevent conflicts with the code.

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.

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

This input type requires FSUIPC and works for all simulators that have FSUIPC support (FSX, P3D)

Some PMDG functions are only accessible through FSUIPC in MSFS2020

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. Have a look at the example configuration for default planes that ships with MobiFlight Connector to see how to configure different offsets like for COM and NAV avionics.

Settings

  • Load preset - select a preset from the list and click use-button to load the values into the base settings
  • Base settings - the differnt values that describe a FSUIPC offset:
    • Offset
    • Value Type - This can be either Int (integer), Float or String, 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 the Customize 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.)

FSUIPC - PMDG EventID

FSUIPC - Jeehell Events

FSUIPC - Lua Macro

Keyboard Input

vJoy - Virtual Joystick