Input action maps in Unity - Performance & Optimization

Performance: Input action maps

MEDIUM IMPACT

Input action maps affect how quickly and efficiently user inputs are processed and responded to in the game, impacting input responsiveness and frame rate.

Handling player input with action maps

Unity

private InputAction jumpAction;
private InputAction interactAction;

void OnEnable() {
  jumpAction.Enable();
  interactAction.Enable();
  jumpAction.performed += ctx => Jump();
  interactAction.performed += ctx => Interact();
}

void OnDisable() {
  jumpAction.Disable();
}

Using InputAction callbacks avoids polling every frame and only triggers code when input occurs, reducing CPU usage and improving responsiveness.

📈 Performance GainInput processed only on events, reducing CPU usage and input lag significantly.

Handling player input with action maps

Unity

void Update() {
  if (Input.GetKeyDown(KeyCode.Space)) {
    Jump();
  }
  if (Input.GetKeyDown(KeyCode.E)) {
    Interact();
  }
  // Multiple if checks every frame
}

Checking multiple input keys manually every frame causes unnecessary CPU usage and can lead to missed inputs or lag.

📉 Performance CostTriggers input polling every frame for each key, increasing CPU load and potentially causing input lag.

Performance Comparison

Pattern	Input Polling	CPU Usage	Input Lag	Verdict
Polling keys every frame	High (multiple checks)	High	Higher lag due to constant checks	[X] Bad
Using InputAction callbacks	Low (event-driven)	Low	Minimal lag, responsive input	[OK] Good

Rendering Pipeline

Input action maps process input events before the frame update cycle, triggering callbacks that update game state and UI accordingly.

→Input Processing

→Game Logic Update

→Rendering

⚠️ BottleneckInput Processing stage can become expensive if polling is done inefficiently every frame.

Core Web Vital Affected

INP

Input action maps affect how quickly and efficiently user inputs are processed and responded to in the game, impacting input responsiveness and frame rate.

Optimization Tips

1Use InputAction callbacks instead of polling keys every frame.

2Enable and disable input actions properly to avoid unnecessary processing.

3Profile input handling to ensure minimal CPU usage and low input lag.

Performance Quiz - 3 Questions

What is the main performance benefit of using InputAction callbacks over polling keys every frame?

A Input is processed only when an event occurs, reducing CPU usage.

B It increases the number of input checks per frame.

C It delays input processing until the next frame.

D It requires more memory to store input states.

DevTools: Profiler

How to check: Open Unity Profiler, record while playing, check CPU usage under Input and Scripts sections.

What to look for: Look for high CPU time spent in input polling or Update methods indicating inefficient input handling.

Practice

1.

What is the main purpose of an Input Action Map in Unity's Input System?

easy

A. To handle audio playback

B. To render graphics on the screen

C. To store game settings permanently

D. To group related input actions for easier management

Solution

1. Step 1: Understand what Input Action Maps do

   Input Action Maps group related input actions, like movement or UI controls, to organize inputs.

2. Step 2: Compare with other options

   Rendering graphics, storing settings, and audio playback are unrelated to input action maps.

3. Final Answer:

   To group related input actions for easier management -> Option D

4. Quick Check:

   Input Action Maps = Group inputs [OK]

Hint: Remember: Action maps group inputs logically [OK]

Common Mistakes:

• Confusing input maps with graphics or audio systems
• Thinking action maps store data permanently
• Assuming action maps handle rendering

2.

Which of the following is the correct way to enable an InputActionMap named playerControls in C#?

?

easy

A. playerControls.Activate();

B. playerControls.Start();

C. playerControls.Enable();

D. playerControls.Run();

Solution

1. Step 1: Recall the method to enable input action maps

   The correct method to enable an InputActionMap is Enable().

2. Step 2: Verify other options

   Start(), Activate(), and Run() are not valid methods for InputActionMap.

3. Final Answer:

   playerControls.Enable(); -> Option C

4. Quick Check:

   Enable() activates input maps [OK]

Hint: Use Enable() to start input action maps [OK]

Common Mistakes:

• Using Start() instead of Enable()
• Confusing method names with other Unity components
• Forgetting to enable the action map before use

3.

Given the following code snippet, what will be the output when playerControls is enabled and the player presses the jump button?

var playerControls = new PlayerInputActions();
playerControls.Player.Jump.performed += ctx => Debug.Log("Jump pressed");
playerControls.Player.Enable();
// Player presses jump button

medium

A. Jump pressed

B. No output

C. NullReferenceException

D. Jump pressed twice

Solution

1. Step 1: Understand event subscription and enabling

   The code subscribes to the Jump action's performed event and enables the Player action map.

2. Step 2: Predict output on jump button press

   When the jump button is pressed, the subscribed lambda logs "Jump pressed" once.

3. Final Answer:

   Jump pressed -> Option A

4. Quick Check:

   Subscribed event triggers log once [OK]

Hint: Enabling action map triggers subscribed events [OK]

Common Mistakes:

• Forgetting to enable the action map
• Expecting multiple logs without multiple subscriptions
• Confusing event names or missing subscription

4.

What is wrong with this code snippet that tries to disable an input action map?

var controls = new PlayerInputActions();
controls.Player.Disable();
controls.Player.performed += ctx => Debug.Log("Action performed");

medium

A. The event subscription is on the action map instead of a specific action

B. Disable() method does not exist on InputActionMap

C. You cannot disable an action map before subscribing to events

D. The code should call Enable() before Disable()

Solution

1. Step 1: Check event subscription target

   The code subscribes to performed on controls.Player, which is an InputActionMap, not an InputAction.

2. Step 2: Understand correct subscription

   Events like performed belong to InputActions, e.g., controls.Player.Jump.performed, not the whole map.

3. Final Answer:

   The event subscription is on the action map instead of a specific action -> Option A

4. Quick Check:

   Subscribe events on actions, not maps [OK]

Hint: Subscribe events on actions, not action maps [OK]

Common Mistakes:

• Subscribing events on InputActionMap instead of InputAction
• Confusing Disable() method availability
• Assuming order of Enable/Disable affects subscription

5.

You want to switch between two control schemes, Keyboard and Gamepad, during gameplay using input action maps. Which approach correctly handles this switch?

?

hard

A. Use only one action map and ignore control schemes

B. Disable the current action map and enable the other action map

C. Create new input actions every time you switch

D. Enable both action maps at the same time

Solution

1. Step 1: Understand control scheme switching

   Switching control schemes means activating one input action map and deactivating the other to avoid conflicts.

2. Step 2: Evaluate options

   Enabling both maps causes input conflicts; creating new actions wastes resources; ignoring schemes loses flexibility.

3. Final Answer:

   Disable the current action map and enable the other action map -> Option B

4. Quick Check:

   Switch by toggling action maps [OK]

Hint: Toggle action maps to switch control schemes [OK]

Common Mistakes:

• Enabling multiple action maps causing input conflicts
• Recreating actions unnecessarily
• Ignoring control scheme differences