PlayStation

The PlayStation is the platform that best shows what RetroXR does with saves. Your save is not a hidden file in a folder — it is on a memory card, and the card is an object you hold, slot in, and can lose.

Before anything: the BIOS

The PlayStation will not boot without its BIOS, and RetroXR cannot ship it. Open CORES → BIOS / Extras and pick PlayStation to see exactly which files it wants.

The filenames have to match exactly — scph5500.bin, scph5501.bin, scph5502.bin and psxonpsp660.bin. A file that is right in every way except its name will not be found.

If you run a RomM server holding your firmware, RetroXR can pull these down directly. Otherwise copy them in the usual way — see adding your games and BIOS files.

Memory cards

A memory card. Slot it into the console's card port; your saves live on it, not in a folder.

① The connector edge goes into the console’s card slot. ② The label names the card, which is how you tell two of them apart on a shelf.

Using one

1. Spawn a memory card from SPAWN → Objects.

2. Push it into one of the console’s two card slots.

3. Play. The game saves to that card, in that slot.

Because a card is a real object rather than a setting, the things you could do with a real one work here:

• Keep several saves on one card, until it runs out of blocks.
• Move a save from one card to another.
• Delete a save to free blocks.
• Back a card up to your RomM server.

There is a manager for all of this, reachable from the card itself: point at it and press the menu button.

If a game cannot find your save

Saves are per card, and per slot. The usual cause is a different card in the slot, or the right card in the wrong slot. Check the card before suspecting the emulator.

You cannot delete a save while the console is on

Power the machine down first. It is the same rule cartridge saves follow — see game saves and backups.

Backing a card up to RomM

A card you can lose is a card worth backing up, and this is the reason to connect a RomM server even if you copy your games across by hand.

1. Connect RomM.

2. Back the card up from its own manager.

3. The card’s contents live on your server, not only on the headset.

That matters more here than for most saves: on a Quest you cannot safely copy save files back in from a PC — files pushed from a computer land owned by the shell rather than the app, and RetroXR can no longer write to them. RomM is the route that avoids the problem entirely.

Full detail on game saves and backups.

Discs

Spawn a game from SPAWN → Cartridges and it arrives as a disc rather than a cartridge. Open the console’s lid, set the disc in the tray, close it, and power on.

Multi-disc games work — RetroXR retrieves the right image for each disc rather than handing every disc the first one, which was a real bug fixed in v0.3.0.

A procedural stand-in

The PlayStation is one of the machines wearing a clean procedural stand-in rather than a detailed replica — fully playable, deliberately minimalist, like most of the hardware in the room. The memory cards above are the exception, and they are in.

Controllers

Plug a pad into one of the two controller ports. For a real gamepad, spawn a Controller Receiver and plug that in instead — see controllers and peripherals.

Cores

The PlayStation has several libretro cores with different accuracy and speed trade-offs. Pick the default in CORES → Manager — see downloading and managing cores.

Needs an in-headset pass

The memory card manager’s exact controls, and the lid and tray interaction, are written from the code and the v0.3.0 release notes rather than from a session in the headset.