The input in NWH Vehicle Physics 2 centers around InputProviders. These are scripts that take user input (e.g. keypresses, mouse movement, gamepad input, etc.), process it and pass it on to the vehicles.

Process of retrieving input from different sources using InputProvider system.

The diagram above explains the path from input source to vehicle input state:

1. Input is retrieved from hardware through Input Sources (green). This can be input from any input method available for Unity. In this example InputManager (old/standard Unity input), touchscreen/sensors (mobile input) and LogitechSDK for steering wheel input.
2. InputProviders pass this input to the vehicle (VehicleController.InputHandler). Input from all input sources is combined and processed depending on settings for that particular vehicle.
3. If the Auto Set Input is set to false the state of the corresponding input for the vehicle in question will be set to the combined value of all inputs.
4. If the VehicleController has Input > AutoSetInput set to false the new input will be discarded. This happens in case the vehicle is inactive or the input is being set by some other script (e.g. AI).

• A single InputProvider provides the input for all the vehicles so it is recommended to only have one InputProvider of particular type (e.g. one desktop and one mobile input provider - this will allow the vehicles to get both desktop and mobile input at the same time).
• Input providers just provide the input, they do not set it. Vehicles themselves get the input from input providers if AutoSetInput is enabled.
• All InputProviders inherit from either VehicleInputProvider (for vehicle-related input) or SceneInputProvider (for scene-related input such as cameras). Therefore it is best to think about InputProviders as a standardized interface between different input methods and a vehicle.
• InputProviders are split into VehicleInputProviders and SceneInputProviders. VehicleInputProviders relay vehicle input (throttle, brakes, etc.) while SceneInputProviders take care of scene input (vehicle changing, camera changing, camera movement and the rest of the inputs not directly related to vehicle. One of each needs to be present (e.g. InputSystemVehicleProvider and InputSystemSceneInputProvider).
• Multiple different InputProviders can be present in the scene (v1.0 or newer required). E.g. InputSystemProviders and MobileInputProviders can be used in the same scene. The resulting input will be a sum of inputs from all InputProviders in case of numeric inputs and logical OR operation of all inputs in case of boolean inputs.
• Input is stored inside InputStates struct and can be copied over from one vehicle to another. E.g. this is what is done when a trailer is connected to a towing vehicle.
• To manually set the InputStates make sure Auto Set Input is set to false.

All input providers inherit from either VehicleInputProviderBase or SceneInputProviderBase, but differ in their implementation. To create a new input provider simply inherit from one of those two classes and implement the members.

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

Both Yes or No can be selected but it is important to set the Project Settings ⇒ Player ⇒ Input Handling to Both afterwards. This way both new InputSystem and the old InputManager will work. If this setting is set to InputManager only errors might appear as the demo scenes of the asset rely on InputSystem.
If a message This Unity Package has Package Manager dependencies. appears, click Install/Upgrade.

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

• Type of InputProvider for handling user input on desktop devices through keyboard and mouse or gamepad.
• Uses classic/old Unity Input Manager. It is recommended to use the Unity's new Input System instead for new projects.

Since v1.1 InputSystem package is required even if not used. If using the old/classic Unity input set Project Settings ⇒ Player ⇒ Input Handling to Both and proceed as normal. InputSystem package being present installed will not interfere with old/classic Unity input / InputManager.

When first importing NWH Vehicle Physics 2 the project will be missing required bindings. There are two ways to add those:

1. Manually adding each entry to the Project Settings ⇒ Input following the input bindings table available here.
2. Copying the contents of InputBindings.txt and appending them to the contents of the [UnityProjectPath]/ProjectSettings/InputManager.asset file. To do so:
   • Close Unity.
   • Open InputManager.asset in Notepad/Notepad++/Visual Studio or any other text editor of your choice.
   • Copy the contents of the provided InputBindings.txt file (Scripts ⇒ Vehicle ⇒ Control ⇒ Input ⇒ InputProviders ⇒ InputManagerProvider ⇒ InputBindings.txt) and paste them at the end of the InputManager.asset. Make sure there are no empty lines between the existing content and the pasted content. Save the file.
   • Open Unity. Check Project Settings ⇒ Input. The input bindings for NWH Vehicle Physics will appear towards the bottom of the list.

To set up InputManager-based input in the scene add the following components to the scene:

1. 'InputManagerVehicleInputProvider'
2. 'InputManagerSceneInputProvider'

Any vehicle that is present in the scene will now receive input from these providers.

Default InputActions.

• Since v1.1 NWH Vehicle Physics 2 has moved to InputSystem as a default input method.
• InputSystem v1.0 or higher is required. This is available in Unity 2019.3 or newer.

When using DS4Windows, InputSystem will detect button presses twice.

• Install 'Input System' package through Window ⇒ Package Manager
• Under Edit ⇒ Project Settings ⇒ Player ⇒ Other Settings ⇒ Active Input Handling select Input System Package (New) or Both - the latter in case your project still uses UnityEngine.Input somewhere.

• Add InputSystemVehicleInputProvider and InputSystemSceneInputProvider to any object in your scene.
• Default bindings can be modified by double clicking on .inputactions files. Save Asset must be clicked for the changes to take effect.

• Add MobileVehicleInputProvider and MobileSceneInputProvider 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 MobileVehicleInputProvider and MobileSceneInputProvider inspectors. 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.