Triggering events and failures through key presses

  • I've finally got around to reading the documentation in depth, and I 've come across the part about using key shortcuts as triggers

    Does this mean you can tie any fault or cockpit button to a key press (or click spot?)


    Code
    <[input_event][TriggerEngineFail][]
        <[string8][Message][Controls.Button]>
        <[float64][InputValue][1.0]>
        <[string8][Events][ Engine1FailEvent.Trigger ]>
    >


    Code
    <[event_value][Engine1FailEvent][]
        <[string8][Input][1.0]>
        <[string8][Events][ Engine1FireDetected.Set ]>
    >
  • You can program any inputs in the FS 4, whether virtually as a kind of touchdown or with visible elements. And you can use any events as input. In this article there is an example of this:

    And see here:

    It is the FS 2-Wiki, but also useable for the FS 4.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • I still have additions to operate switches, knobs, buttons or click points on and in the aircrafts:

    (1) The affected camera view must contain the tag "pilot" or "copilot" in the line <[string8][Tags][  ]>, here is an example from the C130:

    Code
                <[camera][CameraCockpitFlightEngineeerFuelControlPanelCentre][]
                    <[string8][Body][Fuselage]>
                    <[tmvector3d][R0][ 10.65 0.01 1.20 ]>
                    <[tmvector3d][Direction][1.0 0.0 1.2]>
                    <[bool][InCockpit][true]>
                    <[bool][Overhead][true]>
                    <[string8][Tags][ cockpit jumpseat copilot ]>
                >

    (2) The contact point of the element must not be more than approx. 4.60 m away from the camera position so that the operation also works.

    The distance limit can be used constructively. For example, you can move click points up by 20 m "out of the view" with touch screens if they are not needed.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • 777Driver April 8, 2026 at 9:06 PM

    Changed the title of the thread from “Triggering events and fauilres through key presses” to “Triggering events and failures through key presses”.
  • ... so much potential for some amazing add-ons.

    🤣 Attention - it can be addictive! 🤣

    FS 4 is also designed in such a way that you can save all additions for an aircraft in the user folder without intervening in the original FS 4 folder.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+