Game engine architecture overview in Unity - Step-by-Step Execution

Concept Flow - Game engine architecture overview

Start Game Engine

↓

Initialize Core Systems

↓

Load Assets & Resources

↓

Game Loop Start

↓

Process Input

→Update Game Logic

↓

Check Exit Condition

↓

Repeat Game Loop

↓

Shutdown & Cleanup

This flow shows how a game engine starts, runs its main loop processing input, updating logic, rendering frames, and then shuts down.

Execution Sample

Unity

void Update() {
    ProcessInput();
    UpdateGameLogic();
    RenderFrame();
}

This code runs every frame to handle input, update game state, and draw the scene.

Execution Table

Frame	ProcessInput	UpdateGameLogic	RenderFrame	Exit Condition	Action
1	Read keyboard/mouse	Move player, check collisions	Draw scene to screen	False	Continue loop
2	Read keyboard/mouse	Update NPCs, physics	Draw updated scene	False	Continue loop
3	Read keyboard/mouse	Check win/lose state	Draw final frame	True	Exit loop

💡 Exit condition true at frame 3, game loop ends

Variable Tracker

Variable	Start	After Frame 1	After Frame 2	After Frame 3
PlayerPosition	(0,0)	(1,0)	(2,0)	(2,0)
GameRunning	True	True	True	False
FrameCount	0	1	2	3

Key Moments - 2 Insights

Why does the game loop keep running even though we process input and update logic every frame?

Because the exit condition is checked after processing input, updating logic, and rendering. The loop continues until the exit condition becomes true, as shown in the execution_table rows 1 and 2.

What happens if the exit condition becomes true during the game loop?

The loop stops after completing the current frame's processing, as seen in frame 3 of the execution_table where the exit condition is true and the action is to exit the loop.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of GameRunning after frame 2?

A Undefined

B True

C False

D Null

💡 Hint

Check variable_tracker row for GameRunning after Frame 2

At which frame does the exit condition become true according to the execution_table?

A Frame 1

B Frame 2

C Frame 3

D Never

💡 Hint

Look at the Exit Condition column in execution_table

If the RenderFrame step was skipped, what would likely happen in the game loop?

A The game would not display changes on screen

B The game would not update logic

C The input would not be processed

D The exit condition would never be checked

💡 Hint

RenderFrame draws the scene; skipping it means no visual update

Concept Snapshot

Game engine runs a loop every frame:
- Process input from player
- Update game logic (movement, physics, AI)
- Render the frame to display
Loop continues until exit condition is true
Core systems initialize before loop and cleanup after

Full Transcript

A game engine starts by initializing core systems and loading assets. Then it enters the main game loop. Each frame, it processes player input, updates the game logic like moving characters and checking collisions, and renders the frame to the screen. After rendering, it checks if the game should exit. If not, it repeats the loop. When the exit condition is true, the loop ends and the engine shuts down. Variables like player position and frame count update each frame. This cycle keeps the game running smoothly and responding to player actions.

Practice

1. Which core system in a game engine is responsible for drawing graphics on the screen?

easy

A. Rendering system

B. Physics system

C. Input system

D. Audio system

Solution

1. Step 1: Understand core systems roles

   The rendering system handles all visual output, drawing images and shapes on the screen.

2. Step 2: Match system to function

   Since drawing graphics is about visuals, the rendering system is the correct match.

3. Final Answer:

   Rendering system -> Option A

4. Quick Check:

   Rendering = Drawing graphics [OK]

Hint: Rendering means drawing visuals on screen [OK]

Common Mistakes:

• Confusing physics with rendering
• Thinking input handles graphics
• Mixing audio with visuals

2. Which of the following is the correct way to start a Unity C# script class?

easy

A. public class PlayerController MonoBehaviour { }

B. class PlayerController { }

C. public class PlayerController : MonoBehaviour { }

D. public PlayerController : MonoBehaviour { }

Solution

1. Step 1: Recall Unity script class syntax

   Unity scripts must declare a public class that inherits from MonoBehaviour using a colon.

2. Step 2: Check each option for correct syntax

   public class PlayerController : MonoBehaviour { } correctly uses 'public class ClassName : MonoBehaviour { }'. Others miss 'public', colon, or have wrong order.

3. Final Answer:

   public class PlayerController : MonoBehaviour { } -> Option C

4. Quick Check:

   Class declaration with inheritance uses ':' [OK]

Hint: Class inherits MonoBehaviour with ':' and is public [OK]

Common Mistakes:

• Omitting 'public' keyword
• Missing colon ':' before MonoBehaviour
• Wrong order of keywords

3. What will be the output in Unity Console when this script runs?

using UnityEngine;

public class TestScript : MonoBehaviour {
    void Start() {
        Debug.Log("Hello World");
    }
}

medium

A. Hello World

B. Start

C. TestScript

D. No output

Solution

1. Step 1: Understand Debug.Log in Start()

   Debug.Log prints the message to the Unity Console when the Start method runs at game start.

2. Step 2: Identify printed message

   The message inside Debug.Log is "Hello World", so this will appear in the console.

3. Final Answer:

   Hello World -> Option A

4. Quick Check:

   Debug.Log prints "Hello World" [OK]

Hint: Debug.Log prints message in Start() method [OK]

Common Mistakes:

• Thinking method name prints
• Expecting class name output
• Assuming no output without Update()

4. Identify the error in this Unity C# script:

using UnityEngine;

public class Player : MonoBehaviour {
    void Start() {
        Debug.Log("Game started")
    }
}

medium

A. Wrong class inheritance

B. Debug.Log cannot be used in Start

C. Start method should be public

D. Missing semicolon after Debug.Log statement

Solution

1. Step 1: Check syntax of Debug.Log line

   The Debug.Log statement is missing a semicolon at the end, which is required in C#.

2. Step 2: Verify other parts

   Class inherits MonoBehaviour correctly, Start can be private, and Debug.Log is valid in Start.

3. Final Answer:

   Missing semicolon after Debug.Log statement -> Option D

4. Quick Check:

   Statements must end with ';' in C# [OK]

Hint: Check for missing semicolons after statements [OK]

Common Mistakes:

• Assuming Start must be public
• Thinking inheritance is wrong
• Believing Debug.Log can't be in Start

5. You want to detect player input and move a character smoothly using Unity's architecture. Which systems must your C# script interact with?

hard

A. Rendering system and audio system

B. Input system and physics system

C. Audio system and input system

D. Physics system and rendering system

Solution

1. Step 1: Identify systems for input and movement

   Detecting player input uses the input system; moving a character smoothly involves physics for realistic motion.

2. Step 2: Exclude unrelated systems

   Rendering draws visuals, audio plays sounds, so they are not directly involved in input and movement logic.

3. Final Answer:

   Input system and physics system -> Option B

4. Quick Check:

   Input + Physics = Player movement [OK]

Hint: Input detects keys; physics moves character smoothly [OK]

Common Mistakes:

• Confusing rendering with input
• Ignoring physics for movement
• Mixing audio with input handling