-
Notifications
You must be signed in to change notification settings - Fork 2
Favorites
Press R3 on any game or app to star it. A virtual Favorites page gathers every starred title from every connected device into one list — no matter which drive it lives on.
ℹ Favorites Page Start Mode ships Off
The Favorites tab ships Off under Settings → Game Sources → Favorites Page Start Mode — set it to Manual or Auto before the tab appears and R3 does anything. Use Manual to show the tab and control it yourself, Auto to have OPL manage it the same way it manages other device tabs, or Off to hide the tab and disable R3 entirely.
Open Settings → Game Sources and set Favorites Page Start Mode to Manual (or Auto). Save settings. A Favorites tab now appears alongside your device pages.
Navigate to any game or app on any device page — USB, HDD, SMB, MMCE, anywhere. Highlight the title and press R3 (click the right analogue stick). A small star icon appears next to the title name to confirm it is starred. Press R3 again on the same title to remove the star.
Switch to the Favorites tab. Every starred game you have, across all connected devices, appears here in one list. Cover art, per-game settings, Options — everything works exactly as it does on the source device page.
Select a title on the Favorites page and press Cross to launch it. The game boots through the same path it would on its source device (OPL core or Neutrino, depending on your per-game settings).
The Favorites page is a virtual aggregator — it does not copy or move games. Each entry is a live proxy to the original item on its source device list. Launching, cover art lookups, per-game config, and the Options/Info menu all forward to the source device as if you had selected the game there directly.
- Stars are visible everywhere: a small star mark is drawn next to the title on both the source device page and the Favorites page.
- If a device is disconnected (USB drive unplugged, SMB share unreachable, etc.) its starred titles are hidden from the Favorites list but are not lost — they reappear automatically when the device becomes available again.
- BDM devices (USB, MX4SIO, iLink) can move between bus slots; RiptOPL re-matches the item by game ID and title across all slots, so a favorite does not break just because a drive appeared on a different port.
- Rename and Delete are blocked on favorited titles and on any game accessed through the Favorites page. Un-star the game first if you need to rename or delete it.
Starred games are stored in favourites.bin, written into the same shared OPL config directory as
your artwork, themes, and VMCs — typically mc0:/OPL/ or the root of whichever device holds your OPL
config.
ℹ Shared with uOPL and wOPL
favourites.bin sits in the shared OPL folder, not in the RiptOPL-private settings area. If you
have an existing favourites.bin written by uOPL or wOPL, RiptOPL will read it
automatically on first boot and carry your starred games over. Your favorites will then be saved in RiptOPL's own
versioned OFAV format on the next write. That OFAV format is RiptOPL's own — uOPL and wOPL cannot read it back, so the carry-over is one-way only.
The on-disk format uses an OFAV magic header, a version number, and an explicit record count,
followed by one record per favorite. Every field is written as an explicit scalar (no raw struct dumps), and the
reader validates the header, version, record count, and every text-length field before accepting a file — a
corrupt or truncated favourites.bin is rejected cleanly rather than causing a crash or out-of-bounds
read.
| Field | Value / limit |
|---|---|
| File name |
favourites.bin (shared OPL config dir) |
| Format magic |
OFAV (0x4641464F, little-endian) |
| Format version | 3 (v1/v2 remain readable; v3 uses the old byte as an ISO / VCD / CUE / ELF kind) |
| Maximum favorites | 512 entries |
| Maximum title length | 255 characters + NUL (256 bytes) |
| Import from uOPL / wOPL | Automatic, read-only (one-way carry-over) |
Favorites has one enable/startup option in Settings → Game Sources:
| Setting | Values | Notes |
|---|---|---|
| Favorites Page Start Mode | Off / Manual / Auto | Off (default) hides the tab and disables R3 entirely. Manual shows the tab but does not auto-start into it. Auto behaves like Auto mode on a regular device tab. |
ℹ R3 only works when Favorites Page Start Mode is on
When Favorites Page Start Mode is set to Off, pressing R3 does nothing — no star is set and nothing is written to disk. Enable the tab first.
Favorites keeps its own independent L3 ring. It is not pinned by the shared PS2/PS1 Game Display setting. The page opens on PS2; press L3 to cycle:
- PS2 — PS2 disc favorites only.
- PS1 — POPSTARTER and Ember favorites together.
- ELF — homebrew/app favorites only.
- All in One — PS2, PS1, and ELF favorites together.
The mixed view keeps each row's real behavior: PS1 rows open PS1 options and launch through their own core; ELF rows use the app path; PS2 rows retain normal game options. All four stops remain available regardless of how ordinary device game pages are displayed.
ℹ Where you leave it is where you come back
The shelf you were last on is remembered across reboots, so Favorites only opens on PS2 until you move it. The same applies to every page L3 does something on — each device page and the APPS split side keep their own position. Pressing L3 never writes to storage: a position rides along with a write that already happens — launching a game, or saving settings — so toggling and then powering off without doing either is the one case that is not kept. If a remembered view stops being possible — you switched PS2/PS1 Game Display from Mixed to Both, say — it is discarded and the page opens on its default rather than on a view with no rows.
ℹ Covers in All in One keep their own shape
A PS2 case is
portrait; a PS1 jewel case and an app box are square. On the mixed shelf every row's cover is drawn
at the size its own media uses, instead of one shape being stretched onto all three — so
PS1 and app covers stay square beside portrait PS2 covers. Themes size the three boxes with the
favsMain, vcdMain and appsMain families; see
Block families.
The Favorites page renders using the favsMain element family (which falls back to the regular
game-list main family when the theme defines no favsMain override). The star mark drawn beside favorited titles in any list uses the embedded fav_mark
texture. Themes can override the appearance of the Favorites tab icon via the fav texture slot.
Covers are resolved per row, by media kind, so a mixed shelf never stamps one box on everything: an app favorite
(sourced from the Apps tab) draws with the apps family, a PS1 favorite with the vcd family, and a PS2
favorite with the page's own favsMain element. Each brings its own geometry, case overlay and
placeholder. Only the cover is redirected — the background, the texts and the list itself stay on
favsMain, so nothing moves as you scroll.
For full details on element families and texture slots, see the Theme Engine reference.
What happens to a favorite when a device is not connected?
The record stays in favourites.bin — it is never deleted just because the source device is absent.
When you open the Favorites tab, RiptOPL tries to resolve each stored entry against the currently loaded device
lists. Any entry whose device is not available (drive unplugged, share offline, etc.) is simply hidden from the
visible list. The moment that device is connected and its game list loads, the entry becomes visible again
automatically — no action needed on your part.
Can I favorite a PS1 game?
Yes. PS1 titles shown on a device page can be starred with R3 just like PS2 games. In Both (L3) mode, L3 opens the PS1 page; in Mixed mode, L3 cycles to the PS1-only view. In PS1 mode, the PS1 list is already shown and L3 is disabled. They appear in Favorites and launch through the same row-specific core: POPSTARTER for VCD rows, Ember for CUE/game-folder rows. UDPFS and UDPBD can contribute Ember favorites but never POPSTARTER rows. See PS1 Games for how the PS1 view works.
Can I favorite a Neutrino-backed game?
Yes. Neutrino per-game settings are stored in the game's own per-game config file, not in the Favorites list. A favorited game that is set to use Neutrino will still launch via Neutrino when opened from the Favorites page, because the launch path proxies to the source device entry with all its settings intact.
Source: favourites.html @ fc2e13154e51. Read on the documentation website.
Start here
Storage and networking
- USB, MX4SIO and iLink
- MMCE
- Internal HDD: APA and exFAT
- SMB shares
- Network boot: UDPFS and UDPBD
- HTTP
- NBD server
Games and features
- Neutrino core
- PS1: POPStarter and Ember
- Per-game settings
- Virtual memory cards
- GSM video modes
- In-game reset
- Cheats
- PADEMU
- RetroAchievements
- Apps
Interface and customization
Help and reference
- Troubleshooting
- ZSO format
- Backward-compatible PS3
- Credits and sources
- Features in other forks
- Project overview
Detailed references
- Complete repository guide
- Rolling release reference
- APA hard disk safety and code 402
- Autolaunch and global settings
- Controls reference
- GSM reference
- HTTP reference
- In-game reset reference
- Folders, parental lock and audio
- Language maintenance
- MX4SIO launch reference
- Neutrino reference
- PADEMU reference
- RetroAchievements reference
- Theme engine: full authoring reference
- PS1/VCD reference
- HTTP server conformance tools
- APA recovery tool