What is Lichii and why has it become viral?
Lichii is an experimental, open-source Nintendo Switch and Switch 2 emulator written in C++ that builds directly upon previous emulation efforts. It draws its foundation from Eglantine, Eden, yuzu, and Sudachi, preserving their previous contributions while actively developing renderer fixes and improving game compatibility. This independent fork operates entirely separate from official releases of those upstream projects and has no affiliation with Nintendo.
The repository has quickly captured attention in the open-source community, much like other viral developer tools such as gpu-unlock-ada, because it targets upcoming hardware generations. Its recent surge on GitHub reflects ongoing developer curiosity regarding next-generation console architectures and backward compatibility research.
What are the compatibility limits and reporting rules?
Compatibility, performance, and stability vary significantly depending on the specific game, underlying hardware configuration, and installed graphics drivers. Users should expect potential rendering errors, stutters, and occasional application crashes during testing sessions. Furthermore, passing automated software tests does not guarantee proper in-game rendering, and the project offers no universal frame-rate promises.
When submitting an issue report on the Eglantine issues page, contributors must include the exact build version, game version, CPU, GPU, and driver details alongside relevant settings and logs. It is strictly prohibited to upload proprietary game files, cryptographic keys, firmware data, or private user account details.
How do I install and configure the emulator?
Published software builds are hosted on the project's releases page, even though the repository retains its historical Eglantine name while the desktop application is named Lichii. On Windows systems, operators must extract the complete archive and execute the primary application binary directly.
Follow these steps to safely set up and run experimental builds on your desktop environment:
Download the latest build archive from the official repository releases page.
Extract the entire archive contents into a dedicated local directory on your machine, ensuring all runtime assets stay intact.