A more practical GTA IV configuration
ARMSX3 is an Android emulator for PlayStation 3 software, built around the upstream RPCS3 codebase and its ARM64 work. Version 1.1.2 focuses heavily on making Grand Theft Auto IV more usable on supported Android hardware, while also improving general rendering performance and developer diagnostics.
The release adds a built-in patch that prevents GTA IV from falling through the world when SPU XFloat Accuracy is set to Approximate. Approximate mode uses less CPU than Accurate mode, so the affected game versions can now use the faster setting by default when the patch is enabled automatically.
Automatic activation applies to BLUS30682 v1.02, the Complete Edition containing both episodes, and BLUS30127 or NPUB30702 v1.08. Older game versions may still require Accurate mode, and the release notes state that the base 1.0 version does not work with RPCS3. These version distinctions matter: the patch is not presented as a universal solution for every GTA IV release.
Rendering and performance fixes
GTA IV also benefits from a fix for the grey, semi-transparent rectangle that could appear during daytime scenes. The same correction applies to other games that left stale blocks on screen, making it a broader rendering fix rather than a GTA IV-only change.
The release also changes how games using Multithreaded RSX handle their helper thread. They no longer stall while waiting for that thread to complete. RPCS3’s game database enables the setting for around 170 games, so the change can benefit titles beyond the examples highlighted in the release notes.
For GTA IV specifically, the project reports a frame-rate change from approximately 16–18 frames per second to 25–30 frames per second on an Odin 3. That is a project-reported result rather than a guarantee for every Android device. The notes characterize the game as playable on devices using Snapdragon 8 Elite and newer hardware, with performance described as comparable to original PlayStation 3 behavior, including frame drops. Actual results will depend on the device, game version and configuration.
Broader built-in patch coverage
Built-in patches that apply to multiple versions of the same game now activate across all of their listed versions. Previously, only the final version in a patch entry received the fix, leaving earlier entries without the intended behavior.
The release specifically calls out the US version of Splatterhouse, the European version of Killzone 3 and several Ratchet & Clank versions as examples that were previously missed. This should reduce the need to manually identify a particular regional or revision-specific patch entry when a supported fix is already included.
Small controller improvement
Navigation in settings receives a focused usability correction. When a prompt is open, pressing the D-pad now keeps the selection inside that prompt instead of moving to the setting behind it. The change should make confirmation dialogs and similar controls less confusing when operated with a gamepad.
New tools for RSX capture work
Version 1.1.2 adds several tools for developers and graphics investigators. Under Settings, Advanced, Developer tools, Replay a capture can play back a frame recorded with Capture RSX frame. Replay also supports captures made on another device when the .rrc.gz file is placed in the config/captures directory.
The release attributes a memory fix required for replaying captures to upstream RPCS3 contributor @elad335. This makes captured rendering data more useful for comparing behavior across devices or examining a graphics problem away from the original Android hardware.
A new Dump this frame option appears in the in-game menu beneath Capture RSX frame. It saves the next frame as image data in config/captures. Users can choose whether to save the completed image or every render pass through Settings, Advanced, Developer tools, providing either a finished frame or more detailed information for investigating the rendering pipeline.
Capture RSX frame itself no longer leaves the game paused. The game continues running, and a message identifies where the capture was saved. That makes the function less disruptive during testing while providing clearer confirmation that the capture completed.
Android package options and documented requirements
ARMSX3 1.1.2 is distributed as Android APK packages for several ARM64 configurations: armv8.2 builds targeting Android SDK levels 30, 33 and 35, plus a legacy armv8.1 package targeting SDK level 30. The package names identify the intended Android target, so users should select the package appropriate for their device.
Running ARMSX3 requires PlayStation 3 firmware, which is not included with the project. The project is licensed under GPL-2.0-only, following RPCS3, although individual files may carry different licenses.
The supplied release includes packaged APKs. The repository’s build instructions are relevant to people compiling ARMSX3 themselves rather than a requirement to use those packages. The README identifies arm64-v8a and armv8.2 support and explains that ARMSX3 incorporates recent upstream RPCS3 ARM64 improvements.
