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.
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 resets the saved video mode to Auto without touching any other settings.
Verify the display returns
Start OPL normally (without holding buttons). If the interface is now visible, the forced video mode has been cleared. Open Settings → Video and leave it on Auto unless you have a specific reason to force a mode.
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, or MMCE. The path must be exactly:
POPS/ ← folder at device root POPSTARTER.ELF <module files for your chosen variant>
Note: USB source scans the whole mass namespace
When BDMA Source is set to USB, RiptOPL scans the entire BDM massN: namespace — this includes USB drives, MX4SIO, and the internal exFAT HDD (if BDM HDD is enabled in Device Settings). So if the only drive currently connected with a POPS/ folder is the internal HDD, the USB source setting will still find the files there.
Re-apply the equip
With the files in place, go to Settings → General Settings → BDMA Mode / BDMA Source, set your desired values, and save. 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 |
Resets saved video mode to Auto |
| GSM override locked display | Triangle + Cross |
Resets saved video mode to Auto |