Settings Reference

Dashboard settings are grouped by purpose and retain explicit unsaved-state behavior.

Major groups

PS2 clock without a working CMOS battery

Use Settings > System > Set PS2 clock manually... and enter YYYY-MM-DD HH:MM:SS. Launchstation validates the date, writes the PS2 RTC and verifies the readback. With a dead clock battery, the time may need setting again after power loss.

Colored Game ID launch bars

Game ID color output for ELF/application launches is off by default on new configurations. It remains available in Settings > Launching > Game ID output for RetroGEM-compatible display adapters. Previously saved configurations retain their selected value until changed.

Theme-matched controller button icons

Settings > Appearance > Control icon backings controls whether face-button and D-pad symbols receive a theme-derived badge. When disabled, the symbols render without the backing. Button symbols are generated from the built-in vector atlas and need no external icon PNGs.

Unsaved state

Settings compare current serialized values with the session snapshot. Touching a control and returning it to the original value does not leave a false dirty flag. Save failures remain visible and can be retried.

Path pickers

Program/file settings use the native browser picker. POPStarter and Neutrino have explicit ELF path fields. Ember uses an Ember directory picker instead: the folder name/location is arbitrary, but the save-safe umbrella still contains ember.elf, bios.bin and games/<Game>/. When a selected game's own umbrella lacks ember.elf, the configured Ember directory can supply it to that device automatically. VCD remains POPStarter; CUE/BIN/EXE remains Ember.

Unavailable devices

Show unavailable devices controls whether confirmed-missing devices are displayed. Hidden devices are removed from navigation as well as drawing. Unprobed devices remain actionable.

Reset actions

Display/theme reset actions restore known project defaults so users do not need to manually reverse each visual setting.

MMCE backup & sync page

The IGR helper row reports Current, Outdated, Not installed or Partial / mixed by comparing installed helper bytes with the helper this build would install for the current application and backup paths. Entering this page is treated as an explicit request for live MMCE status: if a backup destination is configured and MMCE is not already running, the MMCE stack is started on demand before the read-only status scan. A startup failure is shown instead of leaving the page silently at Not checked.

This page groups the controls that previously lived across Settings and Tools: Sync all cards, Automatic sync, IGR helper, After IGR, Language, retention, backup format, Google account, Check for updates and About. Existing lower-level backup/cloud routines are reused rather than duplicated.

Native update install

Check for updates validates ancestry against the rolling latest release. The updater selects the standard or DS34 PSU package for the running variant, verifies its advertised SHA-256 and contents over trusted HTTPS, stages the verified ELF and then replaces the running app's ELF using a .BAK rollback file. The verified four-file PSU can restore missing updater CA and BGM sidecars, but it does not overwrite existing customized sidecars. Interrupted .UPDATE/.PACKAGE staging files are preserved for manual recovery rather than silently truncated. Restart LAUNCHSTATION to execute the new build. Older update clients may require a one-time manual package install.

MMCE sync status

Sync all cards reports Checking..., All synced, or the number of card images still pending. The pending check is read-only: it compares live MMCE card images with the newest local history without creating, pruning or deleting backups. PCSX2-format history is compared in memory rather than by creating a temporary conversion. Opening this Settings page starts MMCE on demand when live card status is needed, even when MMCE auto-start is disabled. The page shows Starting MMCE... during initialization and reports a startup failure explicitly rather than leaving the status indefinitely at Not checked. The Google account row similarly reports whether the native Drive account is linked.

Current Home, Apps and Files placement

Home includes the Applications library and Last folder shortcut. Files runs the native File Browser directly; separate Apps and Devices labels are retained only where the old internal section identifiers require compatibility. Tools is where classic MISC commands live.

MMCE and Drive recovery

The MMCE backups Settings page can select a local snapshot for non-destructive recovery. The Google account/Tools cloud menu can browse remote history and recover a SHA-256-qualified snapshot into a new image on USB/HDD. Neither flow automatically replaces a live MMCE card. Recovery details.