The module is designed to work as you would expect a controller / mouse input to work. Events for button presses, dragging, and similar are sent in response to input.
The module sends pointer events to components as a mouse / input device is moved around, and uses the Graphics Raycaster and Physics Raycaster to calculate which element is currently pointed at by a given pointer device. You can configure these raycasters to detect or ignore parts of your SceneA Scene contains the environments and menus of your game. Think of each unique Scene file as a unique level. In each Scene, you place your environments, obstacles, and decorations, essentially designing and building your game in pieces. More info
See in Glossary, to suit your requirements.
The module sends move events and submit / cancel events in response to Input tracked via the Input managerA Unity window where you can define all the different input axes, buttons and controls for your Project. More info
See in Glossary. This works for both keyboard and controller input. The tracked axis and keys can be configured in the module’s inspectorA Unity window that displays information about the currently selected GameObject, Asset or Project Settings, alowing you to inspect and edit the values. More info
See in Glossary.
|Horizontal Axis||Type the desired manager name for the horizontal axis button.|
|Vertical Axis||Type the desired manager name for the vertical axis.|
|Submit Button||Type the desired manager name for the Submit button.|
|Cancel Button||Type the desired manager name for the Cancel button.|
|Input Actions Per Second||Number of keyboard/controller inputs allowed per second.|
|Repeat Delay||Delay in seconds before the input actions per second repeat rate takes effect.|
|Force Module Active||Tick this checkbox to force this Standalone Input Module to be active.|
The module uses:
The flow for the module is as follows
Did you find this page useful? Please give it a rating: