From a1c4ada08b139261a1f70303063553416f699c7d Mon Sep 17 00:00:00 2001 From: Jamie Wells Date: Wed, 21 Oct 2026 07:19:19 +0000 Subject: [PATCH] docs: explain Project scene picker and per-scene environments --- content/editor.md | 2 +- content/editor/scene-hierarchy.md | 9 +++++++++ docs/SCENE_ENVIRONMENT.md | 2 ++ 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/content/editor.md b/content/editor.md index 3bcdba7..3f8e4f1 100644 --- a/content/editor.md +++ b/content/editor.md @@ -8,7 +8,7 @@ Prerequisites: a working desktop graphics session and a writable project locatio 1. In Project Manager, choose **New project**, enter a name and location, choose a template, then **Create project**. For an existing project, choose **Import…**, select its location, and **Import project**. 2. Choose **Open project**. The editor shows the project name in the toolbar. A locked project may open read-only; the **READ ONLY** indicator means authoring changes cannot be saved. -3. Use the **Project** panel's **Scene** tab for objects and **Explorer** tab for files. Select an object to show its properties in **Inspector**. +3. Use the **Project** panel's **Scene** tab for objects and **Explorer** tab for files. Select an object to show its properties in **Inspector**. The settings gear at the top right of Project opens **Change scene**, which loads another scene with its objects and environment. 4. Save with **File → Save scene**. Check Console for `Scene saved transactionally` or a save error. Game Settings exposes autosave; when enabled, changed scenes are saved automatically, with a periodic save check at 30 seconds. Expected result: your project opens with its scene, and a successful save persists authored changes. Save explicitly before closing or copying a project. diff --git a/content/editor/scene-hierarchy.md b/content/editor/scene-hierarchy.md index 9f53b27..cfbeab7 100644 --- a/content/editor/scene-hierarchy.md +++ b/content/editor/scene-hierarchy.md @@ -2,6 +2,15 @@ Prerequisites: open a writable project, stop Play, and switch the **Project** panel to **Scene**. +## Change scenes + +1. Keep your scene files in the project's scenes folder: `scene/` for new projects, or the configured `scenes/` folder in older projects. Both `.scene` and legacy `.rscene` files are supported, including files in subfolders. To try a second scene, save the current scene, then copy `scene/main.scene` to `scene/night.scene` using your file manager. +2. In the **Project** panel, click the **settings gear** at the top right, open **Change scene**, and select a scene. The list shows paths relative to the scenes folder and highlights the current scene. New files appear after the background project scan, normally within a few seconds. +3. The editor saves pending changes to the scene you are leaving, even when autosave is off. It then replaces the hierarchy and viewport with the selected scene's objects, cameras, lights, script attachments and environment. Selection and undo history start fresh. Check Console for `Loaded scene`. +4. Edit **Scene sky & atmosphere** in Inspector and save. Switch back and forth to verify that each scene retains its own sky, ambient light, sun and haze settings. Play, Play Solo and Run use the scene currently selected in the editor. + +Stop play and resolve **Review runtime changes** before switching; **Change scene** is disabled until then. Read-only projects can switch scenes for inspection, but cannot save edits. If loading the target or saving local edits fails, the current scene stays open with its edits intact; inspect Console for `Could not change scene` and fix the reported path, scene data or write-permission issue. Scene files outside the configured scenes folder are not listed. Reopening the project still starts with `main.scene` (or legacy `main.rscene`); the picker does not change the project's startup scene. + ## Create and organise objects 1. Choose **+ Add → Folder** to create an organisational folder. Select the folder before adding children. diff --git a/docs/SCENE_ENVIRONMENT.md b/docs/SCENE_ENVIRONMENT.md index beef4d7..d25fa3d 100644 --- a/docs/SCENE_ENVIRONMENT.md +++ b/docs/SCENE_ENVIRONMENT.md @@ -2,6 +2,8 @@ Each scene can save its own sky image, ambient light, sun light and haze. The settings affect the 3D editor viewport and the game renderer in Play, Play Solo and Run. They are scene settings, so you do not attach a sky to an entity. Inserted scene instances use the containing scene's environment. +Use **Project → settings gear → Change scene** to load another scene together with its objects and saved environment. See [Change scenes](/docs/guides/editor/scene-hierarchy#change-scenes) for file setup, saving behavior and troubleshooting. + ## Topics - [Set up a sky](/docs/guides/scene-environment/set-up-a-sky)