Set up input from different sources to be used in ORK Framework
Input keys are found in Controls > Input Keys.
Input keys build a control layer between ORK and various input sources (e.g. the game engine’s input system or 3rd party solutions). This allows inputs to be set via Control HUDs (for virtual on screen controls, e.g. on mobile platforms), schematics (Set Input Key node) or via scripting.
General Settings #
The general settings define settings not bound to a specific input key.
Unity: Load Input Actions #
This is only available in Unity and used for input actions of the new input system.
It allows you to load not yet used input actions from a provided input action asset.
New input keys will be created for each input action that hasn’t yet been used by another input key.
Input Rebinding #
Input rebinding allows the player to change the input source for an input key. Rebinding is based on the input ID currently used for the options menu – i.e. also depending on where it was called from. E.g. for local multiplayer, each player can define their own controls via menu screens.
You can define what happens when rebinding an already used input, e.g. keeping both inputs, swapping the inputs or setting the other input to none.
Rebinding can only use input sources that are added to the settings here.
Cancel Key #
Optionally define an input key used to cancel input rebinding.
Please note that the cancel key’s input source can’t be used for rebinding. E.g. when bound to Escape, the escape key can’t be used to bind any other input to it.
Bind Audio #
Optionally play an audio clip when binding an input key to a new input source.
Rebind Info Dialogue #
Optionally show a rebind info dialogue while rebinding an input.
The dialogue can show content information about the input key as well as the current bound input source (e.g. key code).
Input Search #
Rebinding will search the defined input sources that are added here. Inputs are found on pressing down an input (e.g. key or mouse down).
You can add the input sources you want to be able to be found. The available types depend on the game engine.
Input IDs #
Input IDs allow having multiple input origins for an input key. They’re used to create different control styles/layouts or allow local multiplayer controls.
The default (global) input ID is 0 when starting a game. Machine components can either use the default input ID or override it, i.e. this can be used to have machines with the same schematic react to different input.
The global input ID can also be changed in-game, e.g. for switching control styles.
The minimum input ID is 0, an input ID of -1 can be used to check for any inputs of an input key (ignoring input ID).
Example #
The Accept and Cancel input keys have 2 input origins each.
Accept uses joystick button 1 for input ID 0 and joystick button 2 for input ID 1.
Cancel uses joystick button 2 for input ID 0 and joystick button 1 for input ID 1.
Switching the global input ID between 0 and 1 allows switching the Accept and Cancel input key’s buttons.
Input Origins #
The input origin defines where an input ID key’s input is coming from. There are several input origins available out of the box and you can use the Custom input origin to quickly connect 3rd party input systems via reflection.
You can also create custom input origins by deriving your class from the BaseInputIDKeySetting. Check out the included input origins for examples.
ORK Input Origins #
The following input origins are available in all game engines.
Custom #
A custom control script is used.
Input Key #
Other input keys are used.
Key Combo #
A key combo sequence is used.
Mouse #
A mouse button is used (uses mouse cursor position change as axis).
Please note that the axis is based on mouse cursor movement, i.e. it’ll not work during locked cursor.
None #
No direct input is used. Input from a HUD, schematics or code can still be used.
Touch #
A touch is used (uses touch position change as axis).
This is only used if the game engine supports touch inputs.
Unity Input Origins #
The following input origins are available in Unity.
Acceleration #
A selected axis of the last linear acceleration of a device is used.
Action (Input System) #
An input action from the Unity input system is used.
Gamepad Button (Input System) #
The defined gamepad button is used.
Gyroscope #
A selected axis of gyroscope data of a device is used.
Key Code (via extension) #
The key mapped to the selected key code is used.
This uses the legacy input system and requires the legacy input extension (download here).
Keyboard Key (Input System) #
The defined keyboard keys are used.
Rewired (via extension) #
A Rewired input is used.
This uses Rewired and requires the Rewired extension (download here).
Unity Input Manager (via extension) #
A key defined in the Unity input manager is used.
This uses the legacy input system and requires the legacy input extension (download here).

