Game Development: Physics, Graphics, and Game Loops

One Person, Six Days, $2.5 Billion

Markus "Notch" Persson built the first playable version of Minecraft in six days using Java. The game was eventually acquired by Microsoft for $2.5 billion. Stardew Valley was created by one person, Eric Barone, who spent four years teaching himself programming, art, music, and game design. Revenue: over $300 million. Flappy Bird was built by one person in three days. At its peak, it generated $50,000 per day in ad revenue. Meanwhile, Grand Theft Auto V cost $265 million and took 1,000+ developers five years to ship.

Game development is the only software field where a solo developer working in their bedroom and a AAA studio with billions in budget compete for the exact same player's attention -- and the solo developer sometimes wins. This is because games are judged by how they feel to play, not by how much money was spent making them. A technically crude game with brilliant mechanics (Undertale, Celeste, Vampire Survivors) can outsell a visually stunning game with mediocre gameplay.

That makes game development uniquely rewarding and uniquely brutal. It sits at the intersection of art, engineering, psychology, and physics. And it all starts with a single loop that runs 60 times per second.

The Game Loop: The Heartbeat of Every Game

Every video game ever made -- from Pong to Elden Ring -- runs the same fundamental structure. It is called the game loop, and it executes the same three steps in sequence, over and over, as fast as the hardware allows.

Step 1: Process Input. Read the controller, keyboard, mouse, or touchscreen. Which buttons are pressed? Where is the joystick pointing? Did the player tap the screen? This input data is stored for the next step to use.

Step 2: Update Game State. Using the input data, update everything in the game world. Move the player character based on joystick input. Apply gravity to objects in the air. Check if bullets hit enemies. Advance NPC behavior trees. Update particle effects. Tick down timers. Apply damage, check health, trigger death animations if health reaches zero. Every rule of the game is applied during this step.

Step 3: Render. Draw the current game state to the screen. Position every sprite, mesh, particle, and UI element. Apply lighting and shaders. Composite the final frame. Send it to the display.

Then repeat. At 60 frames per second, this entire cycle -- input, update, render -- must complete in 16.67 milliseconds. At 120fps (common on modern monitors and consoles), the budget drops to 8.33ms. If your update takes 20ms, the frame is late, and the player sees a stutter. Consistent frame pacing -- delivering every frame exactly on time -- is what makes a game feel "smooth" or "laggy."

Game Engines: Build Your Game, Not Your Engine

A game engine is a software framework that provides the core systems every game needs: rendering (drawing to the screen), physics (gravity, collisions), input handling, audio, asset management, and scripting. Building these systems from scratch for every new game is like building your own car engine every time you want to drive somewhere. It is educational, but it is not how you ship a game.

Three engines dominate modern game development, each with distinct strengths and philosophies.

The choice between engines is less dramatic than it appears online. Unity and Godot are both excellent for 2D games and indie projects. Unreal is the clear choice for AAA-quality 3D. The worst decision is spending months comparing engines instead of building your game. Pick one, learn it, make something. You can switch engines for your next project if needed -- the game design knowledge transfers completely.

Physics Simulation: Making Things Fall Convincingly

Every platformer needs gravity. Every racing game needs friction. Every shooter needs projectile trajectories. But game physics is not real physics. Real-world physics simulation at the precision required for engineering applications is far too computationally expensive to run at 60fps alongside rendering, AI, and everything else. Game physics is the art of approximations that feel right.

Consider gravity. In the real world, gravity accelerates an object at 9.8 m/s^2 continuously. In a platformer, true gravity feels slow and floaty. Mario does not obey Newtonian physics. Nintendo's designers tuned the gravity, jump height, air control, and coyote time (a brief window after walking off a ledge where you can still jump) until the movement felt perfect. The physics are "wrong" by any real-world standard, but they feel right to the player, and that is all that matters.

Collision Detection

At its simplest, collision detection answers one question: are two objects overlapping? This question gets asked for every pair of objects that could collide, every frame. In a game with 100 objects, that is potentially 4,950 pair checks per frame, 60 times per second. As object counts increase, naive collision detection becomes a performance bottleneck.

The most common approach is AABB (Axis-Aligned Bounding Box) collision. Every object is wrapped in a rectangle aligned to the screen axes. Checking whether two rectangles overlap requires only four comparisons: is A's left edge past B's right edge? Is A's right edge before B's left edge? Same for top and bottom. If all four checks fail (meaning there is overlap on all axes), the objects are colliding.

For complex shapes, games use a two-phase approach. The broad phase uses bounding boxes to quickly eliminate pairs that are obviously not colliding. The narrow phase performs more precise checks (circle-to-circle, polygon-to-polygon, or pixel-perfect) only on the pairs that the broad phase flagged. This combination handles thousands of objects efficiently.

Raycasting is another essential technique. A ray is an invisible line shot from a point in a direction. When it hits something, the game knows what that something is and how far away it is. Raycasting is used for gunshot hit detection (did the bullet's path intersect an enemy?), line-of-sight checks (can this NPC see the player?), ground detection (is the character standing on solid ground?), and mouse picking (what 3D object is the player clicking on?). First-person shooters use raycasting thousands of times per frame.

Graphics and Rendering: Turning Data Into Pixels

Rendering is the process of converting the game's mathematical representation (object positions, materials, light sources) into the colored pixels you see on screen. The approach differs dramatically between 2D and 3D games.

2D Rendering: Sprites and Tilemaps

In a 2D game, graphics are sprites -- flat images drawn on a coordinate plane. A character sprite is a series of images (frames) that create the illusion of animation when played in sequence, just like a flipbook. A tilemap is a grid where each cell references a small tile image, allowing designers to build large levels by arranging a relatively small set of tiles. This approach is incredibly efficient: instead of storing a unique image for every pixel of a large level, you store a few dozen tile images and a grid of indices. Stardew Valley, Celeste, and virtually every retro-style game use tilemaps.

3D Rendering: Meshes, Textures, and Shaders

In a 3D game, objects are made of meshes -- networks of triangles that approximate surfaces. A human character mesh might contain 10,000-100,000 triangles. Textures are images wrapped around meshes to give them surface detail (skin, fabric, metal). Shaders are small programs that run on the GPU and determine how each pixel of a surface should be colored based on material properties, light sources, camera angle, and environmental effects. A shader is what makes metal look like metal and skin look like skin, even using the same underlying mesh geometry.

The rendering pipeline in simplified form: determine which objects are visible to the camera (frustum culling), transform 3D coordinates to 2D screen coordinates (projection), determine which surfaces face the camera (backface culling), run vertex shaders to transform geometry, rasterize triangles into fragments, run fragment shaders to color each pixel, apply post-processing effects (bloom, motion blur, color grading), and output the final frame. This process involves millions of parallel calculations, which is why it runs on the GPU -- a processor designed specifically for massive parallelism. A modern GPU has thousands of cores running simultaneously, compared to a CPU's 8-24 cores.

Game Design vs. Game Development

These terms are often confused, but they describe fundamentally different disciplines.

Game design answers: what makes this game fun? It encompasses mechanics (the rules and systems of interaction), progression (how the player grows stronger or advances), difficulty curves (keeping challenge balanced between boring and frustrating), narrative (story, characters, world-building), and player psychology (what motivates players to keep playing, what makes a moment feel rewarding, what creates tension). Game design is closer to psychology and creative writing than to engineering.

Game development answers: how do we build this technically? It encompasses programming the game loop, implementing physics, building rendering systems, creating tools for designers, optimizing performance, fixing bugs, and shipping on target platforms. Game development is software engineering applied to interactive entertainment.

A technically perfect boring game still fails. A technically rough game with brilliant design (Minecraft's initial graphics were deliberately primitive) can become the best-selling game in history. Both disciplines are essential, and the best game developers understand both even if they specialize in one.

Indie Game Development: The Realistic Path

The indie path is the most accessible entry into game development. You do not need a studio, a publisher, or a large budget. You need a game engine, a manageable scope, and the discipline to finish.

Essential Indie Tools

Beyond the game engine, indie developers rely on specialized tools. Aseprite ($20) is the standard for pixel art creation and animation. Audacity (free) handles basic sound editing. LMMS or FL Studio for music composition. Tiled (free) is a powerful tilemap editor for level design. Krita (free) for digital painting and concept art. Blender (free) for 3D modeling and animation -- its capabilities rival commercial tools costing thousands. The entire indie game creation pipeline can be assembled for under $50 in software costs.

Answers to Questions People Actually Ask

Which programming language should I learn for game development? If you choose Unity: C#. If you choose Unreal: C++ (or start with Blueprints visual scripting). If you choose Godot: GDScript (easiest starting point) or C#. For a beginner, C# with Unity or GDScript with Godot are the most accessible paths. C++ is the language of AAA game development, but its learning curve is steep -- save it for when you have a specific reason to need it, like working with Unreal or needing maximum performance for a custom engine.

Can I make a game alone? Yes. Stardew Valley, Undertale, Cave Story, Papers Please, Axiom Verge, and Celeste (mostly) were made by one or two people. But solo development means doing everything: programming, art, music, sound, design, marketing, QA. Most solo developers either develop skills across disciplines (like Eric Barone learning pixel art for Stardew Valley) or use pre-made assets and focus on game design and programming. The key constraint is scope: one person can make a great small game or a mediocre large one.

Is game development a good career? The game industry is large ($184 billion in 2024) but has well-documented problems: crunch culture (60-80 hour weeks before deadlines), lower pay than equivalent non-game software roles (a senior game developer might earn $120K where a senior web developer earns $170K), and periodic mass layoffs. The indie path offers freedom but financial uncertainty -- most indie games never earn enough to cover development costs. The people who thrive in game development are those who genuinely love making games, not those who think it sounds fun based on playing games. Making games and playing games are entirely different experiences.

Do I need to understand math for game development? For 2D games: basic algebra and trigonometry (for angles, trajectories, and rotations). For 3D games: linear algebra (vectors and matrices for 3D transformations) and basic calculus concepts (for physics simulation and animation curves). The game engine handles the heaviest math, but understanding what it is doing helps you use it correctly and debug problems. You do not need a math degree. You need to understand what a dot product does (direction comparison), what a cross product does (perpendicular direction), and how to use sin/cos for circular motion. Game-specific math tutorials are more accessible than abstract math courses.