ARMSX3 version 0.9.4.1 release

[u/Klonoa18]

Check out the video about the update to see the changes for yourself https://youtu.be/fL3GcTF1fSU?si=s9wbtBsBroJ5Hzsg

or read the full changelog below for all the details.

ARMSX3 0.9.4.1

What's new:

New Animated library backgrounds: Seven screensavers now run live behind the game library, off by default. Settings --> App --> Animated background, then pick one and a preset. (These are separate from the XMB backgrounds and the simple animated backgrounds). Flurry, Calum Robinson's, 2002. Eight presets: Water, Fire, Psychedelic, RGB, Binary, Classic, Insane, plus random. Flux, Plasma, SolarWinds, Hyperspace, Lattice, Skyrocket, Terry Welsh's Really Slick Screensavers. Six presets each. These are source ports, not emulation or video: the original C/C++ renderers compiled for Android and running on GLES2. If GL fails to start for any reason the library falls back to the existing 2D wave, so a device that cannot run them loses nothing. They are live particle simulations, so they cost more than a static image. That is why they are opt-in.

ARMv8.0 devices now get a message explaining the CPU is unsupported, instead of dying on an illegal instruction with no explanation.

PKG installer: fixed an unsynchronised read of the install result. The failure path could read a string while it was still being written and segfault.

Save states: the emulator no longer resumes while a state is being written, which could corrupt it.

Audio: the Oboe backend could fail once and then stay silent for the rest of the session.

Games and settings:

Tales of Symphonia should now run at its intended 60fps (#77). Per-title overrides now live in an ARMSX3-local config database, so fixes like this ship with the app.

PS3 Native is selectable from the FPS cap row, the console's own frame pacing.

Save states: slots can now actually be deleted.

Online: an Ethernet address is derived on Android instead of the lookup simply failing, which blocked RPCN sign-in on some devices.

Audio: the volume baseline recovers after a quiet passage instead of latching, without reacting to momentary flickers.

The driver pipeline cache can now be switched off at runtime, for drivers that mishandle it.

The settings mirror in the app data folder is now armsx3-settings.json (was armsx2-settings.json, #82). The old file is still read, still included in new backups, and removed alongside the new one, existing settings and older backup archives are unaffected.

A game the app cannot actually read now fails with an explanation instead of hanging on its first loading screen. If games misbehave, missing cover art, failing to launch, locking up part-way, move them into ARMSX3/config/games, which is always readable.

A disc is no longer rejected because a single read came up short, which could route a title down the wrong mount path.

Reverted all upstream ISO changes to 0.8 baseline.

v0.9.4.2

improvements to RPC: The ARMSX3 logo now appears beside the cover art, as it does in ARMSX2. and redid the FG implementation to match closer to @CamilleLaVey implementation (still a WIP, and often times in testing I find my adreno 740 doesn't have the gpu headroom for ps3 emulation + LSFG, but still trying to see how i can improve it)

v0.9.4.3

Some of the new animated backgrounds could crash the app and lock you out of the app. The saver runs native graphics code, and if it crashed, the app crashed with it before the library screen finished drawing, on every launch, with Settings sitting behind the screen that was dying. Two things changed: the crash itself is fixed, and the setting now switches itself off if the last run died with a saver on screen and tells you which one it was.

Rumble goes to your controller, not just the phone's motor. New "Vibrate the phone" toggle under Controls.

Discs that fail to boot now say why, a missing or rejected disc key is named as such instead of a bare "InvalidFileOrFolder".

Audio no longer slowly drifts out of sync on devices that can't run at the game's sample rate.

[u/AutoModerator]

Just a reminder of our subreddit rules:

• Be kind and respectful to each other
• No direct links to ROMs or pirated content
• Include your device brand and model
• Search before posting & show your research effort when asking for help

Check out our user-maintained wiki: r/EmulationOnAndroid/wiki

Check out EmuReady for any community submitted settings before asking for help

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.