Input axis for smooth movement in Unity - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to get horizontal input for smooth movement.

Unity

float horizontal = Input.[1]("Horizontal");

Drag options to blanks, or click blank then click option'

AGetButtonDown

BGetAxis

CGetKeyDown

DGetButtonUp

Attempts:

3 left

💡 Hint

Common Mistakes

Using GetButtonDown instead of GetAxis causes no smooth movement.

Using GetKeyDown returns true only on key press, not continuous input.

Input.GetAxis("Horizontal") returns a smooth value between -1 and 1 based on player input.

2fill in blank

medium

Complete the code to move the player smoothly on the x-axis.

Unity

transform.Translate(horizontal * speed * Time.[1]);

Drag options to blanks, or click blank then click option'

AdeltaTime

BtimeScale

CfixedDeltaTime

DunscaledDeltaTime

Attempts:

3 left

💡 Hint

Common Mistakes

Using fixedDeltaTime in Update can cause inconsistent movement.

Using timeScale or unscaledDeltaTime is not suitable for normal movement timing.

Time.deltaTime ensures movement is smooth and frame rate independent.

3fill in blank

hard

Fix the error in the code to read vertical input smoothly.

Unity

float vertical = Input.[1]("Vertical");

Drag options to blanks, or click blank then click option'

AGetButton

BGetAxisRaw

CGetAxis

DGetKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using GetAxisRaw causes jerky movement instead of smooth.

Using GetButton or GetKey returns boolean, not float values.

Input.GetAxis returns smooth input values, while GetAxisRaw returns immediate -1, 0, or 1.

4fill in blank

hard

Fill both blanks to create a dictionary of axis values for movement.

Unity

var movement = new Dictionary<string, float> { {"horizontal", Input.[1]("Horizontal")}, {"vertical", Input.[2]("Vertical")} };

Drag options to blanks, or click blank then click option'

AGetAxis

BGetButtonDown

CGetAxisRaw

DGetKeyDown

Attempts:

3 left

💡 Hint

Common Mistakes

Using GetButtonDown or GetKeyDown returns booleans, not floats.

Using the same method for both axes may not fit all movement needs.

Use GetAxis for horizontal to get smooth input, and GetAxisRaw for vertical to get immediate input.

5fill in blank

hard

Fill all three blanks to create a movement vector and apply it smoothly.

Unity

Vector3 move = new Vector3(Input.[1]("Horizontal"), 0, Input.[2]("Vertical"));
transform.Translate(move * speed * Time.[3]);

Drag options to blanks, or click blank then click option'

AGetAxis

BGetAxisRaw

CdeltaTime

DGetButton

Attempts:

3 left

💡 Hint

Common Mistakes

Using GetButton returns bool, not float values.

Not using deltaTime causes movement to depend on frame rate.

Use GetAxis for smooth horizontal input, GetAxisRaw for vertical raw input, and deltaTime for smooth frame-independent 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