mrkeyoor.comAsk

riyadhHDA/wichforkstested 19 Nov 2026commit 5df0f40

wichforks review

Use wichforks if you want dated starting points and will read the reports behind them.

  • Safety failed
  • Build 1 s
5 sto install
  • 35 packages
Dev Toolsevaluationupdated 21 Nov 2026
trackingstars / 7d

wichforks is a guide to Nintendo Switch 2 emulator forks and adjacent native ports. Its README organizes starting points by game, graphics hardware and operating system.

Verdict

Use wichforks if you want dated starting points and will read the reports behind them. Avoid relying on it for a demonstrated Intel Arc laptop fix, one consistent Donkey Kong Bananza recommendation or controlled performance comparisons. Our 5-second install and 1-second build describe the guide's repository tooling; the November 20 deployment record contains a failed Compose-file check.

wichforks infographic: choose a Nintendo Switch 2 emulator fork, plus its uses, our test result, pitfalls and who it suits
Tested 19 November 2026: the source install took 5 s and the build 1 s.

We ran it

Lab card: what happened when we ran wichforks
Lab card from our sandbox run
Screenshot of wichforks (github.com/riyadhHDA/wichforks)
github.com/riyadhHDA/wichforks
Install✓ · 5s35 packages · 39 MB
Build✓ · 1s
Testsn/ano test script
Known vulns0(pip-audit)
Repo40 files~1,776 lines of source · 0.7 MB · 1 CI workflows

Answers from our run

Does wichforks build from source?

Dependencies installed in 5 seconds (35 packages), and the build succeeded in 1 seconds. We cloned commit 5df0f40 into a clean Debian container with 3 CPUs and no project-specific setup.

Does wichforks have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does wichforks have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use wichforks?

Players seeking a demonstrated Intel Arc 140V laptop recommendation.

What are the alternatives to wichforks?

eglantine.pro/forks, Forkbay, NS2 Emulator Manager. Use wichforks if you want dated starting points and will read the reports behind them.

Setup4/5Our source checkout installed in 5 s and built in 1 s with 35 dependencies, but we did not run a README task.Editor’s note: Repository installation and build succeeded, but emulator installation and gameplay were not measured in that completed run.
Docs4/5The README has an install section (“notsapinho/Eglantine Pokopia build”) and usage examples in code; we did not run its quickstart ourselves.Editor’s note: The README and performance page disagree on first picks; the evidence contains no completed assessment under the published site rubric.
Community3/5Last push on 2026-11-07, 592 stars and maintainers answered or closed 5 of the 8 most-discussed issues we sampled.Editor’s note: Sampled issues show accepted corrections and unanswered requests, without a measured support-capacity assessment under the site rubric.
Maturity1/5No tagged GitHub release and repository created 2026-11-05.Editor’s note: Repository tooling built successfully, but the later deployment record conflicts with its failed safety step and supplies no gameplay result.

How we score

Who it’s for

Players comparing dated reports for a particular game and hardware combination.
Contributors submitting experience reports or correcting recommendations through GitHub issues.
Readers willing to keep separate builds and preserve a working installation.

Who it’s NOT for

Players seeking a demonstrated Intel Arc 140V laptop recommendation.
Readers who need one consistent Donkey Kong Bananza first pick across the guide's pages.
Anyone seeking controlled gameplay benchmarks rather than community observations.

Setup reality

Our November 19, 2026 run at commit 5df0f40 installed successfully in 5 seconds and built in 1 second. It recorded 35 dependencies and 39 MB on disk. Tests were skipped because there was no tests script or target; pip-audit reported 0 known vulnerabilities.

The recorded sandbox configuration was 3 CPUs, 8 GB RAM and image ghcr.io/astral-sh/uv:python3.12-bookworm. A November 20 hands-on attempt failed its Compose-file safety check. These are separate repository-tooling and deployment records, described in the body.

wichforks helps readers choose a Nintendo Switch 2 emulator fork, but its README and performance page disagree on some first picks. Use it to shortlist builds for a specific game and machine, then read the underlying reports. Our November 19 repository run installed in 5 seconds and built in 1 second. Those measurements describe the guide's Python tooling. The selection advice comes from project documentation and community experience reports, including an accepted Mario Kart World report whose package label and displayed build version differ.

What people use wichforks for

Contributors use wichforks to publish experience reports, correct obsolete recommendations and propose experimental forks. The tracker records specific outcomes: an Android recommendation changed, an Anka proposal became an experimental entry, and a Mario Kart World report entered the community table. These uses show how readers can contribute more than a bare FPS number. A report with a named game, build and machine gives the maintainer something concrete to include or challenge.

Who used it What they did What changed
MrYeast3kjr Submitted a Mario Kart World experience report The maintainer published it with slowdowns and package-version details; one report did not change the first pick. The community table names the reporter.
The contributor to issue #1 and riyadhHDA Flagged an unmaintained Android recommendation Banana Native replaced the old recommendation.
The Anka proposer in issue #4 Submitted a single-PC Donkey Kong Bananza report Anka entered the guide as experimental without becoming a first pick.
Schroederr/nx-fork-manager, according to Stringers Used wichforks recommendations in a Windows manager Stringers describes automatic downloads and branch switching with recommendations attributed to wichforks.

MrYeast3kjr described Mushroom Cup at 150cc across four races on a Ryzen 9 5950X and RTX 3090, with 64 GB RAM. Race 4 had eight laps. Race 1 laps 2 and 3 appeared flat at 60 FPS, while race 3 had more slowdowns. The v2.0.6 Windows package still displayed v2.0.5, because its bundled README said the Windows build was unchanged. That distinction belongs alongside the performance observations, rather than disappearing behind the download's newer label.

What you can do with wichforks

The README organizes Switch 2 emulator forks and adjacent native ports by game, operating system and GPU. For a first Windows or Linux installation with NVIDIA graphics, it names Djihads80/Eglantine as the starting point. Other rows direct AMD users toward Orchid and Mario Kart World players toward SmileyTatsu. Reading the branches gives you a shortlist tied to a use case, rather than one ranking that applies equally to every game.

The confidence legend distinguishes documentation from corroboration. “Documented” means a fork's README or release notes state the claim; “Corroborated” requires two or more independent reports to agree on the same game, fork and GPU class. The README dates its starting-point advice to November 7, 2026. Build numbers and dates therefore belong in the selection: its instruction to keep the build that worked is more specific than simply following the newest download.

What happened when we ran it

Our November 19, 2026 run used commit 5df0f40: installation succeeded in 5 seconds and the build succeeded in 1 second. The recorded repository contained 40 files, approximately 1,776 source lines and a 0.7 MB checkout. The sandbox configuration listed 3 CPUs, 8 GB RAM and image ghcr.io/astral-sh/uv:python3.12-bookworm. The dependency step recorded 35 dependencies and 39 MB on disk, while pip-audit returned 0 known vulnerabilities.

Step in our sandbox Recorded result What you can conclude
Install Succeeded in 5 seconds; 35 dependencies, 39 MB on disk The recorded dependency step completed.
Build Succeeded in 1 second The recorded repository build completed.
Tests Skipped: no tests script or target The harness recorded a skipped test step.
pip-audit 0 known vulnerabilities This was the dependency-audit result for our run.
Repository signals 1 CI workflow file; no Dockerfile or tests directory The scan found those repository characteristics.

The November 20 safety step failed with “unsafe repo: none of compose.yaml, compose.yml, docker-compose.yaml, docker-compose.yml exists (rule: a compose file is required)”. The message identifies the harness's Compose-file requirement and the missing filenames. Calling this a game crash or a malware finding would change what the log says: the recorded failure was the safety step's prerequisite check.

The November 20 summary nevertheless says “deployed with its own docker compose on our lab server, every port bound to 127.0.0.1”. That summary conflicts with the failed safety step. The teardown record says “teardown: ok”. Keeping all three records visible separates the successful November 19 repository steps from the contradictory November 20 deployment paperwork without turning the summary into evidence of a completed session.

Where people get stuck: changing builds and incomplete fixes

The Mario Kart World notes report force-closes and one third of the FPS for one tester on builds 202 through 212, while another reported success after rebuilding 212. Build 196 was the last stable build for one tester, with 55-60 FPS on an Intel Ultra 255HX. The notes recommend keeping a known-good build. The conflicting outcomes make the named build and machine more useful troubleshooting details than the word “latest.”

Reported problem Documented response Status you should act on
Builds 202 through 212 force-close for one tester Another tester reported success after rebuilding 212 Conflicting experiences; retain a working build.
PGO build crashes or loads slowly Try the MSVC or non-PGO build A workaround in the Mario Kart World notes.
DLC fails after NUP conversion Package DLC separately A discussed workaround in the project notes.
Radeon black screens or GPU-driver crashes in Ocarina of Time builds Shader and Vulkan fixes were documented The performance page still records Radeon failures.
A GPU-first chart suggests a performance ranking riyadhHDA added a compatibility and CPU explanation Issue #2 records the documentation correction.

NUP changes caused a separate class of problems. The project notes say a table-of-contents update around November 1-2 made older NUP files unusable, and users reported games crashing after conversion. DLC was not bundled; packaging it separately was the discussed response to DLC failures. The same notes describe metadata editing and extraction as planned work. A conversion problem therefore needs the container details as well as the emulator build.

The 123 reports are uneven community coverage

The coverage page counts 123 reports across 14 games, including 104 with a named GPU and 93 with a named CPU. It lists 69 distinct CPU, GPU and RAM combinations. Only 60 reports fall in the November 3-6 recommendation window. The separate direct-submission table contains one report for one game and one fork. These are different collections, so the larger count should not be described as 123 direct submissions.

The README reports 63 NVIDIA entries, 37 AMD entries, 6 Steam Deck entries and 17 without a named GPU. Its 68 CPU/GPU pairs also measure a different combination from the coverage page's 69 CPU/GPU/RAM combinations. The README explicitly says the charts count reports. A chart bar therefore describes how often a setup appears in collected reports; it is not a score awarded to that hardware.

GitHub metadata records the repository's last push as November 7, 2026. The tracker shows concrete maintainer actions: the Android correction in issue #1, the CPU/GPU explanation in issue #2, and the accepted race report in issue #5. Those conversations describe the support readers received more clearly than a popularity count does.

Security checks stop at the download boundary

The link checker checks whether repository and release URLs in data/forks.json resolve. Its documented behavior gives dead links and unreachable hosts a failing exit status, while persistent rate limits and server errors can be reported as “INCONCLUSIVE” without failing the run. That distinction matters when reading automation output: a completed command can include destinations the checker classified as inconclusive rather than available.

The checker documents python -I scripts/check_links.py and a variant with --data data/forks.json --timeout 15 --delay 1. These are usage examples from the script, separate from the install and build measurements above. Its classification names describe HTTP outcomes: OK, DEAD, FAIL, INCONCLUSIVE and UNREACHABLE. The script's stated task is URL resolution, so those labels should retain that meaning when a reader assesses a download link.

wichforks vs the alternatives people search

Stringers describes eglantine.pro/forks as a filterable table with per-game pages, while wichforks presents its choices in a repository guide. Its account also describes a pinned r/switch2emu moderator guide with overlapping recommendations. These are differences in browsing and presentation reported by Stringers. Fork managers serve another task: issue #9 proposes keeping installation tools separate from the fork tables and rankings.

Alternative Why you would choose it Relationship to wichforks
eglantine.pro/forks You want filters and per-game browsing A browsing alternative described by Stringers.
Pinned r/switch2emu moderator guide You follow that community's selection discussion An overlapping comparison guide, according to Stringers.
Individual fork READMEs You have selected a project and need its instructions Stringers describes their project-specific focus and says installation videos age quickly.
Forkbay You want installation and update management Its author proposes it as a separate tools entry in issue #9.
NS2 Emulator Manager You want another manager candidate The same proposer names it alongside Forkbay.

Forkbay's author links tom-tour/forkbay and says the manager installs releases, checks downloads against their checksums, and shares keys, firmware and saves between emulators. The proposal also says it never includes or downloads keys, firmware or games. These are the author's descriptions in issue #9. They explain why a manager could complement a selection guide: choosing a build and maintaining its installation are separate jobs.

What the other reviews get wrong

Stringers gives conflicting Zelda explanations for the guide's timing: its timeline identifies the Ocarina of Time remake, while its “Why this one” passage names Tears of the Kingdom launch traffic. Those are different launch attributions on the Stringers page. The contradiction should stay visible rather than becoming a causal history of wichforks. Its descriptions of browsing alternatives and integrations are separate claims from that launch story.

Like.do calls the guide actively maintained while describing a November 9 snapshot and a November 7 push. The same passage says one snapshot says nothing about growth. A dated popularity snapshot and the date attached to a recommendation answer different questions. The README's November 7 starting points should keep their date even when another page displays a newer star count.

The docs disagree on first picks and flatten one race report

The README names Selevet or PokeDinner for Donkey Kong Bananza, while the performance page's corrections name ZendNevs first. For Mario Kart World, the README names SmileyTatsu, while the performance page says ZendNevs shares the pick. The maintainer's issue #4 reply also retains Selevet perf 3/4 or PokeDinner 2.5 for Donkey Kong Bananza. Presenting the disagreement preserves what each page actually recommends.

Claim to read carefully What the fuller account says
“60” typical FPS in the direct-submission summary MrYeast3kjr describes slowdowns and separates a paused menu from racing.
ZendNevs was only tried on Mario Kart World The performance page says its v2.0.5 notes also cover Donkey Kong Bananza and Pokopia startup.
Startup proves a game is playable throughout The Pokopia row labels its observation “startup test only, about one minute”.

Issue #5 explicitly calls the race results player observations rather than benchmark measurements. It also says lowering resolution scale made almost no performance difference on the reporter's system. The maintainer recorded “60 FPS typical with slowdowns” and retained the race-by-race details. Reading that accepted report gives a more precise account than the summary table's bare “60,” without changing either the package version or what the player observed.

Questions people ask

For a first Windows or Linux installation with NVIDIA graphics, the README recommends Djihads80/Eglantine. Its November 7 table then branches by game, GPU and platform. The questions below follow requests in the tracker and community discussion, including Android recommendations, PS5 coverage and a proposed tools section. Their answers preserve the difference between a maintainer's decision, a user's report and a proposal.

Which Switch 2 emulator fork should I use for my game, GPU and operating system?

The README starts NVIDIA Windows/Linux users with Djihads80/Eglantine, AMD users with Orchid, and Mario Kart World players with SmileyTatsu. Its Android branch names Banana Native. The conflicting-picks section above records the Donkey Kong Bananza and Mario Kart World differences between pages. The confidence legend supplies another useful distinction: a documented project claim and independently agreeing reports receive different labels.

Which fork works on an Intel Arc 140V laptop?

The Galaxy Book user in issue #7 reports boot failures, green screens, severe stutter and random crashes across several forks. The request names integrated Intel Arc 140V graphics, 32 GB LPDDR5X RAM and Windows 11 Home. Those are the user's machine details and reported outcomes, so the report should remain attached to that laptop rather than becoming a finding about every Intel GPU.

Can wichforks provide a dedicated guide to PS5 Eglantine forks?

The maintainer requested the 7-10 repository URLs, build tags and several tested games before adding a dedicated PS5 guide. The issue #3 reply describes the existing EglantinePS5 row as experimental and source only. That request gives contributors a concrete task: identify the repositories and tested builds rather than treating similarly named PS5 projects as one release.

Which emulator works with Nintendo Switch Sports Resort?

Issue #10 asks which emulator works with Nintendo Switch Sports Resort. The request uses that exact game name, while the coverage page has a differently named Switch Sports row. Keeping the names separate avoids silently answering a question about one title with a row about another. The thread is the place where that requested recommendation was raised.

Is CPU performance a bigger constraint than the GPU?

CPU single-core speed and build choice often decide FPS, according to riyadhHDA's correction in issue #2. The same reply says GPU branches describe compatibility and known driver bugs, and rejects a proposed platform ranking that mixes native ports with emulator results. Its explanation concerns how to read these charts, rather than assigning a universal performance order to CPU brands or platforms.

Should Banana Native replace the unmaintained Android recommendation?

Banana Native became the Android recommendation, and the old eden-nx2-android entry was marked unmaintained. The maintainer records that change in issue #1, which closed after the correction. This is a clear example of the tracker changing the guide: a contributor identified an obsolete destination, and the maintainer named its replacement and the status of the former entry.

Should Anka be included as a Windows option for Donkey Kong Bananza?

Anka entered the guide as an experimental Windows performance fork. The maintainer recorded its single-PC result on a Ryzen 7 5700X and RTX 4060 Ti, along with its source audit and one-release context. The issue #4 reply kept Selevet perf 3/4 or PokeDinner 2.5 as the Donkey Kong first pick. Inclusion and a first-pick recommendation were separate decisions.

Will wichforks add a tools section for installing and managing emulator forks?

Issue #9 proposes a tools section for Forkbay and NS2 Emulator Manager, separate from rankings. Forkbay's author offers to open a PR and describes installation, updates and checksum checks. The proposal links Forkbay at tom-tour/forkbay. Its wording is a request to add a section, rather than an announcement that the maintainer has added or endorsed those tools.

Why don't the fork developers merge their work into one project?

X user hudsonfiveone expressed a wish for the projects to combine into an eventual Switch 2 emulator. That post records a user's preference. It supplies a reason readers ask about consolidation, but a wish is different from a developer agreement. Keeping the speaker identified avoids attributing the statement to the wichforks maintainer or attaching an unsupported date to a merger intention.

What actually works in Switch 2 emulation on Android?

The README describes Banana Native as a native port, with Donkey Kong Bananza working, Pokopia running at about 60 FPS and Mario Kart World in progress. Its Android entry names Android 13+, Snapdragon/Adreno and 12 GB RAM. These are the guide's claims about the port. They should retain that attribution rather than borrowing support from a video's general introduction to Switch 2 emulation.

Would users want an auto-updater, and should it verify signatures?

The project notes say 7 of 10 respondents favored an updater and that users requested signature checks if one were added. They also date the absence of an auto-updater to November 5. These are dated community requests in the project notes, separate from Forkbay's author's description of checksum checks. Neither passage announces that wichforks shipped an updater.

What we have not tested yet

Our completed run measured repository installation and build steps, with tests skipped because there was no target. It did not measure emulator gameplay, sustained frame rates, GPU comparisons, controllers or Android compatibility. The contradictory November 20 summary and failed Compose safety step do not establish a successful deployment. The sandbox image label does not establish actual runtime versions; those require raw toolchain logs. Managers, the Stringers-reported integration, rendered-page layout, resolved links and accessibility also remain outside our hands-on results.

The available video transcript extract introduces Switch 2 emulation; it does not establish Android compatibility, name Banana Native or support a download-and-done warning. The recommendation pages' revision order and authority remain unresolved. Issue #7 contains no working Intel Arc laptop recommendation or maintainer reply, and the coverage table has no named Intel GPU reports. The PS5 request awaits the repository list, the Sports Resort question has no answer, and the tools proposal has no maintainer reply.

Most collected reports omit driver versions, game versions or 1% lows, and several games lack named GPU-vendor coverage. Those omissions prevent controlled comparisons. The Radeon fixes lack confirmation in affected gameplay; the Pokopia startup observation is not sustained playability evidence. Link availability and our pip-audit result do not establish binary authenticity, signature validity or the safety of linked executables. A November 7 push and a popularity snapshot do not establish daily maintenance through November 20. The records also contain no measured worldwide search demand for this review's query.

Alternatives

ProjectWhat it isPick it when
eglantine.pro/forksStringers describes a filterable table and per-game pages.Consider it when you prefer browsing filters to reading a repository guide.
ForkbayIts author describes installation, updates and checksum checks for emulator forks.Consider it when installing and switching forks is the task; issue #9 proposes it as a separate tools entry.
NS2 Emulator ManagerThe tools-section proposer names it alongside Forkbay.Consider it as another manager candidate named in issue #9.

What people are saying

  1. [velocity-scout] riyadhHDA/wichforks

Sources

  1. wichforks README
  2. wichforks coverage
  3. wichforks performance reports
  4. wichforks link checker
  5. Mario Kart World experience report, issue #5
  6. Intel Arc laptop request, issue #7
  7. Stringers discussion of wichforks
  8. Emulator-manager proposal, issue #9

More dev tools reviews