You need to have your PSP games as .CSO or .ISO files. I do not have the right to distribute those with the app, so you'll have to provide them on your own. To convert your real PSP games for use with PPSSPP, you need to install a "Custom Firmware" on your PSP. Google for that. Then follow these steps:
There are tools to turn ISO files into CSO (compressed ISO) files to save space, such as maxcso by [Unknown].
If you have digital downloads on your real PSP, they can be used directly on PPSSPP. Just copy the EBOOT.PBP over. Note that this has not been tested as much as ISO loading so there may still be issues with some games.
PPSSPP can run on most modern iOS versions. On some versions, the JIT works. See the Downloads page for more info.
Install it exactly the same way as you would on a PSP, that is, copy the files to PSP/GAME or PSP/SAVEDATA (depending on the DLC) on the memory stick. In the Android version of PPSSPP, the memory stick is simply the SD card or USB storage of your phone, PPSSPP will create a PSP folder in the root of that. On Windows without installer, the memory stick is the "memstick" subdirectory in the PPSSPP folder. On iOS, it's in /User/Documents/PSP/ . On Mac and Linux, it's in ~/.config/PPSSPP.
No. PSP Vita is a completely different machine, far more powerful than the PSP and with different security technologies. I don't have neither the information needed nor the time.
No. PPSSPP simulates the BIOS and the internal OS. It does not currently emulate enough of the hardware for the actual PSP operating system to run, so even if you have a copy of it, PPSSPP can't run it.
Why not? The domain name ppsspp.org was available, unlike the corresponding domains for many other alternatives I considered. Today I probably would have named it something different and more memorable.
Contact me at [email protected] and I'll set you up.
Yes, PPSSPP has built-in XInput and DirectInput support on Windows so it will "just work" with any Xbox 360 pad and most other pads that you plug into your PC.
On Android, many Bluetooth gamepads like iPega Red Knight work just fine, sometimes with a few limitations.
Yes, although it's not a super smooth experience. Follow this:
Disabling savestate backups will make save/load faster, but also disables save/load undo.
Sharing controls between the two instances can be an issue though..
Any reasonably modern CPU will be just fine, and any GPU that can handle OpenGL 2.0 should have no issues. You should make sure to install the latest graphics drivers available though. Windows Vista or later is required, Windows 7 or higher is recommended. Vulkan will likely help performance where available, also try D3D9 or D3D11 if OpenGL is slow by changing the backend in settings. On some older computers, you may need to use the D3D9 backend.
CSO are compressed ISO files that can be played directly, decompressing on the fly. Very useful to save space on your Android device, for example. MaxCSO is a great program to create CSO files. Of course, there are others around the web, too.
You can either help out with fixing it, or wait until someone does.
To emulate advanced systems like the PSP fast, the emulator needs to translate the machine code language of the PSP to the machine code language of your PC or mobile device at runtime. This is done with a "Just-In-Time recompiler" or JIT, also known as a Dynarec. PPSSPP has JITs for x86 and ARM, 32-bit and 64-bit.
For a JIT to function, an app needs to have the ability to generate machine code at runtime. This is allowed on Windows, Mac, Linux and Android, while it is disallowed on many versions of iOS.
Chromebooks can run the Android version of PPSSPP. However it has not yet been adapted for keyboard input, so you'll want to use an external bluetooth controller for now.
First, make sure you have charged it to the max once. If you don't, the normal Android mode will not work!
Then, just flip the power switch to on, and press Home+X to start it in Android mode. After that, things should just work! You may want to tweak the controls a little bit in Control Mapping but the defaults are mostly okay.
Apparently, accessibility options can interfere with joystick functionality. Try turning any accessibility settings off in Android settings. This behavior has been seen on Google Pixel phones.
It seems like apps like Quick Cursor that draw over other apps can also cause this, by seemingly taking over joystick input.
The bug has been reported to Google, still no fix: issue report
Shoot me an e-mail (hrydgard at gmail dot com) and I'll remove it.