Guides / Unity Game Engine / Unity Basics: Interface, Projects, and First Scene

Unity Basics - Interface, Projects, and First Scene

What this chapter covers

You will install the Unity Hub, create a real project, learn the main editor windows, and save a first scene. By the end you should be able to open Unity, know where everything lives, and press Play without getting lost.

Time focus: About one focused session. Do not worry about art or code yet. This chapter is only about the editor shell and a clean project start.

Step 1 - Install Unity Hub and an Editor

Unity Hub is the launcher that manages editor versions and projects.

Download Unity Hub from Unity’s official download page.
Install Hub, then open it and sign in (or create a free Unity ID).
In Hub go to Installs and add an LTS (Long Term Support) editor version if you are unsure which to pick. LTS is the safest default for learning and shipping small games.
When the installer asks for modules, add support for your OS build target at minimum (e.g. Windows Build Support if you are on Windows).

Pro tip: One LTS version is enough to start. You can add more editor versions later when a tutorial or asset package requires them.

Step 2 - Create a new project

In Unity Hub open Projects, then New project.
Choose a template. For a general start, 3D (URP) or 3D is fine. URP (Universal Render Pipeline) is common for new projects; you can switch pipelines later with more work, so pick what matches your goal.
Set a project name and a location on disk you control (avoid synced folders like aggressive cloud sync roots if you see strange file locks).
Click Create project and wait for the first import to finish.

Pro tip: Keep project paths short and ASCII-only when possible. Deep paths and special characters sometimes break tools or third-party plugins.

Step 3 - Learn the default editor layout

Unity’s editor is split into windows (panels). The default layout is a good baseline.

Scene view

What it is: A 3D (or 2D) workspace where you place and edit objects.
You use it to: Move, rotate, and scale things, preview lighting, and arrange your level.
Navigation: Orbit with middle mouse (or Alt + left mouse on many setups), pan, zoom. If navigation feels wrong, check Edit → Preferences for navigation settings.

Game view

What it is: What the Main Camera sees. This is closer to what a build will show.
You use it to: Check framing, resolution, and UI scale while editing.

Hierarchy

What it is: A tree of GameObjects in the current scene.
You use it to: Select objects, parent and group them, toggle active state.

Inspector

What it is: Properties of whatever is selected (transform, components, assets).
You use it to: Change numbers, assign references, add components.

Project window

What it is: Files inside your project’s Assets folder.
You use it to: Create folders, import art and audio, open scenes and prefabs.

Console

What it is: Logs, warnings, and errors from Unity and your scripts.
You use it to: Debug. Clear it often so new messages are obvious.

Pro tip: You can save window layouts under Window → Layouts. Many developers keep one layout for coding and one for level design.

Step 4 - Your first scene workflow

When the editor opens, you usually start in a scene named something like SampleScene (names vary by template).
In Hierarchy, select Main Camera and Directional Light. Notice how the Inspector changes for each.
Use File → Save As to save the scene into a folder such as <code>Assets/Scenes/</code> with a clear name like <code>MainMenu</code> or <code>Sandbox</code>.

Pro tip: Create folders early (<code>Scenes</code>, <code>Scripts</code>, <code>Art</code>, <code>Audio</code>) so imports do not land in the project root.

Step 5 - Play mode and why it matters

Press the Play button at the top center of the editor.

While Play is on, many changes are temporary unless your workflow explicitly writes assets. That is by design.
Press Play again to stop. Learn to stop Play before editing serious data so you do not confuse “test tweaks” with real saves.

Common mistake: Decorating a level in Play mode for an hour, then stopping and losing work. If you like what you see while playing, copy values or duplicate objects after stopping, or use a workflow that preserves changes intentionally.

Step 6 - Project settings worth a glance

You do not need to master these today, but know they exist:

Edit → Project Settings - Input, graphics, physics, quality tiers, player name, company, icons.
File → Build Settings - Which scene ships first, which platform you build for.

You will return here when you add a second scene or change resolution defaults.

Quick checklist before the next chapter

[ ] Unity Hub installed and signed in
[ ] One LTS editor installed
[ ] New project created from a template you understand
[ ] You can name and save a scene under <code>Assets/Scenes/</code>
[ ] You can find Scene, Game, Hierarchy, Inspector, Project, and Console
[ ] You know Play mode can discard changes when you stop

Next up

Continue with GameObjects, Components, and the Hierarchy to learn how objects in the scene are built from components and how parent-child relationships work.