Selevet Eglantine: the tuned single-machine build
Latest release
selevet-eglantine-performance-9prerelease Published 2026-11-06· 1 package below
Copies a prompt your AI agent can run to install Selevet Eglantine.
Which package should I choose?
One Windows x86_64 zip per release, published as a prerelease. The current one is performance build 9, extracted and run as selevet.exe. Settings are built in, so setup is keys, firmware and a controller mapping. The repository's tuned README documents what every build changed.
| Package | Architecture | Size |
|---|---|---|
| selevet-eglantine-performance-9-windows-x86_64.zip ↗ | x86_64 | 24.1 MB |
What this build needs
A CPU with AVX2 (the build targets x86-64-v3 and exits on older chips), the current Microsoft Visual C++ x64 runtime, and your own dumped keys, firmware and games. One machine is the tested baseline, named in the tuned README: a Ryzen 5 5500 with an RTX 3050 and 16 GB of RAM.
Getting started
Match your CPU
The build is tuned for Zen 3 CPUs. On other hardware the standard Eglantine build is the documented choice.
Get a build
Download a prerelease from the upstream GitHub releases page.
Keep saves separate
When testing a tuned build against a main install, keep save data apart so the tuned build cannot disturb it.
Check for updates
This directory records the project as no longer maintained, so verify the upstream repository for anything newer.
Common problems
-
The build exits at launch
It is compiled for x86-64-v3, so CPUs without AVX2 will not run it. Use the upstream build it is based on, or compile from source with your own flags.
-
Other Eden or Eglantine builds slow down afterward
This build shares %APPDATA%\eden\config and marks your settings as default when it saves, so the next build reads them as its own. Back that folder up before switching, or create an empty user folder beside the exe for separate data and place keys and firmware there.
-
A game logs a panic (2162-0001 or 2010-0212) and keeps running broken
The cause is not fully known. Restart the build. After stopping a game, check Task Manager for a windowless selevet.exe or eglantine.exe still holding memory.
-
A black screen when entering races
Turn Sync memory operations back on first. The tuned README names it as the suspect on the older builds of this line.
How it differs
Selevet Eglantine is a single-maintainer tuning fork of the Eglantine line, built for one game on one documented PC, with no stable tag and a repository marked no longer maintained. Its later builds merged Ocarina of Time support from Lichii branches. The tuned README records what each merge cost.
Recent upstream releases
- Selevet Eglantine performance build 9 ↗ prerelease Published 2026-11-06 · 1 package
See every release on the upstream page ↗
Last checked 2026-11-22. Release data fetched 2026-11-22. A release sync refreshes metadata from upstream; it does not re-verify compatibility.
Download FAQ
Why is everything a prerelease?
The project publishes tuned builds of a fork under development and tags nothing stable, and the repository itself is marked no longer maintained.
Which build runs which game?
The tuned README walks each one: later builds merged Ocarina of Time support and its speed-ups, while an earlier build kept fixes those builds dropped. The notes name the trade in both directions.
Before installing
- Do not share the shader cache: vulkan.bin contains game code.
- The build reads its switches from nx2_switches.txt beside the exe
- remove the unsafe preemption line if glitches appear.
- Report problems to this repository, not to the upstream projects: the tuned README asks reporters to keep them off those trackers.