Short answer: use this repository for patch history
Our sandbox install of ShadyHero/Eden-NS2 failed in 1 second because CMake required 3.31 or higher and found 3.25.1. Use this repository to study the patch effort and its handoff. Players seeking a supported download should start with a project's own release information. ShadyHero announced archiving this repository in issue #1, and the README directs readers to 0x2593/Eden-NS2.
ShadyHero/Eden-NS2, 0x2593/Eden-NS2 and Takoroka's eden-nx2 are separate repository identities. Our CMake failure belongs to the ShadyHero checkout. LoveGame's compatibility inventory describes 0x2593's fork, while the Windows debugging observations below belong to sskyNS/Eden-NS2-dlss-osd. Those names matter when choosing a source tree, finding a download or following a troubleshooting report. A result attached to one repository answers a question about that repository and revision.
What people use Eden-NS2 for
ShadyHero used this repository for a patch effort and then handed discussion to 0x2593/Eden-NS2; the other recorded uses concern named related projects.
| Who | What they did | Recorded outcome |
|---|---|---|
| ShadyHero | Developed and handed off this patch repository | Announced archiving it because it had done its job. Maintainer's comment |
| 0x2593/Eden-NS2, summarized by LoveGame | Pursued Donkey Kong Bananza and Mario Kart World compatibility | LoveGame records claims that both were playable with slow areas before archiving. Fork inventory |
| PixelCNinja on X | Described compatibility in the related fork | Reported Mario Kart World Free Roam, Splatoon Raiders loading crashes and Welcome Tour booting to black. Compatibility post |
| sskyNS/Eden-NS2-dlss-osd work-log author | Built and debugged a related Windows patch | Reported a working mode-select menu followed by loading failures. Windows work log |
The Windows work-log author reported the mode-select menu at 100% speed and 60 FPS, checked more than six times, with single-core and multi-core operation. Selecting Normal Mode then reached a loading screen and a crash at that recorded stage. The sequence gives developers a concrete stopping point: the menu worked, the next step failed, and the author investigated loading errors. A menu result and a loading result describe different parts of the same attempt.
What happened when we ran it
Our November 18, 2026 run at commit edee9f7 stopped during CMake configuration with exit 1 after 1 second; the full harness took 7 seconds.
| Recorded check | Result | Practical meaning |
|---|---|---|
| Sandbox configuration | 3 CPUs, 8 GB RAM, image lab-cpp:1 | Recorded configuration for this attempt |
| Checkout | 4,071 files, approximately 775,693 source lines, 43.1 MB | Size of the measured source checkout |
| Install step | Failed, exit 1, 1 second | Configuration stopped before a build result |
| Exact blocker | CMake 3.31 or higher required; 3.25.1 running | The installed CMake fell below the declared minimum |
| Repository signals | 0 CI workflow files, no Dockerfile, no tests directory | Results of the repository file scan |
| Complete harness | 7 seconds | Total recorded harness duration |
The log prints cmake test flags: -DYUZU_TESTS=ON, repeats the minimum-version error and reports that configuration is incomplete. Our run measured a setup failure at the version check. The next practical step follows directly from that error: use a toolchain meeting the checkout's CMake 3.31 minimum before attempting configuration again. The recorded attempt supplied CMake 3.25.1, so changing game settings would not address this particular failure.
The separate hands-on runner recorded a failed safety step because none of compose.yaml, compose.yml, docker-compose.yaml or docker-compose.yml existed. Its rule required a Compose file. The hands-on summary nevertheless says it deployed with its own Docker Compose configuration and bound every port to 127.0.0.1. The detailed safety failure conflicts with that summary; the teardown record says teardown: ok.
The two setup records stopped at different requirements. The source harness reached CMake and recorded a version error. The separate runner encountered its Compose-file safety rule. For a developer investigating this source checkout, the CMake log supplies the direct toolchain finding, while the Compose refusal explains the failed automation step. Both failures remain part of the record, alongside the contradictory deployment summary and successful teardown message.
Where people get stuck: patches, Qt and loading screens
The supplied reports describe patch-installation confusion, a Qt startup error, file-handle exhaustion and distinct graphics or loading failures in related projects.
| Problem and source | Recorded response | Status in that source |
|---|---|---|
| An X user asked what to do with .patch files | Zia4dd explained applying the patch to source before compiling | Source-build workflow explained |
| Related Windows build reported no Qt platform plugin | Author copied runtime dependencies beside eden.exe and supplied qt.conf with the plugin directory | Startup blocker addressed in that log |
| Related MinGW run reported Too many open files after Normal Mode | Author changed VFS cache eviction to respect the runtime limit | File-handle blocker fixed in that log |
| Related Windows run presented frames but showed black | Author backed and mapped render-target ranges reserved by GPU command 214 | First visible UI frames reported |
| PixelCNinja reported black destructible terrain in Bananza and loading crashes in Splatoon Raiders | Post supplies compatibility observations | Reported failures retained |
A patch changes source code before compilation. Zia4dd's patch reply gives git apply NS2.patch, followed by the project's build instructions. The PC tutorial likewise explains that putting the patch in Eden's folders does nothing. This workflow starts with source code and leads to compilation. The relevant instructions therefore belong to the patch's intended source checkout, rather than an installed emulator's game or configuration folders.
The Windows work log records the VFS keeping up to 8192 host files open while its MinGW runtime capped _setmaxstdio at 2048. The author changed eviction to stay below _getmaxstdio() - 256. The same extract records a SparseLargeVector page fault about 20 seconds after selecting Normal Mode, followed by null-pointer accesses and a guest jump to 0. Another supplied passage places a name-table null dereference roughly 15 seconds into loading.
The related work log also describes render targets without backing, so their clears and draws went nowhere. After backing and mapping work involving GPU command 214, the author reported first visible UI frames at 60 FPS. A subsequent first-load investigation identified a silent 1024-mapping limit per worker, with 0xce01, OutOfResource. These are separate debugging observations: the visible-frame result addresses the black display, while the loading investigation identifies another stopping point.
The README directs readers to 0x2593/Eden-NS2
ShadyHero announced archiving the repository in issue #1. The README opens with a notice directing readers to 0x2593/Eden-NS2 and then introduces Eden as a Switch 1 emulator.
The readable repository README describes Eden as free and open source, written in C++, with builds for several platforms. Its compatibility paragraph says the emulator can run most commercial games at full speed when hardware requirements are met. That paragraph sits within the inherited Eden introduction. The build guide and release destinations also point to upstream Eden, which is the project named by those links.
The supplied GitHub facts record ShadyHero/Eden-NS2's last push as October 30, 2026. The maintainer's issue #1 comment supplies the archive announcement and handoff. LoveGame separately describes 0x2593/Eden-NS2 as source only, with no builds, and archived on November 3. These are two repository histories: ShadyHero's comment explains his handoff, while the dated inventory describes the later state of the named destination.
Eden-NS2 vs Eglantine, Lichii and eden-nx2
LoveGame's dated inventory separates source-only 0x2593/Eden-NS2 from desktop forks and Android ports, while the eden-nx2 snapshot describes a specific Windows release.
| Project | Why consider it | Decision boundary |
|---|---|---|
| ShadyHero/Eden-NS2 | Study the patch repository and handoff | README directs readers elsewhere |
| 0x2593/Eden-NS2 | Trace ShadyHero's named destination | ShadyHero explicitly directed discussion there in issue #1 |
| Eglantine | Investigate desktop downloads and related development | LoveGame describes several desktop platforms |
| Lichii | Follow dated player reports for particular games | LoveGame favors it for several games in its comparison |
| Takoroka's eden-nx2 | Study its Windows pre-release | Separate branch and release identity |
| Official Eden | Run original Switch games | November 3 coverage says it lacks Switch 2 support |
The first-week coverage lists Eglantine for Windows, Linux on x86_64 and ARM64, and Apple silicon Mac. The eden-nx2 snapshot describes one release, followed by a small Linux build fix, and names Eglantine and Lichii as projects continuing the work. Its Linux discussion describes AppImages for both. These records help readers locate a project and artifact before following a report about a particular game.
For Android, the November inventory identifies Hokkaido as the active Android fork and describes Eden SX2A separately. The first-week coverage names moceure as SX2A's maintainer and calls v0.3.2 its final release. For original Switch games, the official-Eden status report identifies stable v0.2.1. Choose a platform and repository first, then read the release information and game reports attached to that project.
What the other reviews get wrong
AxeeTech's Android recommendation conflicts with the supplied inventory, while other named pages mix project identities or make claims broader than their examples support.
| Page or claim | Correction supported by the supplied records |
|---|---|
| AxeeTech presents Eden-NS2 as an Android choice with precompiled APKs | LoveGame lists 0x2593/Eden-NS2 as source only and identifies Android ports separately |
| AxeeTech describes daily architectural commits in Takoroka's branch | The later snapshot describes release-day work followed by one small Linux build fix |
| AxeeTech limits Eglantine to rudimentary homebrew | LoveGame describes commercial titles reaching gameplay, alongside failures |
| IGN France attributes Eglantine to Camille LaVey | LoveGame lists Djihads80 as Eglantine's maintainer and describes LaVey reviewing a separate Eden draft |
| SoVis Games says no commercial Switch 2 game runs in a public emulator | Its later table says Bananza boots and moves through its opening section |
| SoVis Games calls PokeDinner an Android port | LoveGame lists Windows, Linux and Apple silicon Mac, with SX2A separately identified for Android |
The corrections concern AxeeTech's fork comparison, IGN France's coverage and SoVis Games' setup guide. The counterevidence comes from the supplied inventory, first-week coverage and release snapshot. SoVis Games supplies a particularly clear internal conflict: its Bananza row describes booting and movement through the opening section. That concrete outcome gives readers a more useful answer than its blanket statement about commercial games.
Creative Gamers' Android walkthrough calls SX2A an Eden-team product, while the inventory identifies a separate community port. Splatoon Raiders has another conflict: LoveGame records stable-60-FPS project claims, and PixelCNinja's compatibility post reports loading-screen crashes. The page retains both reports with their speakers attached. A reader choosing a build needs the reported failure as well as the claimed frame rate.
FAQ
An NS2 patch applies to Eden's source before compilation; the supplied tutorial says placing it in an installed emulator folder does nothing. That answers the patch-installation question raised on X. The remaining questions come from the supplied synthesis and concern downloads, decryption, collaboration, platforms and official support. The answers below identify the repository, report or participant responsible for each factual statement.
How do I apply an NS2 .patch file and compile Eden afterward?
Zia4dd gives git apply NS2.patch, followed by the project's build instructions. The X explanation describes applying a source change before compiling. The Windows work log also describes hand-merging context differences during related work. Start with the patch's intended source revision and its build documentation; putting the file in an installed emulator folder is the mistaken workflow addressed by the supplied tutorial.
Should Eden-NS2 remove ROM decryption logic to reduce the risk of a lawsuit?
Issue #1 proposes removing decryption logic because of litigation concerns. Commenters discuss unencrypted Switch 2 dumps and inherited Switch 1 functionality before ShadyHero redirects the thread. The decryption discussion records that request and the participants' responses. Its documented outcome for this repository is ShadyHero's instruction to move discussion to 0x2593/Eden-NS2, together with his announcement that he was archiving his repository.
Are Switch 2 game dumps already unencrypted?
Slimemaster0 says Switch 2 dumps are unencrypted in issue #1. Another participant asks whether that leaves decryption logic for Switch 1, referring to functionality retained upstream. These comments explain the participants' reasoning in the decryption thread. The exchange concerns the proposed removal of code, and the maintainer's response sends that discussion to a different repository.
Have the NS2 researchers considered joining the Eden team and combining their work into one pull request?
Leo7rz6 asks a researcher about joining the Eden team and combining work into one PR. The X question records that collaboration request. The November 3 status coverage separately describes an unmerged draft and smaller format-recognition contributions awaiting review. Together, these records describe a public request to coordinate work and the reported state of particular proposed contributions.
How do I emulate Switch 2 games on a PC?
The supplied PC tutorial uses an experimental Eden NX2 build and explains the distinction between a source patch and an installed emulator. Its setup walkthrough concerns that project. For the reviewed ShadyHero checkout, our concrete setup result is the CMake minimum-version failure at edee9f7. The immediate source-build requirement from our log is CMake 3.31 or higher; the recorded environment supplied 3.25.1.
Where is the Eden-NS2 download?
ShadyHero's README directs readers to 0x2593/Eden-NS2, which LoveGame lists as source only with no builds. The inherited release destination points to upstream Eden. The dated fork inventory lists desktop alternatives separately, including Eglantine and Lichii. Begin a download search with the full repository name and follow its actual release destination, since the shared Eden-NS2 name spans different source and coverage records.
How do I set up Eden SX2A and add my game folders on Android?
Creative Gamers' walkthrough selects a game folder, grants folder access and enables deep scanning; the creator reports games appearing with missing covers. This is the workflow shown for Eden SX2A in the Android video. The dated inventory identifies SX2A separately from Eden-NS2. That distinction keeps an Android folder-access instruction attached to the application shown in the walkthrough.
Which Switch 2 emulator should I choose for PC, Android or Mac?
LoveGame's November 10 comparison favors Lichii for several desktop games, names Hokkaido for Android and distinguishes a native route for Apple silicon. Its platform inventory provides those dated recommendations. For a practical starting point, use the table above to identify a project for your platform, then follow a report naming the game and release you intend to use.
Will official Eden support Switch 2 games?
The November 3 status says official Eden does not support Switch 2 and identifies an unmerged draft PR. Mr. Sujano's video reports discussion of accepting patches. The status coverage identifies stable v0.2.1 and proposed contributions separately, while the video report covers development discussion. The dated status supplies the concrete answer about official support in the supplied evidence.
Can Switch 2 games already run on a PC?
The supplied coverage describes commercial games booting and reaching gameplay in experimental forks. PixelCNinja reports Mario Kart World Free Roam, black destructible terrain in Bananza, loading crashes in Splatoon Raiders and a black screen in Welcome Tour. The compatibility post and fork coverage answer this through named games and stopping points, which are more useful for choosing a build than a single yes-or-no compatibility label.
What we have not tested yet
Our edee9f7 attempt ended at configuration; gameplay, successful installation with supported CMake, controllers, saves, graphics accuracy and sustained sessions remain untested. The image label establishes neither runtime nor operating-system versions. File-scan signals are not executed tests, and enabling a test flag supplies no passing-test count. The latest-release field is null; that lookup does not establish whether a release exists. These boundaries apply to our measured source attempt.
The supplied repository facts contain no archived field; the archive account rests on ShadyHero's announcement. The separate hands-on records conflict about deployment and contain no completed game task, hands-on Q&A or screenshot records. The source-patch command was not executed for this revision. The Windows work-log milestones belong to sskyNS/Eden-NS2-dlss-osd, and the supplied extract ends before establishing a completed fix for its first-load mapping failure or final gameplay stability.
Alternative recommendations are a reading order drawn from dated reports, not our controlled comparison. Their artifacts, platform coverage and compatibility results have not been reproduced here. PixelCNinja's post supplies no firsthand test procedure, and the conflicting Splatoon reports do not establish identical hardware or builds. The Spyke extract is a security screen, and the Linux build-document record returns 404, leaving neither as usable build guidance.
No legal assessment, security audit or explanation for 0x2593's archive event follows from these records. The decryption comments record participants' views rather than a finding about every game-file format. Rendered layout, accessibility and recommendation modules were outside this text revision. A useful next measurement would record the precise source revision, game version, host GPU, driver and stopping point, beginning with a toolchain that meets the checkout's declared CMake requirement.

