Input axis for smooth movement in Unity

Introduction

Input axis lets your game character move smoothly instead of jumping in steps. It reads how much you press a key or move a joystick.

When you want a character to walk or run smoothly in a game.

When using a joystick or gamepad for gradual movement.

When you want to detect how hard a player is pressing a control.

When you want to move objects in a game with fluid motion.

When you want to create natural-feeling controls for a player.

Syntax

Unity

float horizontal = Input.GetAxis("Horizontal");
float vertical = Input.GetAxis("Vertical");

"Horizontal" and "Vertical" are default input axis names in Unity for left/right and up/down controls.

Input.GetAxis returns a float between -1 and 1, showing how much the control is pressed.

Examples

Reads horizontal input for left/right movement smoothly.

Unity

float moveX = Input.GetAxis("Horizontal");

Reads vertical input for up/down movement smoothly.

Unity

float moveY = Input.GetAxis("Vertical");

Reads horizontal input instantly without smoothing (jumps between -1, 0, 1).

Unity

float moveX = Input.GetAxisRaw("Horizontal");

Sample Program

This script moves a game object smoothly based on keyboard or joystick input. The character moves left/right and forward/back smoothly using Input.GetAxis.

Unity

using UnityEngine;

public class SmoothMovement : MonoBehaviour
{
    public float speed = 5f;

    void Update()
    {
        float moveX = Input.GetAxis("Horizontal");
        float moveZ = Input.GetAxis("Vertical");

        Vector3 move = new Vector3(moveX, 0, moveZ) * speed * Time.deltaTime;
        transform.Translate(move, Space.World);
    }
}

Important Notes

Input.GetAxis smooths input over time, so movement feels natural.

Use Input.GetAxisRaw if you want instant input without smoothing.

Always multiply by Time.deltaTime to keep movement smooth and frame-rate independent.

Summary

Input axis reads how much a control is pressed, giving smooth values between -1 and 1.

Use Input.GetAxis for smooth gradual movement in games.

Combine axis input with speed and Time.deltaTime for smooth character movement.

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