Obstacle avoidance in Unity - Performance & Optimization

Performance: Obstacle avoidance

MEDIUM IMPACT

This affects the frame rate and responsiveness of the game by how often and how complex the obstacle detection and avoidance calculations are.

Detecting and avoiding obstacles for a moving character in a game scene

Unity

void Update() {
  if (Time.frameCount % 5 == 0) {
    RaycastHit hit;
    if (Physics.Raycast(transform.position, transform.forward, out hit, 10f)) {
      if (hit.collider.CompareTag("Obstacle")) {
        transform.Rotate(0, 90, 0);
      }
    }
  }
  transform.Translate(Vector3.forward * Time.deltaTime * speed);
}

Limits raycast checks to every 5 frames, reducing physics calls and smoothing CPU usage.

📈 Performance Gainreduces physics raycasts by 80%, lowering CPU load and improving frame rate stability

Detecting and avoiding obstacles for a moving character in a game scene

Unity

void Update() {
  RaycastHit hit;
  if (Physics.Raycast(transform.position, transform.forward, out hit, 10f)) {
    if (hit.collider.CompareTag("Obstacle")) {
      transform.Rotate(0, 90, 0);
    }
  }
  transform.Translate(Vector3.forward * Time.deltaTime * speed);
}

This runs a raycast every frame without any optimization, causing many physics checks and potential frame drops.

📉 Performance Costtriggers 1 physics raycast per frame, causing CPU spikes especially with many moving objects

Performance Comparison

Pattern	Physics Calls	CPU Usage	Frame Drops	Verdict
Raycast every frame	High (1 per frame)	High	Frequent	[X] Bad
Raycast every 5 frames	Low (1 per 5 frames)	Low	Rare	[OK] Good

Rendering Pipeline

Obstacle avoidance calculations run on the CPU and affect the game loop update cycle. Frequent physics raycasts increase CPU usage and can delay frame rendering.

→Game Loop Update

→Physics Calculation

⚠️ BottleneckPhysics Calculation stage due to frequent raycasts

Optimization Tips

1Avoid running physics raycasts every frame if possible.

2Use simpler colliders and limit raycast targets to reduce cost.

3Batch or space out obstacle detection checks to smooth CPU usage.

Performance Quiz - 3 Questions

What is the main performance cost of running obstacle avoidance with raycasts every frame?

A High CPU usage due to frequent physics raycasts

B Increased GPU load from rendering

C More memory usage from storing raycast results

D Longer loading times at game start

DevTools: Unity Profiler

How to check: Open Unity Profiler, run the game, and look at CPU Usage and Physics sections to see how many raycasts are called per frame.

What to look for: High spikes in Physics raycast calls indicate inefficient obstacle avoidance; smoother CPU usage means better performance.

Practice

1. What is the main purpose of obstacle avoidance in Unity game programming?

easy

A. To help objects move without hitting obstacles

B. To make objects jump higher

C. To change the color of objects

D. To increase the speed of objects

Solution

1. Step 1: Understand obstacle avoidance concept

   Obstacle avoidance is used to prevent objects from colliding with obstacles in their path.

2. Step 2: Identify the correct purpose

   The main goal is to help objects move smoothly without hitting anything.

3. Final Answer:

   To help objects move without hitting obstacles -> Option A

4. Quick Check:

   Obstacle avoidance = prevent collisions [OK]

Hint: Obstacle avoidance means avoiding collisions [OK]

Common Mistakes:

• Confusing obstacle avoidance with speed control
• Thinking it changes object appearance
• Assuming it makes objects jump

2. Which Unity function is commonly used to detect obstacles ahead for avoidance?

easy

A. Update

B. Instantiate

C. Raycast

D. Destroy

Solution

1. Step 1: Recall Unity functions for detection

   Raycast is used to send an invisible line to detect objects in front.

2. Step 2: Match function to obstacle detection

   Raycast detects obstacles ahead, while Instantiate creates objects, Update runs every frame, and Destroy removes objects.

3. Final Answer:

   Raycast -> Option C

4. Quick Check:

   Obstacle detection = Raycast [OK]

Hint: Raycast checks ahead for obstacles [OK]

Common Mistakes:

• Choosing Update which runs every frame but doesn't detect
• Confusing Instantiate with detection
• Selecting Destroy which deletes objects

3. What will be the output if the following Unity C# code runs and an obstacle is detected by the raycast?

void Update() {
    if (Physics.Raycast(transform.position, transform.forward, out var hit, 5f)) {
        transform.Rotate(0, 90, 0);
        Debug.Log("Obstacle detected, turning right.");
    } else {
        transform.Translate(Vector3.forward * Time.deltaTime * 3);
    }
}

medium

A. The object moves forward continuously without turning

B. The object moves backward

C. The object stops moving and no message is logged

D. The object turns right and logs "Obstacle detected, turning right."

Solution

1. Step 1: Analyze raycast detection and response

   If the raycast hits an obstacle within 5 units, the object rotates 90 degrees on Y axis and logs a message.

2. Step 2: Understand else behavior

   If no obstacle is detected, the object moves forward at speed 3 units per second.

3. Final Answer:

   The object turns right and logs "Obstacle detected, turning right." -> Option D

4. Quick Check:

   Obstacle detected = turn right + log message [OK]

Hint: If raycast hits, rotate and log; else move forward [OK]

Common Mistakes:

• Ignoring the rotation when obstacle detected
• Thinking object stops instead of turning
• Assuming object moves backward

4. Identify the error in this obstacle avoidance code snippet:

void Update() {
    if (Physics.Raycast(transform.position, transform.forward, 5f)) {
        Debug.Log(hit.distance);
        transform.Rotate(0, 90, 0);
    }
}

medium

A. The Rotate method parameters are incorrect

B. The Raycast method is missing the 'out RaycastHit' parameter

C. The if condition should use '==' instead of parentheses

D. The Update method should be named FixedUpdate

Solution

1. Step 1: Check Raycast method signature

   Physics.Raycast requires an 'out RaycastHit' parameter to store hit info when using this overload.

2. Step 2: Verify Rotate and method names

   Rotate parameters are correct for rotation; Update is valid for frame updates.

3. Final Answer:

   The Raycast method is missing the 'out RaycastHit' parameter -> Option B

4. Quick Check:

   Raycast needs 'out RaycastHit' [OK]

Hint: Raycast needs 'out RaycastHit' to detect hits [OK]

Common Mistakes:

• Omitting the out parameter in Raycast
• Confusing Rotate parameters
• Thinking Update must be FixedUpdate

5. You want your Unity object to avoid obstacles smoothly by turning gradually instead of instantly. Which approach should you use in your obstacle avoidance script?

hard

A. Use Quaternion.Slerp to rotate smoothly when obstacle detected

B. Use transform.Rotate(0, 90, 0) instantly on detection

C. Stop the object completely when obstacle is detected

D. Ignore obstacles and keep moving forward

Solution

1. Step 1: Understand smooth rotation methods

   Quaternion.Slerp smoothly interpolates rotation over time, creating gradual turns.

2. Step 2: Compare with instant rotation

   transform.Rotate(0, 90, 0) turns instantly, which is not smooth.

3. Final Answer:

   Use Quaternion.Slerp to rotate smoothly when obstacle detected -> Option A

4. Quick Check:

   Smooth turn = Quaternion.Slerp [OK]

Hint: Use Quaternion.Slerp for smooth turning [OK]

Common Mistakes:

• Using instant rotation causing jerky movement
• Stopping object instead of turning
• Ignoring obstacles completely