Skip to content

Documentation Index

NathanNeurotic (Ripto) edited this page Oct 31, 2026 · 11 revisions

RiptOPL documentation

Current comparison: Full ecosystem fork-gap refresh - October 29, 2026 (301 provenance records; 152 stable families). Source/branch/release evidence and console acceptance are recorded separately.

Start with installation and first boot and your first game. The website provides searchable task guides. Use the references below for implementation details, exact limits and contributor workflows.

Installation and troubleshooting

Task Reference
Choose an edition, configuration or package Release reference · Build configurations
Test a PR artifact or collect freeze diagnostics Test builds
Understand defaults and saved settings Fresh-start defaults
Diagnose setup or a failed launch Setup questions · Troubleshooting
Separate package, core, transport and launch-stage failures Launch diagnostics
Recover a failed VMC creation VMC creation and recovery · Automatic VMC
Copy, move or delete files, back up saves as PSU File Manager
Diagnose an APA disk without formatting it APA safety · Recovery tool

Sources and game cores

Topic Reference
Game image formats ISO, ZSO, CHD, CSO and server decoding · Compressed images
USB, MX4SIO and iLink Device setup · MX4SIO launch notes
MMCE MMCE setup
Internal HDD APA/exFAT guide · exFAT and APA-Jail
SMB / UDPFS / UDPBD SMB · Network boot
HTTP HTTP profile and limits · Host conformance tools
Neutrino Installation, core selection, arguments, cheats and VMC
PS1 POPSTARTER and Ember, including POPS UDPFS and device/core restrictions
RetroAchievements RA setup and runtime limits; requires its separate kit
Experimental hardware PC CARD CF · PSX DESR DVR

Settings and customization

Migration and history

ps2build migration, the C++ conversion plan and the parity ledger record how RiptOPL tracks Open-PS2-Loader. Fork-gap status: 2026-10-28 is the current summary: parity with the legacy edition, fixes landed in both, the RIPPS2 audit and port plan, and the open hardware checks. Learning across PS2 loader projects says what evidence a candidate from another fork needs before it is ported, and Maintaining documentation says where each page of the website, wiki and these references is edited and how the wiki is rebuilt.

Integration plans, dated audits and community-report handoffs are engineering history. Their old DONE/pending states, branches and package names describe that baseline; they are not current installation instructions. Historical records: gap ledger, community reports, contributor roadmap, Ember plan, HTTP plan, RA plan, VMC audit and legacy changelog.


Source: docs/README.md @ 6bab0a0257c0.

RiptOPL Wiki

Start here

Storage and networking

Games and features

Interface and customization

Help and reference

Detailed references

Wiki maintenance

Clone this wiki locally