The Simpsons: Hit & Run on R36S: Why You Cannot Find the Port

The Short Version

The tutorials are real. The game does run on this hardware. But three things are true at once, and they explain why following those videos in August 2026 leaves you stuck:

• It is not a PortMaster port. It has never been in the official library, so no amount of scrolling or updating the app will surface it.
• It came from a third-party port collection, installed by hand rather than through PortMaster's built-in browser.
• That collection no longer carries it. The path the tutorials and search results point at returns a 404.

So the honest answer to “how do I install The Simpsons: Hit & Run on my R36S” is that the route the videos document is closed. The rest of this page explains why, because the reasoning is worth more than the one game — it is the same reasoning that tells you whether any port you find is going to be there next month.

It Is Not in PortMaster's Library

This is checkable rather than a matter of opinion. PortMaster publishes its entire catalogue as a machine-readable list, and at the time of writing it holds 1,375 ports. Searching that list by port name, by display title and by description returns zero results for “Simpsons” or “Hit & Run”.

The catalogue is not missing things, either — the same search finds DevilutionX, Quake, GTA III, Vice City, Stardew Valley and the Sonic ports exactly where you would expect them. It is a complete list, and this game is not on it.

Why PortMaster Does Not Carry It

The Simpsons: Hit & Run shipped in 2003 for PlayStation 2, GameCube, Xbox and Windows. In August 2021 the game's full source code appeared online. It was leaked, not released — the publisher did not put it out, and nobody was given permission to build on it.

That distinction is the whole story. PortMaster's library carries ports built on open-source engines, on source that was properly released, or on reimplementations written from scratch. A port derived from leaked code does not qualify, and PortMaster has not endorsed this one. That is a deliberate line, not an oversight.

It is the same line our PortMaster guide describes when it sorts ports into five kinds. The legitimate categories all start from code somebody had the right to build on. This game does not have a category to sit in.

What You Would Still Need, Even If You Found It

Worth knowing before you go hunting: the port was never a complete game you could just install. Like DevilutionX with Diablo, or the Quake and DOOM ports, it was an engine that expected you to supply the original game's data files — specifically from the Windows PC version, not from a console disc.

So the full requirement was: own the PC release, extract its asset folders, and copy them alongside the port. If you were picturing a one-tap install from the Ports menu, that was never what this was, even when the download existed.

The Console Versions Are Not a Way Around It

The obvious next thought is to skip the port and emulate the PS2, GameCube or Xbox release instead. That does not work on this device, and it is not close.

As our performance guide sets out, GameCube, PlayStation 2, Wii and 3DS are all beyond the R36S — not “slow”, but out of reach on an RK3326 with four Cortex-A35 cores and 1 GB of RAM. The original Xbox is in the same territory. Dreamcast, a full generation earlier, already sits at roughly 59% playable and is described on this site as borderline rather than comfortable.

This is precisely why a native port was interesting in the first place. Native ARM code pays no emulation tax, which is how a 2003 game that no R36S emulator can touch was running fine in those videos. The PortMaster guide covers that distinction in more detail, including the two port categories that do pay a translation cost.

How to Check Any Port Before You Chase It

You can run the same check we ran, in under a minute, and it will save you an evening on the next game you go looking for:

1. Open PortMaster on the device and search there first. If a port is in the library, it is in the app. If the app cannot find it, no tutorial can change that.
2. Check the date on the tutorial. A video from last month is describing what was true last month. Third-party ports get pulled, and the video stays up.
3. Notice where the download actually lives. If the instructions send you to a GitHub repository or a file host rather than to PortMaster itself, you are installing something unvetted through the autoinstall folder — which is a legitimate route, described in our PortMaster guide, but you are on your own for updates and for it still being there.
4. Ask why it is not in the library. Sometimes the answer is that it is new. Sometimes, as here, the answer is that it cannot be.

What Actually Runs

If what you wanted was a full 3D game from that era running natively on this handheld, PortMaster's library has that, properly supported and installable from the app. GTA III and Vice City are both in it, and both work the same way this one would have: you supply the original game's files, the port supplies an ARM build of the engine.

Our best games guide covers what the emulated side does well, and the PortMaster guide covers how to get ports installed without Wi-Fi, which folder your firmware uses, and why two games that look equally simple can behave completely differently.