New Input System overview in Unity - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Unity New Input System?

The Unity New Input System is a modern way to handle player input from devices like keyboard, mouse, gamepads, and touchscreens. It replaces the old input system with more flexibility and better device support.

beginner

How does the New Input System improve device support?

It supports many devices automatically, including gamepads, joysticks, touchscreens, and keyboards, and can detect new devices at runtime without extra coding.

beginner

What is an Input Action in the New Input System?

An Input Action is a named input event like 'Jump' or 'Move'. It groups input controls and lets you respond to player actions in a clear way.

intermediate

What is an Input Action Map?

An Input Action Map is a collection of Input Actions grouped by context, like 'Gameplay' or 'UI'. It helps organize inputs and switch between control schemes easily.

intermediate

How do you listen for input events using the New Input System?

You create Input Actions and subscribe to their events in code. When the player performs an action, your code runs automatically to respond.

What does the Unity New Input System replace?

A The Physics Engine

B The Rendering Pipeline

C The old Input Manager

D The Audio System

The New Input System replaces the old Input Manager to provide better input handling.

Which of these is NOT a feature of the New Input System?

A Requires manual device detection

B Allows runtime device detection

C Uses Input Actions to organize inputs

D Supports multiple devices automatically

The New Input System automatically detects devices; manual detection is not required.

What is an Input Action Map used for?

A Rendering graphics

B Grouping Input Actions by context

C Playing sounds

D Saving game data

Input Action Maps group Input Actions by context like gameplay or UI.

How do you respond to player input using the New Input System?

A Subscribe to Input Action events

B Use Update() to check keys manually

C Modify physics settings

D Change camera settings

You subscribe to Input Action events to respond when the player performs actions.

Which device is supported by the New Input System?

A Scanners

B Printers

C Projectors

D Gamepads

Gamepads are supported devices for player input in the New Input System.

Explain the main benefits of using the Unity New Input System over the old Input Manager.

Think about flexibility and ease of use.

Describe how Input Actions and Input Action Maps work together in the New Input System.

Consider how inputs are grouped and managed.

Practice

1. What is the main purpose of the New Input System in Unity?

easy

A. To create 3D models for games

B. To handle multiple input devices easily and flexibly

C. To manage game physics and collisions

D. To optimize game graphics performance

Solution

1. Step 1: Understand the role of input systems

   The New Input System is designed to manage inputs from devices like keyboard, mouse, gamepads, etc.

2. Step 2: Compare with other options

   Options B, C, and D relate to graphics, physics, or modeling, not input handling.

3. Final Answer:

   To handle multiple input devices easily and flexibly -> Option B

4. Quick Check:

   New Input System = device input management [OK]

Hint: Focus on input device management purpose [OK]

Common Mistakes:

• Confusing input system with graphics or physics
• Thinking it only handles keyboard input
• Assuming it creates game assets

2. Which of the following is the correct way to enable an input action in the New Input System?

easy

A. inputAction.Run();

B. inputAction.Start();

C. inputAction.Activate();

D. inputAction.Enable();

Solution

1. Step 1: Recall method names in New Input System

   The method to activate an input action is called Enable(), not Start(), Activate(), or Run().

2. Step 2: Confirm syntax correctness

   inputAction.Enable(); is the correct syntax to enable the action.

3. Final Answer:

   inputAction.Enable(); -> Option D

4. Quick Check:

   Enable() activates input actions [OK]

Hint: Remember Enable() activates input actions [OK]

Common Mistakes:

• Using Start() instead of Enable()
• Confusing method names with Activate() or Run()
• Forgetting parentheses after method name

3. Given this code snippet using the New Input System:

var moveAction = playerInput.actions["Move"];
moveAction.Enable();
var value = moveAction.ReadValue<Vector2>();
Debug.Log(value);

What does value represent?

medium

A. The current 2D vector input from the Move action

B. A boolean indicating if Move is pressed

C. The name of the Move action as a string

D. An integer representing Move action's ID

Solution

1. Step 1: Understand ReadValue<Vector2>()

   This method reads the current input value as a Vector2, typically for movement directions.

2. Step 2: Analyze the variable 'value'

   Since moveAction is enabled and ReadValue<Vector2>() is called, value holds the 2D input vector from the Move action.

3. Final Answer:

   The current 2D vector input from the Move action -> Option A

4. Quick Check:

   ReadValue<Vector2>() returns Vector2 input [OK]

Hint: ReadValue<Vector2>() returns 2D input vector [OK]

Common Mistakes:

• Thinking it returns a boolean
• Confusing value with action name or ID
• Not enabling the action before reading

4. What is wrong with this code snippet using the New Input System?

var jumpAction = playerInput.actions["Jump"];
jumpAction.ReadValue<float>();
jumpAction.Enable();

medium

A. The action is read before it is enabled

B. ReadValue<float>() is not a valid method

C. The action name "Jump" is invalid

D. Enable() should be called twice

Solution

1. Step 1: Check the order of method calls

   The code reads the input value before enabling the action, which means no input is active yet.

2. Step 2: Understand correct usage

   Enable() must be called before reading values to get valid input data.

3. Final Answer:

   The action is read before it is enabled -> Option A

4. Quick Check:

   Enable() must come before ReadValue() [OK]

Hint: Always enable input action before reading values [OK]

Common Mistakes:

• Reading input before enabling action
• Assuming ReadValue<float>() is invalid
• Thinking action names must be changed

5. You want to temporarily stop all player input during a cutscene using the New Input System. Which approach is best?

hard

A. Delete the input action asset during the cutscene

B. Set all input action callbacks to null

C. Call playerInput.actions.Disable() to disable all input actions

D. Ignore input values but keep actions enabled

Solution

1. Step 1: Understand disabling input actions

   Calling Disable() on the actions disables all input reading cleanly and temporarily.

2. Step 2: Evaluate other options

   Deleting assets is destructive, setting callbacks to null is error-prone, ignoring inputs wastes resources.

3. Final Answer:

   Call playerInput.actions.Disable() to disable all input actions -> Option C

4. Quick Check:

   Disable() cleanly stops input during cutscenes [OK]

Hint: Use Disable() to pause all inputs safely [OK]

Common Mistakes:

• Deleting input assets instead of disabling
• Nullifying callbacks causing errors
• Ignoring inputs wastes CPU