Skip to content

settings

github-actions[bot] edited this page Nov 12, 2026 · 14 revisions

Settings Reference

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

Panel transparency

Settings > Appearance > Panel transparency uses 0% for fully opaque panels and 100% for fully transparent panels. The default OSD Classic theme uses 30% transparency. The Panels colour editor under Customize theme > Interface colours uses opacity, where 70% opacity corresponds to 30% transparency.

Major groups

Group Examples
Appearance Theme, selection style, icon backing, clock/date, screen position.
Home & applications Application folders, startup section/view, Home shortcuts.
Sound Dashboard audio and BGM behavior.
Input Confirm/cancel mapping, USB keyboard, virtual keyboard layout.
Launching Normal ELF IOP reset, ESR, OSDSYS, POPStarter, Ember/PS1 behavior, Neutrino and launch keys.
Storage & devices Memory-card/HDD visibility, MMCE history and storage behavior.
Network IP, netmask, gateway and network-oriented feature controls.
System Core runtime options and maintenance actions.

PS2 hardware clock

Use Settings > System > Set PS2 Clock, then choose Set manually.... The editor starts with the saved PS2 time zone, daylight-saving and 12/24-hour preferences read from NVRAM; active kernel settings provide a fallback if the saved configuration cannot be read. The boxed date/time fields use 1–12 plus an AM/PM field in 12-hour mode, or 00–23 in 24-hour mode. The lower row selects a standard-time UTC offset from −12:00 to +14:00 in one-hour steps, daylight saving on/off, and 12/24-hour format. An existing fractional-hour offset is preserved unless the time-zone field is edited; editing moves to a whole-hour offset in the selected direction. Daylight saving adds one hour to the selected standard-time offset; it is a manual choice, not an automatic seasonal rule. Numeric offsets avoid assuming that every BIOS has the same city/country list. The existing native location-name identifier is preserved.

Left/Right selects a field. Up/Down changes it; L1/R1 changes numeric fields by ten steps. Holding these buttons repeats with the same accelerating speed. DST, hour format and AM/PM toggle with either direction. The complete button-hint row stays centered. Changes to time zone or DST immediately recalculate the valid local date/time limits; local boundary years may be 1999 or 2100 while the converted RTC year remains within 2000–2099. Dates remain valid, including leap years, and no virtual keyboard is needed.

Apply converts the entered local time to the PS2 RTC base, writes and verifies it, then saves and reads back the selected time zone, DST and hour format through the MECHACON configuration service. Date format, PS1 settings, language, location-name identifier and other unrelated configuration bytes are preserved. Identical preferences do not trigger another NVRAM write. If saving fails, Launchstation attempts to restore and verify the previous preferences and RTC and reports any restoration failure. Back cancels all staged edits without writing the RTC or NVRAM. A successful update refreshes the displayed date and time immediately. Ethernet builds also offer Sync from Internet. With a dead clock battery, the time may need setting again after power loss.

PS2 temperature

Settings > System > PS2 Temperature Units (50K and later) selects Celsius or Fahrenheit. On supported consoles, temperature appears two spaces after the time, with a degree symbol. The sensor is read every five seconds using the R3Z MECHACON command; if the first probe is unsupported, the temperature is hidden. Unit changes convert the cached sensor reading immediately. The choice is saved in DASHBOARD.CNF.

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

SELECT chooses the current folder in folder pickers. Program/file settings use the native browser picker. POPStarter path, Ember path and Neutrino path each select an ELF file. Their popups offer Choose a location..., Clear location and Disabled. Disabled keeps the saved path and prevents that loader from launching. Choosing or clearing a location enables it again; clearing restores the normal discovery rules. Each settings row shows its path, Not set or Disabled. Ember uses the selected executable to supply ember.elf when the game's own umbrella lacks it. The game device still owns bios.bin and games/<Game>/. Older Ember folder settings remain supported. VCD remains POPStarter; CUE/BIN/EXE remains Ember.

Language preview

In System > Language, highlighting a built-in language applies it immediately to file-operation and tool messages. The chooser shows translated Copy, Paste and Cancel samples. Confirm keeps the choice for this settings session; Cancel restores the previous language. A configured external .LNG file is reapplied after either action. Save Settings to keep an accepted change.

Reset actions

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

Reset IOP for one launch

Reset IOP before launch remains the saved default for ordinary ELF launches. Hold Confirm for one second when starting an application to reverse that choice for that launch only; release sooner to use the default. The hold is detected without a popup, and the launch context carries the temporary choice without changing configuration. See One-launch IOP override.

Native update install

Update checks run network requests on the serialized IO worker, keeping the popup and spinner animated. Status messages show certificate loading, server lookup and connection, secure-connection verification, request transmission and response reception. The comparison phase has its own title. The install confirmation and up-to-date results show the matching standard or DS34 package's last update time as YYYY-MM-DD HH:MM:SS UTC. This uses that package's updated_at, since a rolling release retains its original publication date. A missing or invalid timestamp shows Unavailable.

Tools > System > Check for updates (below About Launchstation) 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 title.cfg, then replaces both with matching .BAK recovery copies when originals exist. Metadata comes from the same verified package; its boot entry retains the installed ELF filename. A failed replacement attempts to restore both originals. If the app folder already has its SAS ordering timestamp on a memory card or under hdd0:/__common/, the updater reapplies that date after all writes and cleanup, including failed updates. Ordinary folder dates are left to the filesystem; a failure to restore SAS is reported. 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. Recovery-copy failures show the source ELF path and filesystem error code. If a failed backup rename leaves the boot file unreadable, the updater preserves the .BAK and verified .UPDATE files for recovery. Restart LAUNCHSTATION to execute the new build. Older update clients may require a one-time manual package install.

Current Home, Apps and Files placement

Back moves up settings pages and folders; the Settings root and Files device list no longer have a Home button. Use L1/R1 to change sections. Returning to Settings restores its page, selected row, scroll position and Back history, including after saving or discarding changes. Home includes the Applications library and Last folder shortcut. In Home & applications > Start screen, choose Home, Applications, Files, Tools or Settings. Applications starts directly in Home's library viewer with All applications selected. Home also opens that viewer automatically when Recent applications is 0 and its saved history is empty. Files runs the native File Browser directly; separate Apps and Devices labels are retained only where the old internal section identifiers require compatibility. Tools exposes individual built-in utilities. The popup file browser for automatic-start and launch-key targets retains MISC/.

Video mode confirmation

The mode chooser shows each option's nominal signal resolution, progressive (p) or interlaced (i) scan, and refresh rate on the right. NTSC shows 720x480i 60Hz; PAL shows 720x576i 50Hz; VGA shows 640x480p 60Hz; 480p shows 720x480p 60Hz; and 576p shows 720x576p 50Hz. Auto shows the console-region output, independently of the currently selected forced mode. The 60Hz labels use the nominal NTSC/480p rate. Unsupported 576p retains its resolution details and an unsupported label. The six choices are Auto, NTSC, PAL, VGA, 480p and 576p. The duplicate 576i entry is removed; older saved 576i settings load as PAL, preserving the same output.

A changed video mode is previewed for 10 seconds, giving the display time to resync. Press the shown Confirm button to keep the mode for this settings session, or the Back button to revert. These are direct button actions; D-pad input does not select an action. No confirmation within the countdown also restores the previous mode and screen offsets. Save remains a separate action. The switch waits for outgoing graphics transfers and rendering to finish before resetting the GS, then refreshes the dashboard texture pool. NTSC, VGA and 480p use a 640×448 framebuffer; PAL and 576p use 640×512. The dashboard maps the same 640×448 layout to each framebuffer so panels, text, clipping and spacing keep their relative positions. To inspect a mode, press Confirm to keep it, browse Home, Files, Tools, Settings and the Text Editor, then return to Screen calibration to adjust position or select another mode. Progressive and VGA modes require a compatible display and connection. PAL selects interlaced 576i at 50Hz; 576p selects progressive 576p at 50Hz. Native 576p requires retail PS2 ROM 2.20 or newer, or a detected PSX/DESR console with ROM 1.80J or 2.10J. Unsupported 576p is grayed out in the chooser and skipped with Left/Right. PAL stays available at 50 Hz. If unsupported 576p or an invalid mode was saved, startup changes the selection to Auto before GS initialization and uses the console region. Both outputs use the same 10-second confirmation and rollback. PAL and 576p each reserve 2.5 MiB for two framebuffers, leaving 1.5 MiB for textures; oversized padded textures and palettes are rejected before allocation to keep the interface responsive.

Storage driver loading

Drivers load when a browser, application or tool needs the device. Per-device driver auto-start settings have been removed. Old Dash_DevAuto and Dash_ShowUnavailableDevices values are ignored and omitted on save. Eligible device families remain listed, and opening an unprobed device starts its existing lazy driver stack.

OSDSYS program

Settings > Launching > Disc & PS1 loaders > OSDSYS program selects the executable started by the OSDSYS command. A selected program uses the same device handling, arguments and IOP reset policy as launching that file from the browser. The embedded R3Z loader first tries a regular ELF load, then tries an encrypted executable load if the regular load fails or has no entry point. Long configured paths use the normal executable path buffers. Clearing the setting retains the default system-update boot path.

ELF device paths

Ordinary ELF launches use the fixed R3Z 4.80 policy: usb: and mass: become mass0:/..., and numbered USB/MASS paths become massN:/.... ATA and MX4SIO keep their device paths. The handoff-path selector has been removed; old Modern_Device_Handoff values are ignored and omitted on save.

Automatic start and Start screen

Start screen chooses the first view. A configured Settings > Launching > Automatic start & boot > Automatic start target runs afterward only when Automatic start timeout is greater than zero. A timeout of 0s disables automatic start while keeping the target saved, so the selected screen stays open. Held-button launch keys still work at 0s. Any button cancels a running countdown. Save Settings to keep your choice.

Startup application discovery

The cached application list in DASHLIB.CNF is loaded before the selected Start screen opens. When a library scan runs, it checks memory cards afresh even if an earlier status check reported them absent, and reads other devices whose drivers are already running. A failed card check preserves its cached applications for a later retry. The viewer shows scanning status until the result has been applied. Opening another device, launching an application, or using a storage tool loads the required driver on demand. Background scans skip unloaded stacks.

Clone this wiki locally