riyadhHDA/wichforks
GamesA curated guide to Nintendo Switch 2 emulator forks, matching builds to GPU, OS, and target games.
What this is
Which Forks? is a community-maintained selection guide for Nintendo Switch 2 emulator forks and related native ports. Instead of shipping an emulator, it helps readers choose a build based on platform, GPU vendor, and the game they want to play, and it labels each claim by how it was verified: documented, corroborated, community-reported, or source-only 第16-37行.
The guide currently covers forks such as Djihads80/Eglantine, SmileyTatsu/Eglantine, MythosOfs/Orchid, PokeDinner, notsapinho/Eglantine, Lichii, Droplet, rdenno/Eglantine, ZendNevs, Banana Native, selevet-eglantine, and EglantinePS5. It also includes a game-by-fork matrix, per-game notes, a performance dataset, and a source audit 第88-99行 第224-252行 source audit.
Quick start
- Read the fork selection table and pick a starting point for your GPU and OS. For a first install on Windows or Linux with an NVIDIA GPU, the guide suggests Djihads80/Eglantine 第16-37行.
- Follow the setup checklist: bring your own game dump,
prod.keys, and firmware; update to current Vulkan drivers; keep at least 16 GB of RAM; and warm the shader cache before judging performance 第272-281行. - Use the game-specific notes for settings and known issues, for example Mario Kart World notes, Donkey Kong Bananza notes, and Pokopia notes.
- Pin a build that works for your game and keep a copy before updating. Builds change frequently and regressions are normal.
On Android, the guide points to Banana Native, a native port rather than an emulator. It requires Android 13+, a Snapdragon/Adreno GPU, and at least 12 GB of RAM, and the game must be prepared once. Mario Kart World preparation needs a Mac 第282-290行 releases.
Constraints
- Neither the guide nor its linked builds include game dumps, keys, or firmware. Users must supply their own, and sharing those files is discouraged 第329-337行.
- These are unsigned community builds. Forks can change, regress, or disappear, so the guide recommends preferring repository releases over repacks and checking whether a fork publishes source in its repository 第291-308行.
- Performance claims are tied to specific builds, hardware, drivers, and test locations. The guide explicitly treats single reports as anecdotes and states that frame generation raises the counter, not the simulation rate 第309-316行.
- The fork recommendations reflect reports from 3-5 November 2026 on the newest builds available at that time. Older entries remain as history but do not drive first picks 第317-328行.
HotRepo's take
This is a documentation project, not an emulator distribution. Its value comes from separating documented claims from community reports and from recording when a source audit changed its own recommendations, such as downgrading ZendNevs after reviewing its short repository history. It appeared in HotRepo's new-project snapshot on 2026-11-06 with 107 stars gained since 2026-11-05, and there is no ranked GitHub daily placement recorded for it. That growth is consistent with interest in a fast-moving emulator scene, but it is not evidence that any listed build is stable or safe to run.
Written by AI from the project's README, updated . The project's own docs are the source of truth.