Skip to content

v0.1.3 — safer screenshot default (no more PPSSPP crashes)

Choose a tag to compare

@dmang-dev dmang-dev released this 16 May 20:37
· 66 commits to main since this release

Real PPSSPP crash observed when calling gpu.buffer.screenshot on a homebrew game. Root cause is upstream — _assert_(buf != nullptr) in PPSSPP's GPUBufferSubscriber.cpp fires when GPU_GetOutputFramebuffer returns true with a null buffer. The process aborts; uncatchable from outside.

Changed

  • ppsspp_screenshot now defaults to gpu.buffer.renderColor (reads the active GPU render target via GPU_GetCurrentFramebuffer(RENDER)) instead of gpu.buffer.screenshot (which reads PPSSPP's final composited output via the crash-prone GPU_GetOutputFramebuffer). The render target is the actual rendered scene at PSP-native 480x272, before PPSSPP's post-processing. For agent-vision use cases this is identical content.
  • New source parameter (enum 'render' | 'output', default 'render') lets callers opt into the post-processed gpu.buffer.screenshot path when needed. The tool description carries a clear warning that 'output' can crash PPSSPP on certain games.

Known limitations

  • source: 'output' can still crash PPSSPP — upstream bug. v0.1.2's auto-reconnect ensures MCP recovers cleanly when PPSSPP is relaunched. Will be tracked upstream at hrydgard/ppsspp.

Install: npm install -g mcp-ppsspp@0.1.3 or npx -y mcp-ppsspp

Full Changelog: https://github.com/dmang-dev/mcp-ppsspp/blob/v0.1.3/CHANGELOG.md