Fritchii v6.5: which file to take and what it changes
Latest release
fritchii-v6.5Published 2026-11-21· 3 packages below
Copies a prompt your AI agent can run to install Fritchii.
Which package should I choose?
A release carries Fritchii-v6.5-Windows-x64.zip and Fritchii-v6.5-Linux-x86_64.AppImage (or the tar.gz of the same build), and its notes name the file to take. Installs from version 4 through 6.2 offer the update when they open, so an existing copy needs no fresh download. Anything older unzips anywhere and runs fritchii.exe from the extracted folder. A small lichii.exe stays beside it so old shortcuts keep working. The Source code archives on a release page contain no emulator.
| Package | Architecture | Size |
|---|---|---|
| Fritchii-v6.5-Linux-x86_64.AppImage ↗ | x86_64 | 124.3 MB |
| Fritchii-v6.5-Linux-x86_64.tar.gz ↗ | x86_64 | 133.9 MB |
| Fritchii-v6.5-Windows-x64.zip ↗ | x86_64 | 71.6 MB |
What this build needs
A Windows x64 or Linux x86_64 machine with current GPU drivers. Prepared shaders ship with the release, so first runs skip most shader compilation, and cards with 4 to 8 GB of video memory keep sampled textures instead of re-uploading them, which is why small cards need no extra settings.
Getting started
Pick your asset
Each release tag carries a Windows x64 zip and Linux x86-64 AppImage and tar.gz assets. Match the asset to your host.
Get a build
Download from the upstream GitHub releases page. The debug-symbols archive in each tag is not needed to play, as its asset name states.
Configure
The fork inherits the Lichii codebase, so the upstream lineage documentation is the reference for configuration.
Read the release notes
The README is minimal upstream, so check each tag's notes before updating.
Common problems
-
First start asks whether to use the recommended settings
Use recommended applies the configuration tuned per game and per GPU family and saves a copy of your old settings first. Keep my settings changes nothing, and you can switch later in Settings.
-
Frame rate on an Intel hybrid CPU sits near half of what you expect
Version 6.1 pinned GPU threads to P-cores. Since 6.2 Windows places them, and Fritchii disables a leftover EDEN_HYBRID_CORES=0 line on first start. If it is still halved, uncomment that line in Tools > Switches.
-
A crash on an AMD Radeon card
The extra GPU thread was disabled by a stale vertex buffer read, fixed in 6.5. Make sure you actually took the file the release notes name rather than a Source code archive.
How it differs
Fritchii is the tuning fork in the Eglantine line: its own prepared shader sets, the Ocarina-focused occlusion speed-up with variants built in the background, and per-GPU adjustments upstream does not ship. Selevet Eglantine tunes the same lineage differently, for a single documented machine.
Recent upstream releases
- Fritchii v6.5 ↗ Published 2026-11-21 · 3 packages
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
Do I need to download every release?
From version 4 to 6.2 no, the build offers the update when it opens. Only older installs or a move to another machine need the zip.
What exactly are the recommended settings?
The maintainer's per-game and per-GPU configuration, including the occlusion speed-up on AMD Radeon cards. Applying it saves your current settings first, so trying it is reversible.
Is Frizti/Lichii the same as Lichii?
No. Lichii is zortos293's emulator and Fritchii is Frizti's fork of it, described upstream as a game-specialized fork. The former Frizti/Lichii repository name redirects to the Fritchii repository, so a link carrying that name opens this project, not the original. Lichii's own releases, and its compatibility site at lichii.zortos.me, remain separate.
Before installing
- Extract into a fresh folder rather than over an old build, since settings and prepared shaders live beside the executable.
- Leave the lichii.exe companion file in place
- deleting it breaks old shortcuts.
- In-app updates keep saves and settings where they were, so no manual copy is needed for them.