A major graphics rewrite arrives on Android
ARMSX3 1.5, released under the build tag 1.5 on October 29, 2026, brings RPCS3’s redesigned RSX emulation to the Android PlayStation 3 emulator. The RSX is the PS3’s graphics processor, so this change affects the part of the emulator responsible for processing game graphics and presenting frames on the device.
The new RSX implementation was developed for RPCS3 by kd-11 after about two years of work. The release notes describe 88 changes and more than 13,000 lines of code in the upstream rewrite, which ARMSX3 now uses as part of its core. This puts ARMSX3 back on the same graphics design as current RPCS3 development, allowing future graphics fixes built for that architecture to flow into the Android project.
A cleaner model of the PS3 graphics hardware
The previous RSX implementation concentrated much of its functionality in one large component. The redesigned version separates the graphics command processor, display handling, and renderer into distinct parts. In practical terms, the emulator can handle the stream of commands sent by a game, manage frames and timing, and draw through Vulkan or OpenGL without keeping all of those responsibilities tangled together.
The new structure also separates the state seen by the emulated PS3 from the state used by the Android device’s actual graphics driver. That distinction gives the emulator a clearer way to represent what the game believes the RSX is doing while independently managing how the phone or tablet renders the result.
The core follows the RSX command processor more closely and incorporates community documentation of the underlying NVIDIA hardware. It also keeps hardware state and software state apart, allowing multiple graphics contexts to exist at the same time. These changes are intended to make the emulation model more faithful and provide a stronger foundation for future graphics work.
Renderer changes are safer on mobile
The redesigned graphics system supports changing renderers while a game is running on the desktop version of RPCS3, including switching between Vulkan and OpenGL or restarting after a graphics-driver crash. ARMSX3 applies that idea more cautiously on mobile: renderer and driver changes take effect through Apply & Restart, and a GPU crash closes the game cleanly instead of attempting a risky in-session recovery.
The release carries over ARMSX3’s existing graphics work into the new core, including frame generation, remote play, custom-driver support such as Turnip, Multithreaded RSX, frame pacing, and earlier Adreno and Mali fixes. These features remain part of the Android project while the underlying graphics implementation changes.
Savestates from 1.4.x are not compatible
The RSX rewrite changes how graphics-chip state is stored, so savestates created with ARMSX3 1.4.x cannot be loaded in version 1.5. Users should make a regular in-game save before updating rather than relying on an older emulator state.
ARMSX3 now reports the incompatibility when an old savestate is selected. If that happens while a game is running, the game continues instead of hanging while attempting to load the incompatible state. This improves the failure behavior, but it does not convert existing 1.4.x savestates for use in 1.5.
Bundled fixes are enabled by default
Game-specific fixes bundled with ARMSX3 now activate for all users without requiring a separate patch-database download first. The release specifically mentions freeze-fix patches for Ratchet & Clank along with fixes for Burnout Paradise, J-Stars, Splatterhouse, and Skylanders: Spyro’s Adventure, among others.
WET also now boots and plays according to the release notes. That is a documented title-specific change rather than a general compatibility guarantee for the PS3 library, so results can still vary between games and Android hardware.
OpenGL becomes a usable fallback
ARMSX3 1.5 adds a functioning OpenGL renderer as a second graphics option. The setting was previously present without an implemented renderer; it can now use the device’s own OpenGL driver or ANGLE through the OpenGL Driver setting. ANGLE draws through Vulkan and may avoid driver problems on some Mali and other non-Adreno graphics processors.
The project positions OpenGL as a fallback rather than the preferred option. The release notes state that it is slower than Vulkan, while Vulkan with a suitable custom driver remains the recommended configuration for ARMSX3. OpenGL and ANGLE nevertheless give users another path when Vulkan drivers produce rendering problems or do not behave well with a particular device.
More useful session diagnostics
The Android app’s logs now record how the previous session ended. Entries can distinguish a normal close, a crash, or Android stopping the process to reclaim memory. That information should make it easier to interpret a failed session and separate an emulator crash from the operating system terminating the app under memory pressure.
