When importing the asset for the first time this message will pop up:

To use only the new InputSystem in the project select Yes. Otherwise, to use the old/classic Unity Input (InputManager) click No and then under Project Settings ⇒ Player ⇒ Input Handling select Both. Otherwise this message will keep popping up each time the project is opened.

Out of the box gamepad bindings are only available for InputSystem.

• Add MobileInputProvider to the scene.
• Create a few UI ⇒ Button objects inside your canvas. Make sure that they are clickable.
• Remove the UnityEngine.UI.Button component and replace it with MobileInputButton. MobileInputButton inherits from UnityEngine.UI.Button and adds hasBeenClicked and isPressed fields which are required for Mobile Input Provider
• Drag the buttons to the corresponding fields in the MobileInputProvider. Empty fields will be ignored.

For more info visit SteeringWheelInputProvider page.

Since v1.0 multiple InputProviders can be present in the scene, meaning that their input has to be combined to get the final input result. To get the combined input use:

float throttle = InputProvider.CombinedInput(i => i.Throttle());
bool engineStartStop = InputProvider.CombinedInput(i => i.EngineStartStop());

Or to get the input from individual InputProviders (say to find out if a button was pressed on a keyboard): <code>float throttle = InputProvider.Instances[0].Throttle;</code> When using input generated by code (i.e. AI) it is usually handy to have access to a single axis throttle/brake. This can be done like so:

vehicleController.input.Vertical = 0.5f; //Sets throttle to 0.5f, resets brakes.
vehicleController.input.Vertical = -0.5f; //Sets brakes to 0.5f, resets throttle.

vehicleController.input.states.throttle is equal to vehicleController.input.Throttle. The latter is just a getter/setter for convenience.

Input in each vehicle is stored in InputStates struct:

myVehicleController.input.states

In case input should not be retrieved from user but from another script - as is the case when AI is used - AutoSettable should be set to false. This will disable automatic input fetching from the active InputProvider.
Input now can be set from any script:

myVehicleController.input.Horizontal = myFloatValue; // Using getter/setter.

myVehicleController.input.states.horizontal = myFloatValue; // Directly accessing states.

If a custom InputProvider is needed it can easily be written. Custom InputProviders allow for new input methods or for modifying the existing ones. E.g. if the MobileInputProvider does not fit the needs of the project a copy of it can be made and modifications done on that copy. That way it will not get overwritten when the asset is updated.

Steps to create a new InputProvider:

• Create a new class, e.g. ExampleInputProvider and make it inherit from InputProvider class:

public class ExampleInputProvider : InputProvider {}

• Implement missing methods. Most IDEs can do this automatically.
• The required methods are abstract and will need to be implemented. There are also virtual methods such as ToggleGUI() which are optional and will be ignored if not implemented.
• Methods that are not used should return false, 0 or -999 in case of ShiftInto() method.