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.

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 Aerodynamics the project will be missing the required bindings in Unity Input Manager. There are two ways to add those:

1. Manually adding each entry to the Project Settings ⇒ Input following the input bindings table.
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 a text editor of your choice.
   • Copy the contents of the provided InputBindings.txt file (NWH ⇒ Aerodynamics ⇒ Scripts ⇒ 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. Also make sure that all the indents are correct. Save the file.
   • Open Unity. Check Project Settings ⇒ Input. The input bindings for NWH Aerodynamics 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. 'InputManagerAircraftInputProvider'
2. 'InputManagerSceneInputProvider'

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

• 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 InputSystemAircraftInputProvider 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.

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 ailerons = InputProvider.CombinedInput(i => i.Ailerons());
bool landingGear = InputProvider.CombinedInput(i => i.LandingGear());

Or to get the input from individual InputProviders (say to find out if a button was pressed on a keyboard):

float ailerons = InputProvider.Instances[0].Ailerons;

Input in each vehicle is stored in InputStates struct:

myAircraftInputManager.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 InputProviders.

Input now can be set from any script:

myAircraftInputManager.Ailerons = myFloatValue;

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 are 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 AircraftInputProviderBase or SceneInputProviderBase classes.
• Implement wanted methods. Most IDEs can do this automatically.