Repository navigation
Installation
The RiptOPL menu and OPL core are in RIPTOPL.ELF. Neutrino and PS1 launching also need their companion folders. Extract the installable package, choose a loader, and copy the files needed by your source/core.
RiptOPL is the C++ rewrite of Open PS2 Loader,
built with one SDK, ps2build, into a single PS2 ELF. It is the main line of this project; the C codebase lives on as the
legacy Open-PS2-Loader edition. The standard loader includes
GSM video-mode handling (including the forced-progressive 1080p mode), DS3/DS4 pad emulation (PADEMU), Virtual Memory Cards,
PS2RD cheats and parental controls in one file. In-game screenshots (IGS) and right-to-left (RTL) language support are not in
the standard loader; they belong to the extras configuration. USB DualSense support is the ds5
configuration. Ready-made loaders for both are in the Korium and IncebtIon releases' RIPTOPL-VARIANTS-<version>.zip (see
Releases). The 1080p picker is gated behind a triple confirmation, and holding Triangle + Cross
during console boot forces 480p for the menu only, on displays and connections that accept it.
Private config, shared data
RiptOPL's master settings use settings_riptopl.cfg (with migration from
conf_riptopl.cfg). That filename is separate from stock OPL's master config, but
conf_network.cfg, app lists, per-game configuration and support files can still be shared.
Favorites import from uOPL/wOPL is one-way: the next write saves RiptOPL's own OFAV
format to favourites.bin, which those loaders cannot read back. Keep an original copy if
you use them too. The settings home follows boot-directory discovery or Custom Settings Path;
do not assume it is always mc0:/OPL/.
RiptOPL publishes three editions, each with its own release channel. They are development builds from
rebuild/main: every build is verified before publication, but none is a compatibility guarantee, so check the
release notes for the exact build.
| Edition | Tag | What it is |
|---|---|---|
| Korium | rolling-korium |
The standard loader with the Korium Komblete theme. Also carries RIPTOPL-VARIANTS-<version>.zip and RIPTOPL-DEBUG-<version>.zip. |
| IncebtIon | rolling-incebtion |
The standard loader with the IncebtIon theme. GitHub marks it as Latest. Also carries RIPTOPL-VARIANTS-<version>.zip and RIPTOPL-DEBUG-<version>.zip. |
| RetroAchievements | rolling-ra |
Korium with the RetroAchievements runtime and the NULD (formerly ORBIT) Neutrino RA runtime v1.2.12 in place of upstream Neutrino, plus the same kit built with the IncebtIon theme. See RetroAchievements. |
Download your edition's install kit (RIPTOPL-Korium-<version>.zip, RIPTOPL-IncebtIon-<version>.zip or
RIPTOPL-RetroAchievements-<version>.zip), unzip it, and either copy its ready app folder
(APPS/APP_RIPTOPL/) to a device or import APP_RIPTOPL.psu onto a memory card. See
Releases for the full asset list.
Already have RiptOPL installed?
This page is for a first install. To update, each channel carries a loose loader whose name and link never change:
RIPTOPL.ELF for Korium,
RIPTOPL.ELF for IncebtIon and
RIPTOPL-RA.ELF for RetroAchievements. It is the exact
loader inside that kit. Overwrite the ELF you already have; POPS/, EMBER/, neutrino/ and
your settings stay where they are. Use the full kit instead if companion folders are missing or the release notes announce updated
companion cores or modules: replacing only the loader does not update Neutrino or Ember. Back up your configuration and save cards
before updating.
The Korium, IncebtIon, RetroAchievements and LLVM builds can also do this themselves: Check for Updates, just above About in the main menu, asks the build's own rolling release for a newer build and, when you press OK, replaces the running ELF after checking its SHA-256. It needs RiptOPL started from a memory card or a USB/exFAT drive, a network connection with internet access, and the console clock set (Settings → General & System → Date and Time). It replaces only the ELF. RiptOPLite, debug and variant builds do not have it. See Check for Updates. Not tested on hardware yet.
What is inside the install kit?
Each RIPTOPL-<edition>.zip contains:
-
APPS/APP_RIPTOPL/(APP_RIPTOPL-RA/in the RetroAchievements kit): the ready-to-install app,RIPTOPL.ELFwith its icons,title.cfgand music. Copy the folder into a device'sAPPS/. -
APP_RIPTOPL.psu: the same app as one memory-card save for a PS2 save manager. It holds only the app folder's own files. -
ART/: the app's matching artwork for the device'sART/folder. -
POPS/: the single folder for POPSTARTER support. It containsPOPSTARTER.ELF, the SMB modules,PATCH_5.BINand every loose BDMAusbd.irx.*/usbhdfsd.irx.*pair, including.ilinkand Okeanos's.udpfspair, plus optionalIPCONFIG.DAT/UDPFSCONFIG.DATexamples and upstream notices. See POPS UDPFS setup. No BDMA pair is embedded inRIPTOPL.ELF. OnlyPOPS.ELF, Sony's PS1 emulator, is not distributed here. -
EMBER/: the bundled Ember PS1 core, unmodified and ready for your own BIOS and games. -
neutrino/: the official Neutrino release, extracted as a drag-and-drop folder (neutrino.elf+config/+modules/) with RiptOPL's UDPFS config added and its i.LINK pair replaced by RiptOPL's builds (see Credits). The RetroAchievements kit carries the NULD (formerly ORBIT) Neutrino RA runtime v1.2.12 instead (see RetroAchievements); an ELF-only update does not install it. It is used by per-game Neutrino launching and network boot (UDPBD/UDPFS). Copy the whole folder; see step 3 below. -
BUILD-MANIFEST.json,LICENSE,CREDITSandREADME.md. - Five
.urlshortcuts: PS2-Servers, udpfs-server, OrbitPS2 Manager, OPL PS1 AIO Converter GUI and PS2RD CHT Manager. The tools themselves are not embedded. The RetroAchievements kit adds a shortcut to the xeRAbora client.
Translations are a separate asset, RIPTOPL-LANGS-<version>.zip (see Languages). Every channel
also publishes the loose loader, the app .psu, RIPTOPL-src-<version>.zip (the exact built commit),
BUILD-MANIFEST.json and SHA256SUMS.txt.
RiptOPL requires a way to boot unsigned ELFs on the PS2. The two most common are FreeMcBoot (FMCB) on a memory card and FreeHDBoot (FHDB) on an internal HDD; FreeDVDBoot is a separate disc-based entry point. Any method that can launch an ELF works.
Go to the Releases page, pick an edition, and download its install kit: RIPTOPL-Korium-<version>.zip, RIPTOPL-IncebtIon-<version>.zip or RIPTOPL-RetroAchievements-<version>.zip. Unzip it locally.
The loader is APPS/APP_RIPTOPL/RIPTOPL.ELF inside the kit. The simplest install is to copy the whole APPS/APP_RIPTOPL/ folder into a device's APPS/ (or import APP_RIPTOPL.psu onto a memory card) and point your launcher at the RIPTOPL.ELF inside it. Where the ELF goes depends on your boot method:
-
FMCB — copy
RIPTOPL.ELFto a folder on a device that your launcher can access, such as a USB drive or memory card, then add a FMCB menu entry pointing to it. A common convention ismass:/APPS/RIPTOPL/RIPTOPL.ELFormc0:/RIPTOPL/RIPTOPL.ELF. - FHDB — copy into an HDD partition the same way FHDB expects its launch targets.
- Other launchers — place the ELF wherever that launcher is configured to find it; RiptOPL has no path requirements of its own.
The ELF filename itself does not matter to RiptOPL, only to your launcher's menu entry.
Copy the bundled neutrino/ folder (drag-and-drop: neutrino.elf + config/ + modules/, with RiptOPL's UDPFS config added) to a location RiptOPL can keep available through the launch handoff. For ordinary non-MMCE setups, mc0:/neutrino/ or mc1:/neutrino/ is supported. For MMCE games with GameID card switching, put the folder on the MMCE game device: mmce0:/neutrino/ / mmce1:/neutrino/, or under your configured MMCE Prefix Path. The automatic lookup probes the active game's prefix and device root before the memory cards. If Neutrino resolves from mcN: on the MMCE slot, RiptOPL deliberately skips that slot's GameID switch so the loader is not displaced, which means the per-game card switch is not applied for that launch. To use a copy anywhere else, set Settings → Game Launching → Neutrino Defaults → Neutrino Path to its full path. See Neutrino Core.
OPL expects a specific folder layout on whichever device(s) you plan to load games from. You do not need to create these by hand — RiptOPL auto-creates them once you enable that device — but it helps to know what they are:
DVD/ ← DVD5 and DVD9 ISO images
CD/ ← CD-based game images (blue-bottom discs)
ART/ ← cover art images
CFG/ ← per-game settings files
VMC/ ← Virtual Memory Card images
THM/ ← themes
LNG/ ← language / translation files (see Languages)
CHT/ ← PS2RD cheat files
APPS/ ← homebrew ELF files (see Apps)
For the APA/PFS internal HDD, a usable configured data partition takes priority, followed by existing +OPL (root), then __common/OPL/. No partition is created; see HDD setup. For exFAT HDD (BDMAssault) and all other folder-based devices (USB, MMCE, MX4SIO, iLink, SMB), the folders live at the root of the device.
Auto-creation on device enable
When you enable a device mode in OPL settings and exit back to the game list, OPL automatically creates any missing folders on that device. Nothing is created on a fresh first boot, because every device ships off. You do not need to pre-create DVD/, ART/, etc. manually — just enable the device, save settings, and the directories will appear.
For Japanese UTF-8 game titles with English menus, RiptOPL can load font_CJK.ttf from the same directory as settings_riptopl.cfg. Restart to enable. The font is user-supplied; read the installation guide for naming, builds and memory limits.
Boot through FMCB, FHDB, or your chosen launcher. On a fresh install you land on the start menu — no game-list tabs exist yet, because every device ships off. Enable a device and its tab appears, drawn by the built-in <OPL> theme until you pick another (such as Coverflow or PSBBN Flow), once you have games in the right folders.
Navigate to Settings → Game Sources. Enable the storage device(s) you want to use. Nothing is on by default: turn USB on and set the BDM tab's start mode to Manual or Auto, then save. Games in DVD/ and CD/ appear after the first scan. For SMB, HDD, MMCE, MX4SIO, iLink, or network boot, enable the corresponding toggle and fill in any required details (IP address for SMB/network boot, etc.).
Go to Settings → Save Changes (or the equivalent save action in the settings screen). This writes settings_riptopl.cfg to the config path and auto-creates the device folders. From this point on, RiptOPL remembers your preferences across boots.
Back on the main list, your games appear under the device tabs. Highlight a title and press the confirm button: Cross, or Circle on Japanese consoles. It is configurable, so follow the on-screen hints. The game boots via OPL's built-in core by default. To use Neutrino instead, open Game Settings → Loader Core → Neutrino for that title. See Per-game Settings.
These are the values RiptOPL uses when no saved settings are found; they match the original Open-PS2-Loader's fresh defaults. Existing saved settings override them, and updating the ELF does not reset them. See Defaults for the full list and how to get the widescreen carousel look.
| Setting | Default | Where to change |
|---|---|---|
| Menu aspect ratio | 4:3 (Widescreen off) | Interface |
| Theme | <OPL> (built-in) | Interface |
| Theme View | Default (List for <OPL>); Coverflow, PSBBN Flow and Grid are optional views | Interface, or hold L3 |
| Cover Art | On | Interface → Artwork Settings |
| Per-game background art | Off in Korium and RetroAchievements; On in IncebtIon | Interface → Artwork Settings |
| Notifications (popups) | On | Interface |
| PS2 Logo | On | Game Launching |
| Sound effects, boot sound, background music | Off (stored volume 90) | Audio Settings |
| Controller Vibration in Menus | Off | Controller Settings |
| Confirm button | Cross; Circle on Japanese consoles | Controller Settings |
| USB, iLink, MX4SIO, Internal HDD (exFAT) | Off | Game Sources |
| Every start mode (HDD, MMCE, BDM devices, network, Apps, Favorites) | Off | Game Sources |
| Video mode | Auto | Interface (menu only) |
| Write Operations (rename, delete, VMC creation) | On | General & System |
| Show GameID Barcode (Pixel FX) | On (POPSTARTER only): PS1 half On, PS2 half Off | Interface |
| Network Connectivity | Off | Game Sources |
Start modes
A fresh install ships with every device Off, so no device tabs appear until you enable one in Game Sources. Once a device is enabled, pick its start mode: Manual keeps the tab visible and only populates the game list when you navigate to that tab and explicitly trigger a scan — no automatic background scanning on boot — while Auto scans that tab when OPL starts.
RiptOPL's master settings use settings_riptopl.cfg (with migration from
conf_riptopl.cfg). That filename is separate from stock OPL's master config, but
conf_network.cfg, app lists, per-game configuration and support files can still be shared.
Favorites import from uOPL/wOPL is one-way: the next write saves RiptOPL's own OFAV
format to favourites.bin, which those loaders cannot read back. Keep an original copy if
you use them too. The settings home follows boot-directory discovery or Custom Settings Path;
do not assume it is always mc0:/OPL/.
If you previously used an older RiptOPL build that saved as conf_riptopl.cfg, the new build automatically migrates your settings the next time it saves — you do not need to rename anything manually.
RiptOPL does not read official OPL's conf_opl.cfg (changed 2026-10-29, RiptOPL #190). When the place RiptOPL reads its settings from has no RiptOPL settings, it starts from its own defaults, even with official OPL's file beside it, and the first save writes settings_riptopl.cfg; official OPL's file is never written. The files the two loaders share, such as conf_game.cfg, conf_network.cfg, the apps list and last played, are still read, so after swapping RIPTOPL.ELF in for OPNPS2LD.ELF (in a PSBBN, OSDMenu or HDD-OSD launcher, or a plain memory card or USB install) the global game settings and the network setup carry over. Set the device start modes and menu options once in RiptOPL's Settings and save. NOT TESTED on hardware.
Auto Loading (a game started straight from PSBBN, OSDMenu or another launcher) reads the same settings home as the menu, so global game settings apply the same way, and it starts the game on the core you chose: the game's own Loader Core, or the Default Loader Core when the game is set to Default, Neutrino included. If such a launch cannot go ahead, because the ISO is missing or the device cannot be used, RiptOPL opens its menu instead of stopping on a black screen.
The config file is discovered and written in this priority order (first found wins on read; saves always go back to the same path it was read from):
- The folder
RIPTOPL.ELFwas launched from (its working directory) — this is the config home - Only when the boot path cannot be determined does OPL fall back, in a fixed sequence, starting with the
config.pathredirect pointer file in the current working directory (the Krah bootstrap — it stores the directory of the last saved config and is rewritten on every save) - then
mc0:/mc1:explicitly, then the boot device (mass:orhdd:), then MMCE, then BDM devices, then the BDM/internal HDD (hdd0:__common/OPL/)
Everything else — cover art (ART/), themes (THM/), VMC images (VMC/), per-game config files (CFG/), and favourites.bin — lives in the shared OPL/ folder structure and is read and written by any OPL-family build that understands those formats. RiptOPL will import an existing favourites.bin from wOPL or uOPL on first launch.
All artwork lives in one place: the ART/ folder on the device the item is on. There is
no second location and no fallback folder — if a cover is not appearing, the filename is what to check, not
the path.
Only the key — the part before the suffix — changes with the kind of item:
| Item | Key | Example |
|---|---|---|
| PS2 game | The game ID | ART/SLUS_012.34_COV.png |
| PS1 game (VCD, POPSTARTER) | The VCD's name | ART/Spyro 2 (Ripto's Rage)_COV.png |
| PS1 game (Ember) | The PS1 disc ID | See PS1 Games |
| App | The boot ELF filename | ART/MYAPP.ELF_COV.png |
The suffix says which image it is — _COV is the cover, _SCR and
_SCR2 are screenshots, _BG a background, _ICO an icon. Which of them a
given theme actually draws is up to that theme; see Theme Engine for authoring, and
Coverflow for what the optional carousel theme uses.
Many small files can be slow to open
On a slow device a folder of loose images costs one file open per cover. Cover Art .tar Archive
(Settings → Interface, off by default) is an opt-in loader that also reads art from a single
ART/art.tar alongside the loose files. See the Settings Reference.
Source: install.html @ 2e6dafac320f. Read on the documentation website.
Start here
- Getting started
- Fresh-start defaults
- Installation and first boot
- Releases and packages
- Launch diagnostics
Storage and networking
- USB, MX4SIO and iLink
- MMCE
- Internal HDD: APA and exFAT
- PSX DESR DVR (experimental)
- PC CARD CompactFlash (experimental)
- SMB (moved to Network)
- Network: SMB, UDPFS and UDPBD
- HTTP
- NBD server
Games and features
- Game image formats: ISO, ZSO, CHD and CSO
- Neutrino core
- PS1: POPStarter and Ember
- Per-game settings
- Virtual memory cards
- File Manager
- GSM video modes
- In-game reset
- Cheats
- PADEMU
- RetroAchievements
- Apps
Interface and customization
- Settings reference
- Controls
- Coverflow
- Favorites
- Game library: All Games, Recent, Hide and Delete
- Theme engine
- Languages
- Japanese / Unicode game titles
Help and reference
- Troubleshooting
- ZSO format
- Backward-compatible PS3
- Credits and sources
- Features in other forks
- Notes for ps2sdk
- Project overview
Detailed references
- Documentation index
- Interface screenshots and capture workflow
- Test builds and diagnostics
- Launch diagnostics by package, core and transport
- Learning across PS2 loader projects
- VMC creation and recovery
- PC CARD CF implementation reference
- DESR DVR implementation reference
- Per-game console i.LINK ID
- Per-game parental lock
- SIO2MAN hook compatibility
- APA hard disk safety and code 402
- Autolaunch and global settings
- Folders, parental lock and audio
- Language maintenance
- HTTP server conformance tools
- APA recovery tool
- Setup questions and reporting launch failures
- Editions and build configurations
- Automatic VMC creation
- Compressed PS2 images: ZSO, CSO and CHD
- Favorites storage, staged saves and recovery
- CFG titles in game lists
- RA watch-list and snapshot budgets
- Maintaining the documentation
- Where every setting lives
- Check for Updates