Test and perform

Publish and Performance

Protect a known-good stage version from unfinished Editor changes.

Browse documentation

Start here

Create and edit

Make it playable

Test and perform

Trust and help

On this page

Why Publish is explicit

The draft is mutable and autosaved. A published revision is immutable. This separation prevents a half-finished Editor change from silently replacing the last version that is ready to perform.

What happens during Publish

  1. VMuse saves the latest draft.
  2. The active scene is validated for playability.
  3. A new immutable revision is committed.
  4. Referenced audio, images, and animation artwork are prepared.
  5. The revision-bound Performance runtime is verified.
  6. Only then is the revision marked last-known-good.

Full-screen Performance

  • Plays the last prepared published revision on the same iPad.
  • Provides master volume and Mute All.
  • Uses a protected three-second hold to exit.
  • Keeps later draft changes separate until you publish again.