New Input System overview in Unity - Performance & Optimization

Performance: New Input System overview

MEDIUM IMPACT

This affects how quickly and efficiently user inputs are processed and how responsive the game feels.

Handling player input in a Unity game

Unity

void OnEnable() {
  var playerInput = new PlayerInput();
  playerInput.Player.Jump.performed += ctx => Jump();
  playerInput.Enable();
}

Uses event-driven input handling that triggers only on input events, reducing unnecessary checks.

📈 Performance GainNon-blocking input processing; reduces CPU usage and improves input responsiveness.

Handling player input in a Unity game

Unity

void Update() {
  if (Input.GetKeyDown(KeyCode.Space)) {
    Jump();
  }
}

Uses the old Input class which polls input every frame and can cause missed inputs or lag in complex scenes.

📉 Performance CostBlocks input processing until Update runs; can cause input lag especially with many objects.

Performance Comparison

Pattern	Input Checks	CPU Usage	Input Lag	Verdict
Old Input.GetKeyDown polling	Runs every frame	Higher due to constant polling	Higher due to frame delay	[X] Bad
New Input System event callbacks	Runs only on input events	Lower due to event-driven model	Lower due to immediate event handling	[OK] Good

Rendering Pipeline

Input events are captured asynchronously and dispatched to listeners without blocking the main game loop, improving responsiveness.

→Input Processing

→Game Logic Update

⚠️ BottleneckPolling input every frame in Update causes delays and missed inputs.

Core Web Vital Affected

INP

This affects how quickly and efficiently user inputs are processed and how responsive the game feels.

Optimization Tips

1Avoid polling inputs every frame; use event callbacks instead.

2Enable input actions only when needed to save CPU.

3Use the Profiler to monitor input processing times for responsiveness.

Performance Quiz - 3 Questions

What is a key performance advantage of the New Input System over the old Input class in Unity?

A It uses event-driven input handling instead of polling every frame.

B It requires less memory for storing input states.

C It automatically optimizes graphics rendering.

D It reduces the size of the game build.

DevTools: Profiler

How to check: Open Unity Profiler, record while playing, look at CPU usage and input event handling times.

What to look for: Lower CPU time spent in input processing and faster response to input events indicate good performance.

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