Input axis for smooth movement in Unity - Step-by-Step Execution

Concept Flow - Input axis for smooth movement

Start

↓

Read Input Axis

↓

Calculate Movement Vector

↓

Apply Movement to Object

↓

Update Frame

↩Back to Read Input Axis

The program reads the input axis value each frame, calculates movement smoothly, applies it to the object, and repeats every frame.

Execution Sample

Unity

float moveX = Input.GetAxis("Horizontal");
float moveZ = Input.GetAxis("Vertical");
Vector3 move = new Vector3(moveX, 0, moveZ);
transform.Translate(move * speed * Time.deltaTime);

This code reads horizontal and vertical input axes, creates a movement vector, and moves the object smoothly based on input.

Execution Table

Frame	Input.GetAxis("Horizontal")	Input.GetAxis("Vertical")	Movement Vector (x,y,z)	Action	Object Position Change
1	0.0	0.0	(0.0, 0, 0.0)	No movement	No change
2	0.5	0.0	(0.5, 0, 0.0)	Move right slowly	Position moves right by 0.5 * speed * Time.deltaTime
3	1.0	0.0	(1.0, 0, 0.0)	Move right faster	Position moves right by 1.0 * speed * Time.deltaTime
4	0.0	1.0	(0.0, 0, 1.0)	Move forward	Position moves forward by 1.0 * speed * Time.deltaTime
5	-0.5	0.5	(-0.5, 0, 0.5)	Move diagonally left-forward	Position moves diagonally by vector * speed * Time.deltaTime
6	0.0	0.0	(0.0, 0, 0.0)	Stop movement	No change

💡 Loop continues each frame reading input until program stops

Variable Tracker

Variable	Start	After Frame 1	After Frame 2	After Frame 3	After Frame 4	After Frame 5	After Frame 6
moveX	0.0	0.0	0.5	1.0	0.0	-0.5	0.0
moveZ	0.0	0.0	0.0	0.0	1.0	0.5	0.0
move Vector	(0,0,0)	(0,0,0)	(0.5,0,0)	(1,0,0)	(0,0,1)	(-0.5,0,0.5)	(0,0,0)

Key Moments - 3 Insights

Why does the movement feel smooth instead of jumping suddenly?

Because Input.GetAxis returns values gradually changing between -1 and 1, not just -1, 0, or 1. This gradual change is shown in the execution_table rows where moveX and moveZ change smoothly.

What happens if you use Input.GetAxisRaw instead of Input.GetAxis?

Input.GetAxisRaw returns only -1, 0, or 1 instantly, causing movement to jump suddenly without smoothing. This contrasts with the smooth gradual values seen in the execution_table.

Why multiply by Time.deltaTime when moving the object?

Multiplying by Time.deltaTime makes movement frame-rate independent, so the object moves the same speed regardless of how fast frames update. This keeps movement smooth and consistent.

Visual Quiz - 3 Questions

Look at the execution_table, what is the movement vector at Frame 3?

A (0.0, 0, 1.0)

B (0.5, 0, 0.0)

C (1.0, 0, 0.0)

D (-0.5, 0, 0.5)

💡 Hint

Check the 'Movement Vector (x,y,z)' column at Frame 3 in the execution_table.

At which frame does the object move diagonally?

A Frame 2

B Frame 5

C Frame 4

D Frame 6

💡 Hint

Look for movement vectors with both x and z non-zero in the execution_table.

If Input.GetAxis("Horizontal") returned only -1, 0, or 1 instantly, how would the movement vector change?

A It would jump suddenly between values

B It would stay at zero always

C It would change smoothly like in the table

D It would become negative only

💡 Hint

Refer to key_moments about difference between Input.GetAxis and Input.GetAxisRaw.

Concept Snapshot

Input.GetAxis reads smooth input values between -1 and 1.
Use these values to create a movement vector.
Multiply by speed and Time.deltaTime for smooth, frame-independent movement.
Apply movement vector to transform.Translate each frame.
This creates smooth player movement responding to input gradually.

Full Transcript

This example shows how Unity's Input.GetAxis method reads smooth input values for horizontal and vertical movement. Each frame, the program reads these values, creates a movement vector, and moves the object accordingly. The values change gradually, not instantly, which makes movement smooth. Multiplying by Time.deltaTime ensures movement speed is consistent regardless of frame rate. The execution table traces input values and movement vectors frame by frame, showing how the object's position changes smoothly. Key moments clarify why Input.GetAxis smooths input and why Time.deltaTime is important. The visual quiz tests understanding of these step-by-step changes.

Practice

1. What does the Unity Input.GetAxis function return when used for movement?

easy

A. A string describing the input device

B. An integer value of either 0 or 1 indicating button press

C. A boolean value true if any key is pressed

D. A smooth float value between -1 and 1 representing input strength

Solution

1. Step 1: Understand Input.GetAxis behavior

   Input.GetAxis returns a float value that smoothly changes between -1 and 1 based on input device movement, like joystick or keyboard keys.

2. Step 2: Compare with other input types

   Unlike Input.GetButton or Input.GetKey, it does not return boolean or integer but a float for smooth control.

3. Final Answer:

   A smooth float value between -1 and 1 representing input strength -> Option D

4. Quick Check:

   Input.GetAxis returns float between -1 and 1 [OK]

Hint: Remember: GetAxis gives smooth float, not just on/off [OK]

Common Mistakes:

• Thinking it returns only 0 or 1
• Confusing with boolean input methods
• Expecting integer values instead of float

2. Which of the following is the correct syntax to read horizontal input axis in Unity?

easy

A. float move = Input.GetAxis.Horizontal();

B. float move = Input.GetAxis(Horizontal);

C. float move = Input.GetAxis("Horizontal");

D. float move = Input.GetAxis['Horizontal'];

Solution

1. Step 1: Check method usage

   Input.GetAxis requires a string parameter with axis name in quotes, e.g., "Horizontal".

2. Step 2: Validate syntax correctness

   float move = Input.GetAxis("Horizontal"); uses correct method call with parentheses and string argument. Other options misuse syntax with missing quotes, wrong brackets, or dot notation.

3. Final Answer:

   float move = Input.GetAxis("Horizontal"); -> Option C

4. Quick Check:

   Use parentheses and quotes for axis name [OK]

Hint: Always put axis name in quotes inside GetAxis() [OK]

Common Mistakes:

• Omitting quotes around axis name
• Using square brackets instead of parentheses
• Calling GetAxis as a property instead of method

3. What will be the output of the following Unity C# code snippet if the player presses the right arrow key for horizontal input?

float horizontal = Input.GetAxis("Horizontal");
float speed = 5f;
float movement = horizontal * speed * Time.deltaTime;
Debug.Log(Math.Round(movement, 2));

medium

A. A positive float value close to 0.08 (assuming 60 FPS)

B. Zero, because Input.GetAxis returns only integers

C. A negative float value

D. An error because Time.deltaTime is not used correctly

Solution

1. Step 1: Understand Input.GetAxis with right arrow

   Pressing right arrow sets horizontal axis near +1 smoothly.

2. Step 2: Calculate movement value

   Movement = 1 * 5 * (1/60) ≈ 0.0833, rounded to 0.08.

3. Final Answer:

   A positive float value close to 0.08 (assuming 60 FPS) -> Option A

4. Quick Check:

   Right arrow -> horizontal ~1 -> movement ~0.08 [OK]

Hint: Multiply axis by speed and deltaTime for smooth movement [OK]

Common Mistakes:

• Assuming Input.GetAxis returns only 0 or 1
• Ignoring Time.deltaTime in movement calculation
• Confusing positive and negative axis values

4. Identify the error in this Unity C# code for smooth horizontal movement:

float move = Input.GetAxis(Horizontal);
transform.Translate(move * speed * Time.deltaTime, 0, 0);

medium

A. Missing quotes around "Horizontal" in GetAxis

B. Using Translate instead of MovePosition

C. Multiplying by Time.deltaTime is incorrect

D. Variable 'speed' is not declared

Solution

1. Step 1: Check GetAxis parameter syntax

   The axis name must be a string in quotes. Here, Horizontal is used without quotes causing a compile error.

2. Step 2: Verify other code parts

   Using Translate with speed and Time.deltaTime is correct. Variable 'speed' is assumed declared elsewhere.

3. Final Answer:

   Missing quotes around "Horizontal" in GetAxis -> Option A

4. Quick Check:

   Axis names need quotes in GetAxis() [OK]

Hint: Always put axis names in quotes to avoid errors [OK]

Common Mistakes:

• Forgetting quotes around axis name
• Confusing Translate with other movement methods
• Assuming Time.deltaTime is optional

5. You want to move a character smoothly left and right using the horizontal axis, but only when the input magnitude is greater than 0.1 to avoid tiny unwanted movements. Which code snippet correctly implements this in Unity C#? A)

float h = Input.GetAxis("Horizontal");
if (h > 0.1f) {
    transform.Translate(h * speed * Time.deltaTime, 0, 0);
}

B)

float h = Input.GetAxis("Horizontal");
if (Mathf.Abs(h) > 0.1f) {
    transform.Translate(h * speed * Time.deltaTime, 0, 0);
}

C)

float h = Input.GetAxis("Horizontal");
if (h > 0.1f && h < -0.1f) {
    transform.Translate(h * speed * Time.deltaTime, 0, 0);
}

D)

float h = Input.GetAxis("Horizontal");
if (h != 0) {
    transform.Translate(h * speed * Time.deltaTime, 0, 0);
}

hard

A. Checks if h > 0.1f only (ignores negative direction)

B. Uses Mathf.Abs to check if absolute value of h is greater than 0.1

C. Checks if h is both greater than 0.1 and less than -0.1 (impossible)

D. Checks if h is not zero, allowing very small movements

Solution

1. Step 1: Understand input magnitude filtering

   We want to ignore small inputs less than 0.1 in magnitude, so absolute value check is needed.

2. Step 2: Analyze each condition

   Checks if h > 0.1f only (ignores negative direction) fails to move left since negative h won't exceed 0.1f. Uses Mathf.Abs to check if absolute value of h is greater than 0.1 uses Mathf.Abs(h) > 0.1f, which is concise and correct. Checks if h is both greater than 0.1 and less than -0.1 (impossible)'s AND condition is impossible. Checks if h is not zero, allowing very small movements allows any non-zero input, including tiny values.

3. Final Answer:

   Uses Mathf.Abs to check if absolute value of h is greater than 0.1 -> Option B

4. Quick Check:

   Use Mathf.Abs(h) > threshold for magnitude check [OK]

Hint: Use Mathf.Abs to check input magnitude for smooth control [OK]

Common Mistakes:

• Checking only positive direction (h > 0.1f), ignoring negatives
• Not using absolute value to check magnitude
• Allowing tiny inputs by only checking h != 0