Rigidbody forces and velocity in Unity

Introduction

Rigidbody forces and velocity let you move objects in a game realistically. They help objects react to pushes, pulls, and speed changes like in real life.

When you want a ball to roll after being hit.

When making a character jump or fall naturally.

When simulating wind pushing leaves or objects.

When you want objects to bounce or slide on surfaces.

When controlling a car or vehicle movement with physics.

Syntax

Unity

Rigidbody rb;

// Add a force to the Rigidbody
rb.AddForce(Vector3 force, ForceMode mode = ForceMode.Force);

// Set the velocity directly
rb.velocity = new Vector3(x, y, z);

AddForce applies a push or pull over time, affected by mass.

Velocity sets the speed and direction instantly, overriding current movement.

Examples

This pushes the object upward with a default force mode.

Unity

rb.AddForce(new Vector3(0, 10, 0));

This applies an instant push to the right like a quick hit.

Unity

rb.AddForce(new Vector3(5, 0, 0), ForceMode.Impulse);

This sets the object's speed upward directly, ignoring forces.

Unity

rb.velocity = new Vector3(0, 5, 0);

Sample Program

This script moves an object with a Rigidbody. Press Space to jump up with a quick force. Press V to move right by setting velocity directly.

Unity

using UnityEngine;

public class MoveObject : MonoBehaviour
{
    private Rigidbody rb;

    void Start()
    {
        rb = GetComponent<Rigidbody>();
    }

    void Update()
    {
        if (Input.GetKeyDown(KeyCode.Space))
        {
            // Apply an instant upward force
            rb.AddForce(new Vector3(0, 300, 0), ForceMode.Impulse);
        }

        if (Input.GetKeyDown(KeyCode.V))
        {
            // Set velocity directly to move right
            rb.velocity = new Vector3(5, rb.velocity.y, 0);
        }
    }
}

Important Notes

Use AddForce for natural pushes that respect mass and drag.

Use velocity to instantly change speed, but it can ignore physics effects.

Always get the Rigidbody component before applying forces or velocity.

Summary

Rigidbody forces push or pull objects over time.

Velocity sets object speed instantly.

Use forces for realistic physics and velocity for direct control.

Practice

1. In Unity, what is the main difference between applying a force to a Rigidbody and setting its velocity directly?

easy

A. Applying a force stops the Rigidbody immediately, setting velocity makes it float.

B. Applying a force changes the Rigidbody's color, setting velocity changes its size.

C. Applying a force disables gravity, setting velocity enables gravity.

D. Applying a force changes velocity gradually, setting velocity changes it instantly.

Solution

1. Step 1: Understand force effect on Rigidbody

   Applying a force adds acceleration, so velocity changes smoothly over time.

2. Step 2: Understand velocity setting

   Setting velocity directly changes speed and direction immediately without gradual acceleration.

3. Final Answer:

   Applying a force changes velocity gradually, setting velocity changes it instantly. -> Option D

4. Quick Check:

   Force = gradual change, velocity = instant change [OK]

Hint: Force pushes smoothly; velocity sets speed instantly [OK]

Common Mistakes:

• Thinking force stops the object immediately
• Confusing force with color or size changes
• Believing velocity affects gravity

2. Which of the following is the correct way to add an upward force to a Rigidbody named rb in Unity?

easy

A. rb.AddForce(Vector3.up * 10);

B. rb.AddForce(10, Vector3.up);

C. rb.AddForce(10);

D. rb.AddForceUp(10);

Solution

1. Step 1: Check AddForce method signature

   Unity's Rigidbody.AddForce expects a Vector3 representing force direction and magnitude.

2. Step 2: Verify correct usage

   Using Vector3.up * 10 applies force upwards with magnitude 10, matching the method signature.

3. Final Answer:

   rb.AddForce(Vector3.up * 10); -> Option A

4. Quick Check:

   AddForce(Vector3) is correct syntax [OK]

Hint: AddForce needs Vector3 direction and magnitude [OK]

Common Mistakes:

• Passing separate arguments instead of a Vector3
• Using non-existent methods like AddForceUp
• Passing only a number without direction

3. Consider this Unity C# code snippet:

Rigidbody rb = GetComponent<Rigidbody>();
rb.velocity = new Vector3(0, 5, 0);
rb.AddForce(new Vector3(0, 10, 0), ForceMode.Acceleration);

What will be the Rigidbody's velocity immediately after these lines run?

medium

A. Velocity will be (0, 5, 0) and then increase gradually.

B. Velocity will be (0, 10, 0) instantly.

C. Velocity will be (0, 15, 0) instantly.

D. Velocity will be (0, 0, 0) because forces cancel velocity.

Solution

1. Step 1: Analyze velocity assignment

   Setting rb.velocity to (0,5,0) sets speed instantly upward at 5 units per second.

2. Step 2: Analyze AddForce with Acceleration mode

   AddForce with ForceMode.Acceleration adds acceleration, so velocity increases gradually over time, not instantly.

3. Final Answer:

   Velocity will be (0, 5, 0) and then increase gradually. -> Option A

4. Quick Check:

   Velocity set instantly; force adds gradual acceleration [OK]

Hint: Velocity sets speed instantly; force adds gradual acceleration [OK]

Common Mistakes:

• Assuming AddForce instantly changes velocity
• Confusing ForceMode.Acceleration with ForceMode.VelocityChange
• Thinking forces cancel velocity

4. What is wrong with this Unity C# code to move a Rigidbody upward?

Rigidbody rb = GetComponent<Rigidbody>();
rb.velocity += Vector3.up * 5;

medium

A. You cannot use '+=' operator with velocity; it causes errors.

B. This code instantly adds 5 units upward speed every frame, causing acceleration buildup.

C. Vector3.up is not a valid direction for velocity.

D. Rigidbody velocity cannot be changed directly.

Solution

1. Step 1: Understand velocity += Vector3.up * 5

   This adds 5 units upward speed to current velocity instantly each time it runs.

2. Step 2: Identify problem in repeated calls

   If called every frame, velocity keeps increasing, causing unnatural acceleration buildup.

3. Final Answer:

   This code instantly adds 5 units upward speed every frame, causing acceleration buildup. -> Option B

4. Quick Check:

   Adding velocity each frame causes speed to grow too fast [OK]

Hint: Adding velocity each frame causes speed to grow too fast [OK]

Common Mistakes:

• Thinking '+=' on velocity causes syntax errors
• Believing Vector3.up is invalid
• Assuming velocity cannot be changed directly

5. You want to make a Rigidbody jump smoothly using physics forces, but also limit its maximum upward speed to 10 units per second. Which approach correctly combines forces and velocity control?

hard

A. Use rb.AddForce(Vector3.up * jumpForce) only and ignore velocity limits.

B. Set rb.velocity = Vector3.up * 10 directly every frame without forces.

C. Use rb.AddForce(Vector3.up * jumpForce) and clamp rb.velocity.y to max 10 after applying force.

D. Set rb.velocity = Vector3.up * jumpForce once and never apply forces.

Solution

1. Step 1: Use AddForce for smooth jumping

   Applying AddForce lets physics handle smooth acceleration for jump.

2. Step 2: Clamp velocity to limit max speed

   After applying force, clamp rb.velocity.y to 10 to prevent exceeding max upward speed.

3. Final Answer:

   Use rb.AddForce(Vector3.up * jumpForce) and clamp rb.velocity.y to max 10 after applying force. -> Option C

4. Quick Check:

   Force for smooth jump + clamp velocity to limit speed [OK]

Hint: Combine AddForce with velocity clamp to control max speed [OK]

Common Mistakes:

• Setting velocity directly every frame causing unnatural jumps
• Ignoring velocity limits causing excessive speed
• Using only velocity without forces for smooth physics