Troubleshooting
Step-by-step fixes for the most common RiptOPL problems — boot hangs, blank screens, video mode locks, white-screen game failures, BDMA driver errors, and PS1/VCD list issues.
OPL freezes on the logo or grey screen
Symptom: RiptOPL hangs at the animated logo or a grey screen on every boot — the game list never appears.
Likely cause: A corrupted or incompatible config file (from an older build, a partial write, or a settings collision) is being loaded during initialization.
Skip config on boot
Power on your PS2 and immediately hold START while RiptOPL initializes. Keep it held until the interface appears. This tells OPL to skip loading the saved config and boot with defaults instead. Expect to land on the start menu with no game-list tabs — that is what the defaults look like, since every device ships off — not on a game list.
Open and re-save settings
With the loader running (config skipped), open Settings and configure the options you need — at minimum, enable the device mode(s) you use. Then Save so a fresh, valid settings_riptopl.cfg is written.
Verify the fix
Reboot OPL normally (without holding any buttons). If it reaches the game list or settings screen without freezing, the bad config has been replaced. If it still freezes, the file may need to be deleted manually from your memory card's OPL/ folder via uLaunchELF or a similar file manager.
Why does RiptOPL have its own config file?
RiptOPL saves its master config as settings_riptopl.cfg (auto-migrated from the older conf_riptopl.cfg). This is intentionally separate from stock OPL's conf_opl.cfg so both builds can coexist on the same memory card without clobbering each other's settings. Everything else — artwork, themes, VMCs, per-game configs, and favourites — lives in the shared OPL/ folder and is readable by all OPL-family builds.
Game stops on a white screen
Symptom: A game starts to load but freezes on a white (or black) screen and never reaches the title screen or menu.
Likely cause: The game image is fragmented across the storage device, so OPL cannot read it in one continuous pass. A corrupt or incomplete dump produces the same symptom.
Check image integrity
If you have a known-good checksum (MD5/SHA) for the dump, verify the file against it. An incomplete copy or a rip error produces a file of the right size that fails at load time.
Defragment by re-copying
Copy all game files off the device to a PC. Reformat the device (FAT32 or exFAT, as appropriate). Copy the files back one at a time, in order, so each game lands contiguous on disk. OPL supports up to 64 fragments per file (since v1.2.0 beta), but a fully contiguous copy is the most reliable state.
Relaunch and verify
Boot the same title again. If it passes the white screen and reaches the game's intro or menu, fragmentation was the cause. If it still fails after a clean recopy, the dump itself is likely corrupt — source a fresh rip.
No display on boot (blank or black screen)
Symptom: The PS2 is running but the TV shows nothing — no OPL interface appears at all.
Likely cause: A video mode (or GSM override) was saved that your display does not support. This is the most common trigger after experimenting with GSM video-mode or scaling settings.
Hold Triangle + Cross at boot
Power on your PS2 and immediately hold Triangle + Cross while OPL initializes. Keep both buttons held until the interface appears (or until you have waited a few seconds). This forces the video mode to 480p progressive — a mode virtually every display syncs — without touching any other settings. (Older builds reset to Auto, which resolves to interlaced 480i/576i: exactly what some modern displays and upscalers can't lock onto.)
Verify the display returns
Start OPL normally (without holding buttons). If the interface is now visible, you're running in the safe 480p recovery mode. Open Settings → Video and pick your preferred mode (or Auto).
PS1/VCD — "my VCDs don't show up" (works elsewhere)
Symptom: A device lists PS2 games fine (or works in another loader), but its PS1/VCD view is empty — or a listed VCD does nothing when selected.
Work down this ladder; each step isolates a different stage:
Does the device page appear at all?
If not, it's the device enables, not VCD. Every device ships OFF on a fresh install, so check Device Settings first: USB/MX4SIO/iLink need their own toggles on and BDM Start Mode set to Manual or Auto, and the internal exFAT page additionally needs HDD (GPT/MBR) ON. The two internal-HDD backends are no longer mutually exclusive — APA (HDD start mode) and exFAT/BDM-ATA may both be enabled at once, since one shared ATA stack serves both, so leaving APA on does not suppress the exFAT page.
Do PS2 ISOs list from the device?
If yes, the filesystem/mount layer is proven working, so "but it works in another loader" adds no new information past this step. Both published builds — PS2DEVLATESTSDK (recommended) and PS2DEVPINNEDSDK (the digest-pinned fallback) — take their exFAT/BDM drivers from the stock ps2dev SDK, so the flavour you picked does not change this answer.
Press L3 on the device page
The VCD view is per device and only reachable when Default game view is "Both" (or the page is locked to VCD).
Check the folder — root, not your games prefix
VCDs are scanned from <device-root>:/POPS/*.VCD. The game-folder prefix (usb_prefix etc.) is deliberately not applied, because POPSTARTER itself only reads /POPS at the root. A POPS folder inside your games subfolder will never be found.
Check the filename
Basenames longer than 160 characters and the reserved name POPSTARTER.VCD are skipped at scan (the debug log says which) — previously they listed but could never launch (a dead ✕ button). Rename the file.
Fails only after selecting a game?
Then scanning is fine and the handoff is the suspect: is POPSTARTER.ELF present in /POPS (or __common/POPS on APA)? On exFAT the BDMA equip below is best-effort — a failed equip toasts but the launch still proceeds and may land on the OSD.
BDMA — "module files not found on source device"
Symptom: You have set a BDMA Mode (e.g. USB (exFAT), MX4SIO (exFAT), or HDD (exFAT)) and a BDMA Source, but when you save or apply the equip RiptOPL reports that the module files were not found on the source device.
Cause: The BDMA module files (.irx driver pair for the chosen variant) are missing from or in the wrong location on the source device. RiptOPL does not embed these files — you supply them from the release's POPS/ folder.
Locate the module files
The BDMA module files ship inside the RiptOPL release archive. Find the POPS/ folder in the release zip — it contains the driver variants for each equip mode (e.g. the .ata files for the HDD exFAT variant, equivalent sets for USB exFAT and MX4SIO exFAT).
Copy them to the correct location
Place the module files in a POPS/ folder at the root of whichever device you have set as the BDMA Source — USB, MX4SIO, MMCE, or Internal HDD. The path must be exactly:
POPS/ ← folder at device root POPSTARTER.ELF <module files for your chosen variant>
Note: the source must match the device's driver
RiptOPL resolves the BDMA Source by its block-device driver, not by scanning the whole massN: namespace. A USB source reads only from slots whose driver is usb; MX4SIO reads only mx4sio slots; Internal HDD reads only the ata (exFAT) HDD. So if your POPS/ module folder sits on the internal HDD but the source is set to USB, the files will not be found — set the source to match the driver of the device the files actually live on.
Re-apply the equip
With the files in place, open VCD Settings from the main menu — BDMA has its own page, it is not under General Settings — set BDMA Source / BDMA Mode, and save. (The two manual pickers are hidden while VCD BDMA Apply on Launch is ON, because that option equips automatically; turn it off to set them by hand.) RiptOPL will copy the modules to mc?:/POPSTARTER/ and record the equipped state in a marker file (compatible with POPSLoader).
What exactly does "equipping" BDMA do?
POPSTARTER's stock driver reads FAT32. To boot PS1 games from an exFAT volume, POPSTARTER needs extra block-device modules. When you change BDMA Mode or Source and save, RiptOPL copies the chosen variant's .irx driver pair from your source device's POPS/ folder to mc?:/POPSTARTER/. On the next PS1 launch POPSTARTER finds and loads those modules from the memory card, giving it access to the exFAT volume. Setting BDMA Mode back to USB (FAT32) removes the exFAT modules so POPSTARTER falls back to its built-in FAT32 driver. SMB is excluded because it is network-only and has no block device to equip.
PS1 / VCD list not showing after a settings change
Symptom: You have VCD files on a device but after changing a setting (such as Default game view, enabling a device, or changing BDMA settings) the VCD list is empty or appears to be stuck on the disc list.
Fix: The view state sometimes needs a manual refresh after a settings change.
- Navigate to the device page that should show your VCDs and press L3 to toggle the view. If the view was already on VCDs it will switch to discs; press L3 again to return to VCDs. This forces a list refresh.
- If Default game view is set to ISO, the VCD toggle is disabled by design — L3 does nothing. Change Default game view to Both or VCD in Settings → Display Settings, then save and re-enter the device page.
- If the VCD list still appears empty, confirm the
*.VCDfiles are in aPOPS/folder at the device root (USB / MMCE / MX4SIO / iLink / SMB) or, for the internal APA HDD, inside the correct__.POPS/__.POPS0–__.POPS9partitions. Files in any other location are not scanned. - For exFAT HDD, confirm HDD (GPT/MBR) is enabled in Device Settings and that the HDD has mounted — the game list should show an HDD Games entry. VCDs on the exFAT HDD live in
massN:/POPS/.
Quick-reference button combos
| Problem | Boot combo | Effect |
|---|---|---|
| Freeze on logo / grey screen (bad config) | START |
Skips config load; boots with defaults |
| Blank / black screen (unsupported video mode) | Triangle + Cross |
Forces the safe 480p video mode |
| GSM override locked display | Triangle + Cross |
Forces the safe 480p video mode |