PSPC

Help

Troubleshooting

Fixes for the problems people run into most, and how to report the ones that remain so they can be fixed.

Installing

Windows says it protected my PC

The installer isn't code-signed yet, so SmartScreen warns about an unknown publisher. Choose More info, then Run anyway. To be sure the file is the real one, check its SHA-256 checksum: see Install PSPC.

“Python is missing” when building native code

Native code builds and the servers run on the Python that comes with PSPC, in its python folder. PSPC couldn't find it, or any other Python 3.9 or later. Open the installer again to repair or reinstall PSPC; your settings and saves stay.

Games

A game doesn't appear in the library

  • Check that it is in the Games folder, or in the folder you chose, and press F5.
  • The library shows ISO, CSO, ZSO and DAX images and EBOOT.PBP files. Other formats, and archives such as ZIP or 7z, need converting or unpacking first.
  • An image that isn't a valid PSP disc is skipped. A damaged or incomplete dump can cause that.

A game runs slowly

  • Is its native code built? Without a NATIVE tag, some or all of it runs in the interpreter, which is much slower. Build it, or rebuild it if it says REBUILD or PARTIAL: see What the tags mean.
  • Lower the resolution. With Direct3D 11 at high settings, the graphics card may be the limit: 8× draws 64 times the pixels of 1×.
  • Some games are slow anyway, for now. Syphon Filter: Logan's Shadow's missions run at about half real time, because of the work its 3D graphics take. The compatibility notes list such cases.

Some of the game's text is missing

The game draws that text with the PSP's system fonts, which PSPC doesn't include. Install Sony's 4.01 update through Firmware Manager > Build from update…, or copy a compatible PGF font set into the active profile's firmware\<name>\flash0\font folder: see Fonts without the XMB.

A game freezes, crashes or won't start

  1. Try the interpreter. Right-click the game and choose Play in the interpreter. If it works there, the problem is in the native code: try Rebuild, and report it if that doesn't help.
  2. Rule out plugins. Turn plugins off in the Plugins window, or run with --no-plugins.
  3. Check the firmware version. If you changed Firmware version in Settings, set it back to 6.60: a game that needs a newer version than PSPC reports refuses to start.
  4. Still stuck? Report it, with a log.

The native code build fails

The build window shows what went wrong; keep it open and copy its text. Choosing Yes to “Play anyway?” runs the modules that didn't build in the interpreter. Please report the failure with the window's output and the game's disc ID.

I updated PSPC and my games say REBUILD

That is expected when the update changes PSPC's instruction semantics. The same tag can mean a run found usable code the build missed; the panel explains which. Click Rebuild, or just Play and accept the rebuild. v0.1.2 fixes prompts after every session; games already marked REBUILD may need one last rebuild after updating.

Graphics, sound and controls

Something looks wrong with Direct3D 11

Switch the renderer to Software (accurate) and look again. If it is right there, it is a GPU renderer bug: please report it with a screenshot (F12) from each renderer. Turning texture upscaling off is also worth a try.

I chose Direct3D 11, but nothing changed

Your graphics card or driver may lack Direct3D 11.3 rasterizer-ordered views, which PSPC's GPU renderer needs. PSPC then uses the software renderer and notes it in the log: run the game with --log-file run.log and look for “D3D11 renderer unavailable”. Updating your graphics driver can help.

A key or controller button does nothing

  • Check the Controls list in Settings, or choose Reset controls to defaults.
  • F11 and F12 are always fullscreen and screenshot; they can't be game controls.
  • For the analog stick, check that pad.stick in pspc.ini isn't none.
  • Settings apply when a game starts: restart the game after changing them.

There's no sound

Check Volume and Mute in Settings, and that pspc.ini doesn't say mute=1 or volume=0.

Online

The game says it can't reach its server

  • Combat Ops, Elite Squadron and Super Squadron have built-in server support. Super Squadron defaults to swss.pspc.online; starting a local GameSpy server or choosing another server overrides it. For the other games, start the server you need on the Online page, or use Change… to choose someone else's.
  • In the game, choose the connection PSPC 1.
  • Check that networking isn't off: network=1 in pspc.ini.

The PSN sign-in fails

The PSPC Network server may be down, or have signed you out. Sign in again from Network at the bottom of the launcher's sidebar. Without a server, games sign in locally and always succeed.

Friends can't connect to my server

  • Allow Python and pspc.exe through Windows Firewall on private networks.
  • Give friends the address Copy address copies, not localhost.
  • Over the internet, forward the servers' ports on your router: see Playing with friends on other PCs.

Ad hoc players don't find each other

  • Everyone must use the same ad hoc server, and the server PC must use its LAN address too, not localhost.
  • Everyone needs the same region of the game: the server doesn't connect a US copy with a European one.
  • If you copied a PSPC folder between PCs, delete pspc_idstorage.txt in the copy's active firmware\<name>\flash1 folder, so the two installations stop sharing one console identity.

Firmware and the XMB

Boot XMB says the firmware isn't installed

Open Firmware Manager and choose Build from update…, name the profile and pick Sony's 4.01 update EBOOT.PBP. If you already have a profile, select it and choose Use selected. See Install the firmware and migration from older versions.

The firmware install failed

The build window stays open with the error. Check that the file is Sony's official 4.01 update and that both PSPC's folder and the temporary filesystem have at least 512 MiB free. A failed new build leaves existing profiles and the active selection unchanged. Fix the reported problem, then retry Firmware Manager > Build from update… with an unused profile name.

Select does nothing in the XMB

M33's VSH menu isn't part of Sony's update, so PSPC doesn't install it with the firmware: see M33's VSH and recovery menus.

Reporting a problem

A good report gets a problem fixed. Before opening an issue:

  1. Record a log

    From a terminal in PSPC's folder, run the game with logging to a file:

    pspc.exe --log info --log-file run.log Games\MyGame.iso

    If PSPC crashes, it prints a backtrace in the terminal, with native frames named after the game's functions. Copy that too.

  2. Try the interpreter

    Run the same with --interp and note whether the problem stays. That tells a recompiler bug from a system library bug.

  3. Write down the details

    The PSPC version (pspc.exe --version), your Windows version, your graphics card and renderer settings, the game's title and disc ID (such as ULUS10391), and exactly what you did and where it went wrong.

  4. Open an issue

    Attach the log and, if it helps, screenshots. Never attach game files, firmware or keys.