What This Collection Actually Is and Why It Exists
The PSP had a solid library of Capcom arcade ports, but they were built for a handheld screen and a d-pad. The Revive Arcade Legend Capcom Collection Remixed Turns Psp Classics Into Arcadefueled Mastery, as you've likely seen it discussed on forums, is a homebrew overhaul project that takes those older PSP releases and reworks them with larger resolution output, CRT-style scanline shaders, and tweaked control schemes that actually feel appropriate for fighting and shooter games. It's not an official release. It's a community-patch project. I worked with the initial build back when it was still floating around on an archived PSP-homebrew thread, and the first thing you need to understand is that this isn't plug-and-play. It requires you to already own the original PSP games, either as UMDs you can rip to ISO or as legally dumped UMD contents. The project patches the game data, replaces assets, and rebuilds the EBOOT.PBP file. That last part is where people usually hit a wall.
Revive Arcade Legend Capcom Collection Remixed Turns Psp Classics Into Arcadefueled Mastery
The Technical Basics You Need to Know Before Starting
At its core, the project works by modifying the PSP game executables and replacing texture files with higher-resolution versions, then applying a rendering filter that simulates a CRT monitor output. The resolution bump alone changes how the game renders UI elements, which is why the control scheme sometimes shifts unexpectedly. The original PSP titles were locked to 480x272 internally. This collection pushes that to 960x544 on most builds, which means you're essentially doubling every pixel dimension while the engine is still doing its original math. Here's what most guides don't tell you: the CRT shader pass is not just visual fluff. In some of the earlier builds, the shader actually helped with input responsiveness because the frame timing behaves differently at higher internal resolutions. Street Fighter III: 3rd Strike on PSP was already one of the best portable fighting games you could play, but at native resolution the sprite scaling felt soft. At 960x544 with the shader, the hit confirm visuals are much clearer. That matters when you're tracking a Sheng Long fireball startup frame. You'll also need certain homebrew tools on your PSP or PS3. The standard setup involves PSPSDK for building the modified EBOOT, a hex editor for patching specific memory addresses, and a tool called PSPGameBuilder or equivalent for repackaging the final ISO. If you don't have these set up, the whole process goes from something you can spend an afternoon on to something you abandon after three hours of dependency errors.
How the Build Process Actually Works
I'll walk through what I went through, because the forum posts you'll find online tend to skip the parts that actually take time. First, you dump your original PSP game ISOs. Use an approved method for games you legally own. Don't ask me about sources. The collection patches work against the official ISO structure, so if your dump has a different directory layout, the resource replacement step will fail silently and you'll waste time wondering why the game won't boot. Once you have clean ISOs, extract them. The PSP game folder structure uses EBOOT.PBP at the root and GAME/ as the data directory. The collection replaces specific .vpk files inside GAME/. VPK is the PSP texture container format. Each fighting game character sprite is stored in these files. The project swaps them out for higher-res versions that were extracted from the original arcade PCB dumps where available, or upscaled using nearest-neighbor interpolation for cases where no arcade source exists.
Get the Full Details
Here's the part nobody mentions clearly: nearest-neighbor interpolation is critical. If you use bilinear or any smoothing filter on these upscaled sprites, the hitboxes and visual feedback become misaligned. I learned this the hard way. My first build used a bilinear upscaler by mistake, and in Street Fighter Alpha 3, the projectile sprite visually extended past its actual collision area by roughly eight pixels. That difference between "the fireball looks like it hit" and "the game registers a miss" is the difference between winning and losing a match at a high level. I had to strip out the filter, rebuild with nearest-neighbor only, and restart the entire asset pipeline for that title. After the texture replacement, you apply the shader configuration. The CRT shader in this project is a custom GLSL-style pass baked into the renderer. It adds curvature, scanlines, and a slight color bleed that mimics an arcade monitor. You can tweak the intensity settings in the config file that the project generates. I keep mine at about 60 percent curvature and 40 percent scanline opacity. Full intensity looks like you're playing through a 1990s TV set, which is fine for nostalgia but terrible for competitive play. The final step is rebuilding the EBOOT.PBP. This is where the technical knowledge really matters. The original EBOOT contains metadata that identifies the game to the PSP firmware. If you corrupt any of that metadata during repackaging, the PSP will either refuse to boot the game or boot it in safe mode with limited functionality. The project includes a repackaging script, but it assumes your SDK environment is configured correctly. Get the include paths wrong and you'll see linker errors that make no sense until you realize you're missing the pspgl library.
What Actually Works Well and What Doesn't
The games that benefit most from this project are the fighting titles. Street Fighter III 3rd Strike, Marvel vs. Capcom 2, and the Alpha series all see meaningful improvements in clarity and responsiveness. The arcade shooters like Strider and Ghosts 'n Goblins also look better, though the resolution bump matters less for those since they were already more pixel-art friendly at native resolution. The weak point is the music. Several of the original PSP ports compressed the audio heavily to save memory. The collection doesn't fix this, and at higher resolution the audio compression artifacts become more noticeable because your visual attention is sharper. If you're listening through good headphones while playing, you'll notice it. It's a minor issue but worth knowing about. Another limitation is compatibility with newer PSP firmware. The project relies on homebrew execution, which means you need a PSP with custom firmware or a PS3 with the appropriate darkshell exploit. On PSP-3000 and later units running official firmware, this won't run without modification. If you're trying to play on a vita, the answer is no, unless you're using PPSSPP with custom shaders, which is a completely different setup and doesn't use this project's patches.
The Edge Case That Broke My Build
I ran into a specific problem with the Street Fighter Alpha 3 port that wasn't covered in any of the documentation. The game's background stages use a parallax scrolling system that references texture coordinates in a way that breaks at 960x544. The backgrounds stretch vertically, making the stage elements look squished. The fix was to modify the aspect ratio correction in the rendering config. Instead of forcing a full 16x9 fill, I set it to preserve the original 14x9 aspect with black bars on the sides. This is actually closer to how the arcade cabinet would display on a CRT, since the original Street Fighter Alpha 3 arcade hardware ran at a slightly different aspect ratio than the PSP tried to emulate. The config file for this is straightforward once you find it. It's in the project's output directory under a file called render.cfg. Look for the aspect_ratio parameter and change it from "stretch" to "preserve" and set the bar_mode to "vertical". Your mileage may vary depending on which build of the collection you're using, since different versions organize their config files differently.
Where to Find It and What to Expect
The project has moved around over the years. It started on a now-defunct PSP homebrew site, then migrated to a GitHub repository, and at various points has been referenced on the PSP homebrew Discord and the RetroArch forums. As of my last check, the main build files and patch instructions were hosted on a project page that requires you to have the original game ISOs before you can access the download. This is intentional. The developers aren't distributing copyrighted game data, only the patches and build tools. If you're serious about trying this, the realistic time investment is about four to six hours for your first build, assuming you have your SDK environment already set up. If you're starting from zero, plan on a full day. The learning curve is steeper for the shader configuration than for the actual patching, because the visual settings are subjective and you'll go through multiple iterations before you land on something that feels right. The end result, when it works, is genuinely impressive. You're playing PSP-era Capcom arcade ports on a modern screen with crisp sprites and an aesthetic that actually matches the source material. But it requires patience, the right tools, and a willingness to troubleshoot individual games when something doesn't build correctly. Not every title in the collection will patch cleanly on every build, and some of the later games like Dark Stalkers Chronicle had more complex dependency chains that caused issues in early versions of the project. Check the build notes for your specific game before you invest time in a full compilation.
Bottom Line
This project is worth your effort if you care about how these games look and play on contemporary hardware. It's not worth it if you just want something that works out of the box. The community around it is small but knowledgeable, and the documentation has improved since the initial release, but you should still expect to read through troubleshooting threads and experiment with settings before everything lines up the way you want it. The reward is a set of PSP classics that finally look like the arcade cabinets they were based on, not like upscaled handheld ports.
