FixedUpdate vs Update in Unity - Quick Revision & Key Differences

Recall & Review

beginner

What is the main difference between Update() and FixedUpdate() in Unity?

Update() runs once per frame and is used for regular frame-based updates like input handling. FixedUpdate() runs at fixed time intervals and is used for physics calculations.

beginner

Why should physics-related code be placed inside FixedUpdate()?

Because physics calculations in Unity run at fixed time steps, placing physics code in FixedUpdate() ensures consistent and stable physics behavior regardless of frame rate.

intermediate

What happens if you put physics code inside Update() instead of FixedUpdate()?

Physics code in Update() can cause inconsistent behavior because Update() runs at variable frame rates, leading to unstable or jittery physics.

intermediate

How often does FixedUpdate() run compared to Update()?

FixedUpdate() runs at a fixed interval (default 0.02 seconds), which can be multiple times per frame or less often, depending on frame rate. Update() runs once per frame.

beginner

Can you use Update() and FixedUpdate() together in the same script? Why?

Yes, you can use both. Use Update() for input and visual updates, and FixedUpdate() for physics to keep things smooth and stable.

Which Unity method is best for handling user input every frame?

A Update()

B FixedUpdate()

C LateUpdate()

D OnGUI()

Update() runs every frame and is ideal for input handling.

How often does FixedUpdate() run by default?

A Once per frame

B At fixed intervals (default 0.02 seconds)

C Only when physics changes

D Randomly

FixedUpdate() runs at fixed time steps, usually every 0.02 seconds.

What is the risk of putting physics code inside Update()?

A Physics will run too fast

B No risk, it works fine

C Physics will stop working

D Physics calculations may become unstable

Because Update() runs at variable frame rates, physics can behave inconsistently.

Which method should you use to move a Rigidbody smoothly in Unity?

A Start()

B Update()

C FixedUpdate()

D Awake()

Use FixedUpdate() for Rigidbody movement to sync with physics updates.

Can FixedUpdate() be called multiple times per frame?

A Yes

B No

C Only on slow devices

D Only in editor mode

FixedUpdate() can run multiple times per frame if the frame rate is low.

Explain when and why you would use FixedUpdate() instead of Update() in Unity.

Think about physics and timing.

Describe the consequences of handling input inside FixedUpdate() instead of Update().

Consider how often input is checked.

Practice

1. What is the main difference between Update and FixedUpdate in Unity?

easy

A. Both run at the same time but handle different components.

B. Update runs every frame; FixedUpdate runs at fixed time intervals.

C. FixedUpdate runs every frame; Update runs at fixed time intervals.

D. Update is only for physics; FixedUpdate is for animations.

Solution

1. Step 1: Understand the timing of Update

   Update is called once per frame, so its timing depends on the frame rate.

2. Step 2: Understand the timing of FixedUpdate

   FixedUpdate is called at fixed intervals, independent of frame rate, ideal for physics calculations.

3. Final Answer:

   Update runs every frame; FixedUpdate runs at fixed time intervals. -> Option B

4. Quick Check:

   Update = frame-based, FixedUpdate = fixed interval [OK]

Hint: Remember: Update = frame, FixedUpdate = fixed time [OK]

Common Mistakes:

• Confusing which method runs at fixed intervals
• Thinking FixedUpdate depends on frame rate
• Assuming Update is for physics only

2. Which of the following is the correct syntax to declare the FixedUpdate method in a Unity C# script?

easy

A. void FixedUpdate() { /* code here */ }

B. void fixedUpdate() { /* code here */ }

C. void Fixedupdate() { /* code here */ }

D. void Fixed_Update() { /* code here */ }

Solution

1. Step 1: Check method name capitalization

   Unity requires exact method names with correct capitalization; FixedUpdate starts with capital F and U.

2. Step 2: Verify method signature

   The method must be declared as void FixedUpdate() with no parameters.

3. Final Answer:

   void FixedUpdate() { /* code here */ } -> Option A

4. Quick Check:

   Correct capitalization and signature = void FixedUpdate() { /* code here */ } [OK]

Hint: Method names are case-sensitive; use exact spelling [OK]

Common Mistakes:

• Using wrong capitalization like fixedUpdate
• Adding underscores in method names
• Adding parameters to FixedUpdate

3. Consider this Unity C# script snippet:

void Update() {
    Debug.Log("Update called");
}

void FixedUpdate() {
    Debug.Log("FixedUpdate called");
}

If the game runs at 60 frames per second and the fixed timestep is 0.02 seconds, which output will appear more frequently in the console?

medium

A. Both will appear the same number of times.

B. "FixedUpdate called" will appear more frequently.

C. "Update called" will appear more frequently.

D. Neither will appear because Debug.Log is disabled.

Solution

1. Step 1: Calculate Update calls per second

   At 60 FPS, Update runs 60 times per second.

2. Step 2: Calculate FixedUpdate calls per second

   Fixed timestep is 0.02 seconds, so FixedUpdate runs 1/0.02 = 50 times per second.

3. Final Answer:

   "Update called" will appear more frequently. -> Option C

4. Quick Check:

   60 (Update) > 50 (FixedUpdate) calls per second [OK]

Hint: Update frequency = FPS; FixedUpdate frequency = 1/fixedDeltaTime [OK]

Common Mistakes:

• Assuming FixedUpdate runs more often than Update
• Ignoring fixed timestep value
• Confusing frame rate with fixed update rate

4. You wrote this code to move a Rigidbody smoothly:

void Update() {
    rb.AddForce(Vector3.forward * forceAmount);
}

But the movement is jittery. What is the best fix?

medium

A. Move the AddForce call into FixedUpdate.

B. Increase forceAmount in Update.

C. Call rb.MovePosition inside Update instead.

D. Disable physics in Rigidbody.

Solution

1. Step 1: Identify physics update timing

   Physics updates happen in fixed time steps, so applying forces in Update causes inconsistent timing and jitter.

2. Step 2: Move physics code to FixedUpdate

   Calling AddForce inside FixedUpdate matches physics timing and smooths movement.

3. Final Answer:

   Move the AddForce call into FixedUpdate. -> Option A

4. Quick Check:

   Physics code belongs in FixedUpdate [OK]

Hint: Put physics code in FixedUpdate to avoid jitter [OK]

Common Mistakes:

• Applying physics forces in Update
• Trying to fix jitter by increasing force
• Disabling physics instead of fixing timing

5. You want to create a smooth player movement that responds to input and uses physics. Which is the best way to organize your code?

hard

A. Apply forces in Update, ignore input.

B. Read input and apply forces both in Update.

C. Read input and apply forces both in FixedUpdate.

D. Read input in Update, apply movement forces in FixedUpdate.

Solution

1. Step 1: Understand input timing

   Input should be read every frame in Update to avoid missing user actions.

2. Step 2: Understand physics timing

   Physics forces should be applied in FixedUpdate for consistent physics simulation.

3. Step 3: Combine input and physics correctly

   Store input values in Update, then use them in FixedUpdate to apply forces smoothly.

4. Final Answer:

   Read input in Update, apply movement forces in FixedUpdate. -> Option D

5. Quick Check:

   Input in Update + physics in FixedUpdate = smooth movement [OK]

Hint: Input in Update, physics in FixedUpdate for smooth control [OK]

Common Mistakes:

• Reading input in FixedUpdate causing missed inputs
• Applying physics in Update causing jitter
• Ignoring input or physics timing differences