Skip to content

About

Configurable Playnite Fullscreen boot video with Sunshine and Apollo streaming preload support.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

3 stars

Watchers

1 watching

Forks

Repository files navigation

Playnite Boot Screen

Italiano · Changelog · Troubleshooting · Integration contract

Playnite Boot Screen preview

Playnite Boot Screen is a Playnite Generic Plugin that displays a configurable fullscreen boot video while Playnite Fullscreen starts in the background and can also cover Playnite's built-in Desktop-to-Fullscreen transition.

Demo

Playnite-Boot-Screen_DEMO.mp4

Features

  • Managed video list for supported files in the persistent runtime media folder, while external video paths remain supported.
  • Follow Playnite's Fullscreen display setting or choose a monitor manually, with safe multi-monitor readiness detection.
  • Configurable scaling, fades, mute, and volume from 0 to 100.
  • Choose whether to reveal Playnite as soon as it is ready, wait for the video to finish, or loop until Playnite is ready.
  • Cover Playnite's built-in Desktop-to-Fullscreen transition with the configured boot video; enabled by default and optional in settings.
  • Managed runtime stored outside the replaceable extension installation directory.
  • Configurable Desktop and Start menu shortcut name and icon: Playnite Boot Screen, Playnite Fullscreen, or a custom .ico.
  • Streaming Preload and Continue commands shown directly in the settings page.
  • Public runtime marker for theme/helper plugins that need to suppress duplicate startup intros.
  • English and Italian localization.
  • Local diagnostic logs capped at 2 MiB with one backup.
  • No telemetry, accounts, or network services.

Requirements

  • Windows 10 or 11.
  • Playnite 10.
  • Windows PowerShell 5.1.

The plugin targets .NET Framework 4.6.2 and Playnite SDK 6.16.0.

Installation

Published package

  1. Download the latest Playnite-Boot-Screen-v*.pext file from the GitHub Releases page.
  2. Open the file and allow Playnite to install it.
  3. Restart Playnite.
  4. Open Add-ons → Extension settings → Generic → Playnite Boot Screen.

Development build

Close Playnite, then run:

.\scripts\install-dev.ps1 -Configuration Release

Direct launch

In Quick Setup:

  1. choose a shortcut name and icon;
  2. select Create/update for the Desktop or Start menu shortcut;
  3. close Playnite completely;
  4. launch the new shortcut.

The shortcut uses a hidden VBS bridge, so no PowerShell console should flash.

Streaming integration

Enable streaming preload in the Streaming tab, then copy:

  1. Prep command — Preload;
  2. Detached command — Continue.

No Undo command is required. Preload starts a hidden host, selects the streaming display, primes the video decoder, then pauses and rewinds the video while the overlay stays black. Continue launches or adopts Playnite Fullscreen directly and signals the host to restart playback from the beginning while it keeps tracking readiness behind the same overlay.

See Streaming setup for details and recovery guidance.

Theme and helper integration

While Playnite Boot Screen is actively covering startup, it publishes the signaled Windows event Local\PlayniteBootScreen.StartupIntroHandled.v1. Theme/helper plugins can use this marker to skip their own startup intro for that launch without reading Playnite Boot Screen settings. The marker is independent from the selected video and playback behavior.

See the integration contract for the exact semantics and a C# consumer example.

Aniki ReMake / Aniki Helper

Aniki ReMake / Aniki Helper supports the PBS startup marker, so its own startup intro can be skipped while Playnite Boot Screen is already handling the launch. The extended Aniki ReMake intro is also included as an optional bundled video and can be selected from the normal PBS media library.

This integration does not lock PBS to Aniki: the marker is independent from the selected video, and custom videos or other themes continue to work normally.

Runtime data

Persistent files are stored under Playnite's extension data directory:

%APPDATA%\Playnite\ExtensionsData\71b5c099-3c25-4fe7-b26f-1262c7f0e138\
├── Runtime\
│   ├── config.json
│   ├── media\
│   ├── cache\
│   │   └── video-compat\
│   └── logs\
├── shortcut-icons\
└── shortcut-state.json

The extension installation directory can be safely replaced during updates without deleting custom media, configuration, or logs. Managed runtime files are synchronized by content when Playnite starts, while custom media, configuration, and logs remain untouched.

Place .mp4, .mkv, .webm, .avi, or .mov files directly in Runtime\media, then use Refresh list in the settings page. Files outside this folder can still be selected with Browse external…. WebM files are transparently exposed to the Windows media pipeline through a cached .mkv compatibility alias; the original file is never renamed or modified. The compatibility cache keeps only the alias for the currently selected WebM source and is cleared when a non-WebM video is selected.

Build

Install Visual Studio or Visual Studio Build Tools with:

  • .NET desktop build tools;
  • .NET Framework 4.6.2 SDK;
  • .NET Framework 4.6.2 Targeting Pack.

Then run:

.\scripts\build.ps1 -Configuration Release

Package with the Toolbox supplied by Playnite:

.\scripts\pack.ps1 -Configuration Release

The package is written to dist with a SHA-256 checksum.

Releasing

The repository includes a tagged-release GitHub Actions workflow. See Releasing before creating a tag.

License

Source code is licensed under the MIT License. Third-party names, logos, and trademarks remain the property of their respective owners; see Third-party notices.

About

Configurable Playnite Fullscreen boot video with Sunshine and Apollo streaming preload support.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages