PC/Mac standalone build in Unity - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Unity build script snippet?

Consider this C# script snippet used in Unity Editor to build a standalone PC/Mac application. What will be the output in the console after running this method?

Unity

using UnityEditor;
using UnityEngine;

public class BuildScript {
    public static void BuildGame() {
        string path = "Builds/MyGame.exe";
        BuildPlayerOptions buildPlayerOptions = new BuildPlayerOptions();
        buildPlayerOptions.scenes = new[] {"Assets/Scenes/Main.unity"};
        buildPlayerOptions.locationPathName = path;
        buildPlayerOptions.target = BuildTarget.StandaloneWindows64;
        buildPlayerOptions.options = BuildOptions.None;

        var report = BuildPipeline.BuildPlayer(buildPlayerOptions);
        if (report.summary.result == UnityEditor.Build.Reporting.BuildResult.Succeeded) {
            Debug.Log("Build succeeded: " + report.summary.totalSize + " bytes");
        } else {
            Debug.Log("Build failed");
        }
    }
}

A Build succeeded: 0 bytes

B Build failed

C Build succeeded: [some positive number] bytes

D Compilation error due to missing using directive

💡 Hint

Think about what BuildPipeline.BuildPlayer returns and what the summary.totalSize represents.

The BuildPipeline.BuildPlayer method returns a BuildReport object. If the build succeeds, the summary.result is Succeeded and totalSize is the size of the built player in bytes, which is a positive number. So the output will be "Build succeeded: [some positive number] bytes".

🧠 Conceptual

intermediate

Which build target should you choose for a Mac standalone build in Unity?

You want to create a standalone build for Mac OS using Unity. Which BuildTarget enum value should you use?

A BuildTarget.StandaloneWindows64

B BuildTarget.WebGL

C BuildTarget.iOS

D BuildTarget.StandaloneOSX

💡 Hint

Mac standalone builds require a specific target for Mac OS.

For Mac standalone builds, Unity uses BuildTarget.StandaloneOSX. Windows builds use StandaloneWindows64. iOS and WebGL are for different platforms.

🔧 Debug

advanced

Why does this PC build fail with 'Missing scenes' error?

Look at this build script snippet. The build fails with an error about missing scenes. What is the cause?

Unity

BuildPlayerOptions options = new BuildPlayerOptions();
options.scenes = new string[] {"Assets/Scenes/Level1.unity", "Assets/Scenes/Level2.unity"};
options.locationPathName = "Builds/MyGame.exe";
options.target = BuildTarget.StandaloneWindows64;
BuildPipeline.BuildPlayer(options);

A The scene paths are incorrect or scenes are not added to the build settings

B The locationPathName must end with .app for Windows builds

C BuildTarget.StandaloneWindows64 is deprecated and causes errors

D BuildPipeline.BuildPlayer requires a callback parameter

💡 Hint

Check if the scenes are included in the Unity build settings and if the paths are correct.

Unity requires scenes to be added to the build settings or referenced correctly. If the scene paths are wrong or not included in build settings, the build fails with missing scenes error.

📝 Syntax

advanced

Which option correctly sets the build location for a Mac standalone build?

Choose the correct way to set the build output path for a Mac standalone build in Unity.

A options.locationPathName = "Builds/MyGame.app";

B options.locationPathName = "Builds/MyGame.exe";

C options.locationPathName = "Builds/MyGame";

D options.locationPathName = "Builds/MyGame.dmg";

💡 Hint

Mac standalone builds produce an application bundle with a specific extension.

Mac standalone builds produce an application bundle with the .app extension. Using .exe is for Windows, and .dmg is a disk image, not the build output.

🚀 Application

expert

How many scenes will be included in this PC build?

Given this build script snippet, how many scenes will be included in the final build?

Unity

string[] scenes = new string[] {
    "Assets/Scenes/Main.unity",
    "Assets/Scenes/Intro.unity",
    "Assets/Scenes/Level1.unity"
};

BuildPlayerOptions options = new BuildPlayerOptions();
options.scenes = scenes;
options.locationPathName = "Builds/GameBuild.exe";
options.target = BuildTarget.StandaloneWindows64;
BuildPipeline.BuildPlayer(options);

A 0

B 3

C 1

D Depends on build settings scenes

💡 Hint

When you specify scenes explicitly in BuildPlayerOptions, those scenes are included regardless of build settings.

When you provide the scenes array explicitly in BuildPlayerOptions, Unity includes exactly those scenes in the build, ignoring the build settings scenes list.

Practice

1. What is the main purpose of creating a PC/Mac standalone build in Unity?

easy

A. To create a separate app that can run outside the Unity editor

B. To edit game scripts directly in Unity

C. To test game performance inside the Unity editor

D. To upload the game directly to the Unity Asset Store

Solution

1. Step 1: Understand what a standalone build is

   A standalone build is a version of your game that runs independently from the Unity editor.

2. Step 2: Identify the purpose of the build

   This build lets players run the game as a normal app on PC or Mac without needing Unity.

3. Final Answer:

   To create a separate app that can run outside the Unity editor -> Option A

4. Quick Check:

   Standalone build = separate app outside Unity [OK]

Hint: Standalone builds run games outside Unity editor [OK]

Common Mistakes:

• Confusing builds with editing scripts
• Thinking builds only test performance inside Unity
• Believing builds upload games to Asset Store

2. Which Unity menu option do you use to start creating a PC/Mac standalone build?

easy

A. File > Build Settings

B. Edit > Preferences

C. Window > Package Manager

D. Assets > Import Package

Solution

1. Step 1: Recall where build options are located

   Unity places build options under the File menu in the Build Settings window.

2. Step 2: Confirm the correct menu path

   File > Build Settings is the correct path to select platform and build the game.

3. Final Answer:

   File > Build Settings -> Option A

4. Quick Check:

   Build Settings menu = File > Build Settings [OK]

Hint: Build Settings is always under File menu [OK]

Common Mistakes:

• Choosing Edit > Preferences which is for editor settings
• Selecting Window > Package Manager which manages packages
• Using Assets > Import Package which imports assets

3. Given this code snippet in Unity, what will happen when you build and run the PC/Mac standalone build?

void Start() {
    Debug.Log("Game started");
}

medium

A. The message "Game started" will appear in the standalone build's console window

B. The message "Game started" will appear in the Unity editor console only

C. The game will crash because Debug.Log is not supported in builds

D. Nothing will happen because Start() is not called in builds

Solution

1. Step 1: Understand Debug.Log behavior in builds

   Debug.Log messages appear in the Unity editor console but are not shown in the standalone build by default.

2. Step 2: Confirm what happens when running the build

   The standalone build runs the Start() method, but its console output is not visible to the user.

3. Final Answer:

   The message "Game started" will appear in the Unity editor console only -> Option B

4. Quick Check:

   Debug.Log visible in editor console, not in build [OK]

Hint: Debug.Log shows only in editor console by default [OK]

Common Mistakes:

• Thinking Debug.Log messages appear in standalone build window
• Believing Debug.Log causes crashes in builds
• Assuming Start() is not called in builds

4. You created a PC standalone build, but when you run it, the game window stays black and does not respond. What is the most likely cause?

medium

A. Your computer does not support Unity editor

B. You did not save the project before building

C. You forgot to add scenes to the Build Settings Scenes In Build list

D. You used Debug.Log in your scripts

Solution

1. Step 1: Identify common build issues

   If no scenes are added to the Build Settings, the build has no content to show, resulting in a black screen.

2. Step 2: Eliminate other options

   Not saving project does not cause black screen; computer support for editor is unrelated; Debug.Log does not cause black screen.

3. Final Answer:

   You forgot to add scenes to the Build Settings Scenes In Build list -> Option C

4. Quick Check:

   Missing scenes in build = black screen [OK]

Hint: Always add scenes to Build Settings before building [OK]

Common Mistakes:

• Assuming saving project fixes black screen
• Thinking computer must run Unity editor to run build
• Blaming Debug.Log for black screen

5. You want to create a PC standalone build that runs only in fullscreen mode and uses a specific resolution of 1920x1080. Which code snippet should you add to your game to enforce this when the build starts?

hard

A. void Update() { Screen.SetResolution(1920, 1080, false); }

B. void Start() { Application.fullScreen = false; Screen.SetResolution(1920, 1080, false); }

C. void Awake() { Screen.fullScreenMode = FullScreenMode.Windowed; }

D. void Start() { Screen.SetResolution(1920, 1080, true); }

Solution

1. Step 1: Understand how to set resolution and fullscreen

   Screen.SetResolution(width, height, fullscreen) sets resolution and fullscreen mode at runtime.

2. Step 2: Choose the correct method and parameters

   void Start() { Screen.SetResolution(1920, 1080, true); } sets 1920x1080 resolution and enables fullscreen in Start(), which runs once at game start.

3. Step 3: Eliminate incorrect options

   void Start() { Application.fullScreen = false; Screen.SetResolution(1920, 1080, false); } disables fullscreen; void Awake() { Screen.fullScreenMode = FullScreenMode.Windowed; } sets windowed mode; void Update() { Screen.SetResolution(1920, 1080, false); } sets resolution every frame, which is inefficient.

4. Final Answer:

   void Start() { Screen.SetResolution(1920, 1080, true); } -> Option D

5. Quick Check:

   SetResolution with fullscreen true in Start() [OK]

Hint: Use Screen.SetResolution(width, height, true) in Start() [OK]

Common Mistakes:

• Setting fullscreen false by mistake
• Changing resolution every frame in Update()
• Using wrong fullscreen mode property