Deploy & Operate

Watchdog

Auto-start on boot

Windows (installer option): The Setup wizard offers an optional autostart task (default off). When selected, it creates a shortcut in the All Users Startup folder (shell:common startup) so any interactive logon launches DearScenario Player once. This is launch only — no GPU delay and no crash restart. Leave it unchecked if an external watchdog or Task Scheduler job already starts the player. After install, operators can verify the shortcut in Explorer via shell:common startup.

Windows (venue / integrator): For delayed start after logon and limited restart-on-exit, configure Task Scheduler separately. A ready-to-edit XML template and import steps live in the repository under doc/deployment/windows-autostart/. Combine with Windows auto-logon for unattended kiosks. Power-on → desktop → picture is a full-machine chain (BIOS, auto-logon, start method); the installer only covers the optional Startup shortcut.

Raspberry Pi: Use systemd with a startup service and Restart=always. See Raspberry Pi Deployment for Lite vs Desktop guidance and a unit sketch. This supervises process exits; DearScenario Player does not terminate itself based on render telemetry.

Single-instance lock

DearScenario Player prevents multiple instances from running with the same config. A second launch exits immediately.

Render health observation

The player reports render FPS and present metrics in the Health API under render. These fields are diagnostic only; any site-specific restart policy belongs to the external process supervisor.

Graceful shutdown

In a Maintenance process, use app_quit through POST /api/maintenance/command from an allowed source, or the Web Console exit action, to release resources cleanly. app_quit is unavailable in Normal mode; it is not a stable playback command.

Shutdown does not save a playback session for automatic recovery. After any restart, playback requires an explicit launch target or a new controller command. See Playback after restart.

Previous / Next