Game Physics Interview Questions and Challenges

# CHAPTER 19

Game Physics Interview Questions and Challenges #

1. Introduction #

Whether you are applying for a Gameplay Engineering role at a AAA studio or taking a technical test for a physics-based indie game, you must be able to prove your understanding of simulated mathematics. Interviewers will not ask you to recite API documentation; they will ask you to solve spatial bugs, optimize framerates, and explain the mathematical difference between vectors. In this chapter, we will pressure-test your knowledge with Game Physics Interview Questions and Challenges. We will cover core vector math, troubleshoot severe physics glitches, and present architectural scenarios.

2. Learning Objectives #

By the end of this chapter, you will be able to:

• Articulate the mathematical relationship between Vectors, Velocity, and Delta Time.

• Troubleshoot common physics bugs (Tunneling, Jitter, Desync).

• Architect optimal collision solutions for complex scenarios.

• Demonstrate a deep understanding of the FixedUpdate loop.

---

3. Section 1: Core Physics Math #

Q1: Explain the concept of Vector Normalization. Provide a concrete gameplay scenario where failing to normalize a Vector results in a severe bug. *Answer:* Normalization scales a Vector's magnitude (length) to exactly 1.0 while maintaining its direction. In a top-down game, if the player holds 'Up' (1, 0) and 'Right' (0, 1), the resulting diagonal vector is (1, 1), which has a magnitude of ~1.41. If the programmer multiplies this non-normalized vector by speed, the player will move 41% faster diagonally. Normalizing the vector caps the length to 1, ensuring consistent speed in all directions.

Q2: What is the mathematical difference between Vector3.Distance and Vector3.sqrMagnitude? Which should be used for proximity checks in the Update loop, and why? *Answer:* Vector3.Distance uses the Pythagorean theorem, which requires calculating a Square Root—a notoriously slow operation for a CPU. sqrMagnitude simply calculates the squared distance (A² + B²) without performing the final square root. For checking if an enemy is within 5 meters, you should use sqrMagnitude and check if it is less than 25 (5 squared). This avoids the heavy math and is vastly superior for optimization.

Q3: Describe the relationship between Position, Velocity, and Acceleration in a physics loop. *Answer:* Acceleration is the rate of change of Velocity over time. Velocity is the rate of change of Position over time. In a loop, you multiply Acceleration by DeltaTime and add it to Velocity. Then, you multiply Velocity by DeltaTime and add it to Position.

---

4. Section 2: Engine Architecture & Debugging #

Q4: A junior developer places their Rigidbody.AddForce calls inside the standard Update() loop. The character's jump height is drastically different depending on whether the game runs at 30 FPS or 144 FPS. Explain why this happens and how to fix it. *Answer:* Update() is tied to the rendering framerate, which fluctuates. If a jump force is applied across multiple frames in Update, a 144 FPS PC will apply that force more times per second than a 30 FPS console, launching the player higher. All physics calculations (mass, force, collisions) must occur in the FixedUpdate loop, which runs on a strict, unyielding timer (e.g., exactly 50 times a second), ensuring deterministic math across all hardware.

Q5: What is the "Bullet Through Paper" (Tunneling) problem? Detail two distinct ways to solve it. *Answer:* Tunneling occurs when an object moves so fast (e.g., a sniper bullet) that it passes completely through a thin wall between Frame 1 and Frame 2 without the engine detecting an overlap. *Solution 1:* Change the Rigidbody's collision detection mode to Continuous Dynamic, which forces the engine to sweep the space between frames mathematically. *Solution 2:* Abandon the physical Rigidbody entirely and use a Hitscan (Raycast) approach to instantly calculate the bullet's trajectory line.

Q6: A tower of 50 physics crates is slowly vibrating and jittering, eventually collapsing on its own. What is causing this, and how can it be optimized? *Answer:* This is caused by floating-point precision errors. The engine is constantly trying to resolve the micro-penetrations of 50 heavy objects crushing each other. To fix it, you adjust the engine's "Sleep Threshold." If an object's velocity drops below a tiny threshold, the engine forces the Rigidbody to "Sleep," completely halting the math calculations and freezing the crates in place until pushed.

---

5. Section 3: Architecture Challenges #

Challenge 1: The Multiplayer Desync *Scenario:* You are building an online game where players throw bouncy grenades. You sync the grenades by having each client instantiate the grenade and simulate the bounces locally. After 3 bounces, the grenade is in completely different rooms for different players. How do you re-architect this? *Solution:* You must implement an Authoritative Server. Clients should not simulate physics. The Server instantiates the grenade, simulates the Rigidbody bounces, and broadcasts the absolute X/Y/Z position over the network 20 times a second. The Clients set their grenades to isKinematic and smoothly Lerp (interpolate) the visual grenade to match the Server's coordinates.

Challenge 2: The Sticking Wall *Scenario:* A player jumps toward a vertical wall. They hold the "Forward" key, pressing their character against the wall. The character gets stuck mid-air and refuses to fall until the player lets go of the key. What is happening? *Solution:* The physics engine is calculating standard friction between the player's collider and the wall's collider. The forward force generates enough friction to counteract gravity. To fix this, create a "Zero Friction" Physics Material and apply it to the player's Collider, allowing them to slide perfectly down the wall.

Challenge 3: The Optimized Explosion *Scenario:* A massive bomb goes off in a city full of 10,000 physical debris objects. You need to apply outward force to everything nearby. Using Physics.OverlapSphere followed by GetComponent<Rigidbody>() causes a massive 200ms lag spike. Optimize this. *Solution:* First, use a Collision Layer Matrix so the OverlapSphere only searches the specific "Debris" layer, ignoring static buildings. Second, use Physics.OverlapSphereNonAlloc to prevent Garbage Collection spikes. Third, if there are thousands of objects, distribute the AddExplosionForce calculations over multiple frames using a Coroutine, rather than calculating 10,000 forces in a single frame.

6. Summary #

In Chapter 19, we proved our expertise. We moved beyond simple tutorials and tackled the real-world bugs, performance spikes, and architectural flaws that professional gameplay engineers face daily. You can now articulate the necessity of Vector Normalization, the strict rules of the FixedUpdate loop, and the solutions to high-speed Tunneling and multiplayer Desyncs.

7. Next Chapter Recommendation #

You have the knowledge. It is time to prove it. Proceed to the final challenge: Chapter 20: Build a Complete Physics-Based Game System.