ARMSX2 2.9.5 is available

ARMSX2 2.9.5 was released on November 16, 2026, with changes focused on memory-card reliability, Vulkan rendering, Android stability, and Linux display behavior. The update is available as Android APKs and Linux ARM64 AppImages, with separate packages for 4K- and 16K-page systems on Linux.

ARMSX2 is a PlayStation 2 emulator based on PCSX2. It uses ARM64 recompilers, interpreters, and a virtual machine to reproduce PS2 hardware behavior on supported phones, computers, and gaming handhelds. A BIOS dump from a legitimately owned PS2 is required to use the emulator.

Folder memory cards now protect complete saves

The most important change in 2.9.5 affects memory cards configured as Folder. Each save is now written as a complete unit, preventing a timing problem in which the save data could reach storage before its file entry. If the application was closed immediately afterward, the game could later see a blank save or an older version. The new behavior prevents that mismatch.

The update also keeps a newly created save’s own filename when it reuses space from a deleted save. Previously, that situation could make the new save appear under the deleted save’s name. A save file that the device cannot open for writing can still be read instead of being presented to the game as damaged.

On Android storage locations that require the operating system’s file-access mechanism, new saves are created correctly when the IOP thread is enabled. ARMSX2 also avoids rewriting a folder memory card when nothing changed after the application is closed, reducing unnecessary storage activity.

Samurai Warriors 2 and IOP-thread save loading

Save loading for Samurai Warriors 2 has been corrected when the IOP thread is enabled. A valid save could previously be reported as damaged in that configuration; 2.9.5 allows the game to load it correctly.

The release also fixes restarted transfers between the PS2’s Emotion Engine and I/O Processor when the IOP thread is active. A restarted transfer could leave the IOP with stale data and stop with a “SIF1 Overrun” error. The corrected transfer handling supplies the new data instead.

Rendering and performance changes

ARMSX2 extends the Vulkan draw-batching work introduced in version 2.9.4 to the Minimum blending mode. The release notes use Spider-Man 3 as an example: a scene produced about 3,960 draws per frame with Minimum blending, compared with 92 at Basic blending. The project’s stated goal is to bring comparable batching to Minimum blending, reducing the amount of work submitted to the graphics driver in affected scenes.

Beyond Good & Evil receives a specific optimization for its water. The game produces roughly 285 alpha-tested water draws per frame. ARMSX2 can now test alpha in the shader rather than breaking the render pass for every draw, while later draws in the same pass share a screen copy. Alpha values known to fall inside letterboxed regions can also avoid an unnecessary screen read.

The optimized build’s performance profile was retrained using the 2.9.5 code across the same 16 games used for the preceding profile. This updates the optimized-build profile to match the current code, but the release notes do not provide a general performance guarantee.

Beyond Good & Evil water now renders correctly

The hardware renderers no longer show the lake and sea in Beyond Good & Evil as red. The release also adjusts sprites drawn on texel edges so their coordinates follow the PS2’s own stepping behavior, placing the water’s stipple pattern correctly.

Both retail releases listed in the game database, SLUS-20763 and SLES-51917, are assigned High blending. Together, these changes address the color, stippling, and game-configuration issues called out for the title in this release.

More consistent Android graphics behavior

Batched draws on Turnip-based Adreno graphics drivers now sample their textures consistently. Spider-Man 3’s lighting could change between runs at Minimum and Basic blending because batched draws did not use the same texture-sampling behavior. The fix is intended to make the result repeatable across runs.

The Spin GPU For Readbacks option now works on Turnip and MaliSX2 instead of closing the application when enabled. On Mali GPUs, the option remains disabled because the release notes report no benefit there.

Returning to a game after a settings screen covers it, or after the application has been in the background, no longer closes the app when a setting causes the renderer to reopen. This addresses a crash during that transition.

The release also corrects the problem-report consent text so that it states the actual 14-day retention period.

Linux display fix and package choices

On Linux, reopening the Vulkan renderer while the game list is covering a running game no longer leaves the display blank until a restart. This fixes the reported blank-screen state when the game list covers an active game.

The release provides Linux ARM64 AppImages for both 4K-page and 16K-page systems. Android users can choose packages targeting different ARMv8.2 instruction levels: the A11, A13, and A15 builds require newer ARMv8.2 processor features, including dot product support. If ARMSX2 reports that the device cannot run those packages, the legacy APK ending in “-sdk26” is the alternative for supported devices.

ARMSX2 editorial illustration
AI-generated editorial illustration; not an application screenshot.