Details/Guide: https://misterfpga.org/viewtopic.php?t=10682
Known Issues:
Gameplay (KI1): https://www.youtube.com/watch?v=DTyKQ_GejhA
Download: https://git.eden-emu.dev/eden-ci/nightly/releases/tag/v1786991149.2000fdfb7b
The Lossless Scaling Frame Gen tool has arrived in the latest Eden Nightly update.
AppStore: https://apps.apple.com/us/app/super-zsnes/id6786741278
Details: https://www.zsnes.com/
Video overview: https://youtu.be/-b3T-FPneDI
The two original developers of ZSNES are finally back together! Introducing SUPER ZSNES! Re-written completely from scratch, this GPU-powered SNES emulator is here to bring you the following: some of what is familiar, some of what's new, and then some of what goes beyond
The PSP Homebrew Dev Conference is BACK for 2026! The conference will be held on August 22nd at 6PM UTC; 2PM EDT!
#List of presentations:
https://readonlymemo.com/pcsx2-stuntman-fork-interview-dirge-of-cerberus-translation/
PCSX2-Reliquary, a fork DiscoStarslayer has been developing that focuses on "the issues on the edge of emulating the PS2.
Version 1.7 marks the first Android release of Crash Bandicoot Decomp.
The Android version is designed to provide the same complete experience as the desktop release, including the launcher, developer tools, cheats, graphics settings, mod support, physical controllers, and customizable touch controls.
Crash Bandicoot Recompiled is now available as a single Android APK containing both the launcher and the game runtime.
The Android release includes:
Full Crash Bandicoot launcher
Hardware-accelerated OpenGL ES rendering
SPU and XA audio playback
Physical gamepad support
Controller rumble
Configurable touchscreen controls
Customizable control position, scale, opacity, and colors
Floating 8-way virtual joystick
Landscape and portrait orientation support
Graphics settings and presets
Integer scaling with letterboxing
Developer Menu
Cheat menu
Performance HUD
CPU, memory, RAM, VRAM, SPU, and CD diagnostics
Runtime console and debug information
On-device VRAM viewer
The Android release includes the same modding system available on desktop.
Mods can be:
Imported directly from .zip files
Enabled or disabled from the launcher
Removed from the Mods menu
Distributed with assets and C# code
C# mods can be compiled and loaded directly on Android, and example mods are included with the release.
The Android release can be played using either physical controllers or the built-in touchscreen controls.
Physical controller features include:
Android HID gamepad support
Controller rumble
Controller navigation in menus and dialogs
SDL input fallback
Physical controller state handling alongside virtual controls
The touchscreen controller includes:
Fully editable control layout
Adjustable scale and opacity
Customizable colors
Optional shoulder buttons
Floating 8-way joystick
Multi-touch support
- Immersive fullscreen gameplay
The Android runtime uses direct hardware-accelerated OpenGL ES rendering rather than a software framebuffer presentation path.
Additional work includes:
Direct GPU presentation without per-frame CPU framebuffer readbacks
Improved EGL surface creation, resizing, and recovery
Dynamic landscape and portrait orientation handling
Improved frame pacing and VBlank synchronization
Optimized rendering paths for mobile GPUs
Qualcomm framebuffer-fetch support when available
Qualcomm coarse shading rate support when available
Mali-specific renderer handling and diagnostics
Reduced unnecessary GPU and session logging
Improved texture sizing at high internal resolutions
Faster memory loading paths
Improved audio pause and resume handling
Improved frame clock behavior
Version 1.7 also includes several improvements to the desktop versions:
Removed the black borders at the top and bottom of the game by cropping unused NTSC overscan, allowing the image to properly fill the available display area
Improved keyboard input handling when the game is embedded inside the Windows launcher
Improved focus handling for the embedded game window
Fixed input events potentially reaching a disposed ImGui context during shutdown
Improved input cleanup and resource disposal
General runtime and stability improvements
Nova interface em Qt com sistema de configurações integrado e um debugger funcional. O teclado e os controles agora estão 100% funcionais, com suporte completo ao mapeamento. Também foram implementadas melhorias na renderização 3D, além de diversas correções, otimizações e aprimoramentos na emulação.
Unofficial fork (proof-of-concept) android version of the experimental open source PlayStation 5 emulator, two builds are available to test and download here: https://github.com/edeegg/sharpemu-arm64/releases
Installed on my phone, I have not tried any games yet, it's recommended to test the game named; Dreaming Sarah as a quick test of how well your hardware handles emulation.
Sonic mania Sega Saturn port (engine rebuild) showcase: https://www.youtube.com/watch?v=Y7NKGCxIFAc
Info from the video description;
>Currently building a port of Sonic Mania to the Saturn by rebuilding the entire engine from the ground up so the game takes advantage of the Saturn hardware.
>This currently works with no RAM expansion so far, and it might be possible to get the whole game running on the stock RAM, but I’m not sure yet and have major doubts. So far, I’ve had to basically convert all the assets to 4bpp, which has been lossless for about 99% of them. Although you may notice that the reflection on Sonic’s head is a bit more noticeable, I might be able to fix that or make the change less noticeable eventually.
>A lot of the memory savings come from deduplicating frames. For example, the Bored 2 animation has 68 frames, yet only 14 of them are unique.
>I was originally planning to keep this secret until I had completely finished Acts 1 and 2, but I decided to make it public after seeing that someone else is also porting the game to the Saturn, although in a completely different way.
>Here’s a link to their project—please support their hard work: github.com/likeagfeld/SaturnMania/tree/master
>And i won’t lie here: I started this project thanks to Claude code a few weeks ago, so I may end up facing a roadblock down the road, but so far everything has been going fine.
>I still won’t make the actual project files public or release Acts 1 and 2 until they’re complete and free of bugs, as far as I can test it, so it may take a while.
>Built using SaturnRingLib (SRL)
Apparently there is a known bug:
“PSA: Black screen glitch is known and will be updated on once a cause is found and fixed”
Infinity blade was originally released on iOS in 2010 and became unplayable for a time because of software and hardware updates, but do to the efforts of dedicated independent developers it is playable again today on many different platforms.
They have done dances for Final Fight, King of Fighters, One Piece. IG @robotronic_harmonix_official
Translated by u/LunarIndieStudios and graciously hosted by project_umb.
From r/emulation:
Six months ago I got upstream Flycast compiling to WebAssembly and running as a libretro core. It booted games at about 2 FPS on the interpreter. Fun proof of concept, completely unplayable.
Today, heavy 3D titles like Jet Grind Radio and Shenmue hold their target framerate at native resolution with clean audio, in a browser tab, on ordinary hardware.
Here's how that gap closed.
Every Dreamcast emulator that runs at full speed depends on a dynamic recompiler. A dynarec generates native code at runtime and jumps into it. WebAssembly makes that structurally impossible: code and data live in separate address spaces, so there's no writable-executable memory to generate into, and nothing you write into linear memory can ever be executed.
Upstream had already declined WASM support, and the consensus was that this was a dead end. Browser Dreamcast would stay a slideshow.
Fuck that.
The JIT doesn't patch memory. It generates entire WebAssembly modules at runtime.
SH4 code is decoded into Flycast's SHIL IR, lowered to wasm bytecode in the browser, compiled and instantiated through the wasm API, and dispatched via call_indirect from a C dispatch loop. The host boundary gets crossed once per module, at compile time. Steady-state execution is wasm calling wasm, with no JavaScript anywhere on the dispatch path.
Months of walls, and slightly less hair. Every one of these is documented with numbers in the writeup:
The whole JIT was validated with differential test harnesses against the unmodified reference interpreter. Hundreds of thousands of block-level state comparisons, zero divergence.
Building a correct dynarec solo is mostly a testing problem, not a codegen problem. Once the harness existed, every bug became a bisect instead of a mystery. The writeup covers the methodology in detail, and it generalizes to any target where you have a working interpreter to diff against.
Windows CE titles. They need full SH4 MMU support in the JIT. That's next on my list, at a slower pace than the sprint that built the rest. The phased plan and root cause analysis are already published, so if you want to help, or beat me to it, the hard analysis is done.
I also haven't tested every title. If something breaks, open an issue.
Repo: https://github.com/nasomers/flycast-wasm
Release: https://github.com/nasomers/flycast-wasm/releases/tag/v1.0
Credit where it's due: Flycast is flyinghead's emulator, and this stands on that codebase and its reference interpreter. The WASM port and the JIT are my work.
Happy to answer questions.