NX on Orbis runs the Eden Switch emulator on a jailbroken PS4 Pro, and the author's done with it

A Switch emulator running on a jailbroken PS4 Pro. That’s the pitch of NX on Orbis, an experimental port of Eden that just went up as open source. It was tested on firmware 12.02 with GoldHEN. The author has stopped working on it for lack of time, so the code is published as-is.

The stack is OpenOrbis and the orbis-ports SDK, with Mesa RADV driving the PS4 GPU. Per the Reddit post, Eden runs natively with its own game picker, DualShock 4 input and clean audio. Mario Kart 8 Deluxe menus hit 40-60 fps. Races load and play at 13-16 fps, and the author tested sessions of about 15 minutes. Cuphead reaches its menu at around 30 fps. The Homebrew Menu runs without keys.

The problems are real. Red and blue are swapped. The emulated CPU is the bottleneck, not the GPU. The author projects 20-25 fps at best for MK8D races and says 60 fps isn’t reachable on the Jaguar CPU. Memory is tight too: about 4.5 of 4.6 GB used in a race, so the occasional hang during loading.

The repo has Release v0.1.0, which includes a .pkg and the exact ELF for symbolizing crash logs. There’s full source, build docs and results of all 29 console tests. An experimental branch has working fastmem, but races don’t load there yet. One find is useful for any PS4 port: the SDK’s wmemchr works on 16-bit units while wchar_t is 32-bit. That silently breaks std::find on 4-byte types with a newer libc++.

To try it, grab Release v0.1.0 from the repo. Then dump keys, firmware and games from your own Switch. None of that is included. The author says the port isn’t affiliated with Eden and asks people not to report it to the Eden team. It was built with heavy use of AI assistants, Claude and Codex for a couple of test rounds, which is why it’s kept separate from Eden.

My take: this shows the PS4 Pro can host a Switch emulator at all. The Jaguar CPU is the wall, and the author’s own projection stops at 20-25 fps. Watch the fastmem branch and whether anyone picks up the repo. The AI angle will get the loudest threads, but the test log is the more useful part.