Skip to content

Clarify writer-lock release and read-only project recovery #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JamieW105 merged 1 commit into from
Oct 28, 2026
Merged

Clarify writer-lock release and read-only project recovery #67

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/user/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Hover/click embedded Play before using held WASD/arrows/Shift. Other keys, press

## Files, saving and reopening

Read-only projects may have another active editor holding the lock or a future unsupported scene schema. Save via **File > Save scene**, keep source assets/sidecars together, and save script files separately. Stop Play and discard runtime changes unless you intend to apply them. Inspect the actual permission/recovery diagnostic before altering files; [Scene System](/docs/open-source/engine/scene-system) describes backups and schema migration.
Read-only projects may have another active editor holding the lock or a future unsupported scene schema. Close the editor that owns the project, then reopen the read-only instance to edit. Normal editor closure releases the writer lock immediately, even if a subprocess is starting. The persistent `temp/editor.writer.lock` file alone does not mean an editor is still running; do not delete it to bypass an active lock. Save via **File > Save scene**, keep source assets/sidecars together, and save script files separately. Stop Play and discard runtime changes unless you intend to apply them. Inspect the actual permission/recovery diagnostic before altering files; [Scene System](/docs/open-source/engine/scene-system) describes backups and schema migration.

## Audio and platform differences

Expand Down
Loading