PC/Mac standalone build in Unity - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the build target to PC standalone.

Unity

BuildPipeline.BuildPlayer(scenes, path, BuildTarget.[1], BuildOptions.None);

Drag options to blanks, or click blank then click option'

AStandaloneWindows64

BAndroid

CWebGL

DiOS

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Android or iOS build targets for PC builds.

Using WebGL which is for browser builds.

Use StandaloneWindows64 to build for PC (Windows 64-bit).

2fill in blank

medium

Complete the code to set the build target to Mac standalone.

Unity

BuildPipeline.BuildPlayer(scenes, path, BuildTarget.[1], BuildOptions.None);

Drag options to blanks, or click blank then click option'

AStandaloneOSX

BStandaloneWindows

CStandaloneLinux64

DAndroid

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting Windows or Linux build targets for Mac builds.

Confusing Android with desktop platforms.

Use StandaloneOSX to build for Mac standalone.

3fill in blank

hard

Fix the error in the build target for a Mac standalone build.

Unity

BuildPipeline.BuildPlayer(scenes, path, BuildTarget.[1], BuildOptions.None);

Drag options to blanks, or click blank then click option'

AiOS

BStandaloneWindows64

CWebGL

DStandaloneOSX

Attempts:

3 left

💡 Hint

Common Mistakes

Using Windows or WebGL build targets for Mac builds.

Confusing iOS with Mac standalone.

The correct build target for Mac standalone is StandaloneOSX.

4fill in blank

hard

Fill both blanks to build for PC standalone and specify the output path.

Unity

string outputPath = [1];
BuildPipeline.BuildPlayer(scenes, outputPath, BuildTarget.[2], BuildOptions.None);

Drag options to blanks, or click blank then click option'

A"Builds/PCGame.exe"

B"Builds/MacGame.app"

CStandaloneWindows64

DStandaloneOSX

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing Mac output paths with PC build targets.

Using Mac build targets with Windows executable paths.

Use the Windows executable path and StandaloneWindows64 target for PC builds.

5fill in blank

hard

Fill all three blanks to build for Mac standalone with scenes, output path, and build target.

Unity

string[] scenes = [1];
string outputPath = [2];
BuildPipeline.BuildPlayer(scenes, outputPath, BuildTarget.[3], BuildOptions.None);

Drag options to blanks, or click blank then click option'

Anew string[] {"Assets/Scene1.unity"}

B"Builds/MacGame.app"

CStandaloneOSX

DStandaloneWindows64

Attempts:

3 left

💡 Hint

Common Mistakes

Using Windows build target or output path for Mac builds.

Passing scenes as a single string instead of an array.

Use the correct scenes array, Mac output path, and Mac build target for a Mac standalone build.

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