PC/Mac standalone build in Unity - Mini Project: Build & Apply

PC/Mac Standalone Build in Unity

📖 Scenario: You are creating a simple Unity project that you want to build as a standalone application for both PC and Mac. This project will guide you through setting up the build settings, selecting the correct platform, and making a build.

🎯 Goal: Learn how to configure Unity to build a standalone application for PC and Mac platforms step-by-step.

📋 What You'll Learn

Create a Unity project with a simple scene

Set up build settings for PC and Mac

Switch platform to PC and Mac

Build the standalone application

💡 Why This Matters

🌍 Real World

Building standalone PC and Mac applications is essential for game developers and software creators who want to distribute their Unity projects outside the editor.

💼 Career

Understanding how to configure and automate builds for multiple platforms is a key skill for Unity developers working in game studios or software companies.

1

Create a simple Unity scene

Create a new Unity scene and add a GameObject called Cube with a Transform component at position (0, 0, 0).

Unity

# Create a GameObject named Cube at position (0, 0, 0)
// Your code here

Hint

Use GameObject.CreatePrimitive(PrimitiveType.Cube) to create a cube and set its name and position.

2

Set build target to PC, Mac & Linux Standalone

Add code to set the build target to BuildTarget.StandaloneWindows64 for PC and BuildTarget.StandaloneOSX for Mac using EditorUserBuildSettings.SwitchActiveBuildTarget.

Unity

using UnityEditor;

public class SetupScene : MonoBehaviour
{
    void Start()
    {
        GameObject cube = GameObject.CreatePrimitive(PrimitiveType.Cube);
        cube.name = "Cube";
        cube.transform.position = new Vector3(0, 0, 0);

        // Switch build target to StandaloneWindows64
        // Your code here
    }
}

Hint

Use EditorUserBuildSettings.SwitchActiveBuildTarget with BuildTargetGroup.Standalone and BuildTarget.StandaloneWindows64.

3

Create build options and build player

Create a BuildPlayerOptions variable called buildPlayerOptions with scenes set to the current scene path, locationPathName set to "Builds/PCBuild.exe", and target set to BuildTarget.StandaloneWindows64. Then call BuildPipeline.BuildPlayer(buildPlayerOptions).

Unity

using UnityEngine;
using UnityEditor;

public class SetupScene : MonoBehaviour
{
    void Start()
    {
        GameObject cube = GameObject.CreatePrimitive(PrimitiveType.Cube);
        cube.name = "Cube";
        cube.transform.position = new Vector3(0, 0, 0);

        EditorUserBuildSettings.SwitchActiveBuildTarget(BuildTargetGroup.Standalone, BuildTarget.StandaloneWindows64);

        // Create BuildPlayerOptions and build the player
        // Your code here
    }
}

Hint

Use BuildPlayerOptions to set scenes, locationPathName, and target, then call BuildPipeline.BuildPlayer.

4

Print build completion message

Add a Debug.Log statement to print "Build completed successfully!" after the build process.

Unity

using UnityEngine;
using UnityEditor;
using UnityEditor.SceneManagement;

public class SetupScene : MonoBehaviour
{
    void Start()
    {
        GameObject cube = GameObject.CreatePrimitive(PrimitiveType.Cube);
        cube.name = "Cube";
        cube.transform.position = new Vector3(0, 0, 0);

        EditorUserBuildSettings.SwitchActiveBuildTarget(BuildTargetGroup.Standalone, BuildTarget.StandaloneWindows64);

        BuildPlayerOptions buildPlayerOptions = new BuildPlayerOptions();
        buildPlayerOptions.scenes = new[] { EditorSceneManager.GetActiveScene().path };
        buildPlayerOptions.locationPathName = "Builds/PCBuild.exe";
        buildPlayerOptions.target = BuildTarget.StandaloneWindows64;

        BuildPipeline.BuildPlayer(buildPlayerOptions);

        // Print build completion message
        // Your code here
    }
}

Hint

Use Debug.Log to print the message after building.

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