Repository navigation
Releases
Lichii next build 2 (8bd0f84)
This build uses less memory, keeps video memory steady, and cuts the long freezes when you do
something for the first time. Tested with The Legend of Zelda: Ocarina of Time.
What's faster and lighter
- The game uses one shared copy of its compiled code instead of one per CPU core. Same frame rate,
and the hitch when a save first loads is much shorter. - Water ripples no longer jitter when the game runs at 60 fps.
- Changing the render scale on its own no longer turns on FSR. Pick FSR from its own setting.
- Memory the emulator frees is now handed back to the system, so long sessions stay smaller.
- On PCs with many CPU cores, the emulator uses less memory for its own bookkeeping.
- Shaders you are not using are dropped, so a scene you have left no longer keeps its memory.
- Video memory no longer climbs on its own. The same scene used to swing between 4 and 9 GB; it now
stays put. - When video memory is full, textures fall back to system memory instead of the game failing.
- Freeing video memory no longer stalls the frame. On NVIDIA under Linux this pause was 5 to 14 ms.
- Textures the game throws away are reused instead of allocated again. Ocarina was creating about 5
new images every frame. - Small render targets come from a shared pool instead of a fresh allocation each time.
- The saved shader cache is smaller.
- On a dedicated graphics card, textures stay in video memory instead of spilling into system
memory by mistake. - A low video memory target no longer throws away data the graphics card has written but the game
has not read back. This was losing data on small cards. - Depth effects are drawn at the size they really are, so they no longer come out scaled wrong.
Stutter
- A freeze of up to about 3 seconds while a shader the game needed sat in the compile queue is gone.
- The long freeze the first time you use something new is much shorter: 0.25 to 0.8 seconds
instead of 1.5 to 2.5. A first item use went from about 1.5 to about 0.3 seconds, bombs from 2.2
to 0.6, and entering a new area from about 2.5 to about 0.8. Measured with an empty shader cache;
each freeze happens once, after that the shader is in your cache.
New settings
- RAM Usage Mode (Graphics > Advanced). How many shaders stay loaded.
- Auto: 32 GB of memory or more keeps them all, 16 GB keeps about 3000, less keeps about 1200.
- High: keeps them all. No pop-in, most memory.
- Balanced: keeps about 3000.
- Low: keeps about 1200. Uses the least memory; a place you revisit can flicker for a moment.
- VRAM Usage (Graphics > Advanced). How much video memory the emulator keeps. Your old choice is
kept: Conservative is now Auto, Aggressive is now Unlimited.- Auto: 70 percent of what your card allows. On a 16 GB card that is about 10.5 GB.
- Unlimited: up to what the driver allows.
- 2 GB, 4 GB, 8 GB: fixed budgets. 4 GB measured about 4.2 GB. 2 GB does not reach 2 GB yet; the
game still needs about 3.5 GB.
Benchmarks
Ocarina of Time, the Market fountain, before this work and after.
| Before | After | |
|---|---|---|
| RAM, Low mode | 11340 MiB | 8762 MiB |
| RAM, High mode | 11340 MiB | 9729 MiB |
| Video memory, device peak | 5.7 to 7.1 GB | 3.9 to 4.1 GB |
| First use of an item (empty shader cache) | about 1.5 s | about 0.3 s |
| First bomb (empty shader cache) | 2.2 s | 0.6 s |
| Entering a new area (empty shader cache) | about 2.5 s | about 0.8 s |
| Hitch when a save first loads | 27 stutter frames | 9 |
How the RAM came down, step by step: handing freed memory back (11340 to 10942 MiB), fewer
allocator arenas (10902 to 10826, 76 MiB), smaller shader data and the game files unpacked once
(10829 to 10605, measured together), then the shared code cache and Low mode to 8762.
Measured on one PC: RTX 5080, Ryzen 9 9950X3D, Linux, in Ocarina of Time. Each number is the
median of 2 or 3 runs. Your results will differ.
Recommended settings
See the settings guide in the README: one short checklist per kind of PC, from a 4 GB graphics
card up to 32 GB of memory. On a 4 GB card (GTX 1050 Ti, GTX 1650, RX 570 4 GB), use the 1280x720
render scale and the 2 GB video memory target. That card was not tested directly: on our test PC
the game still needed about 4 GB at 1920x1080, which is why the smaller scale is recommended.
Games
- Donkey Kong Bananza runs at 60 fps on our test PC. The tutorial video shows visual artifacts.
The fix is already in upstream and arrives in the next release.
Known issues
- The first time you use something new, or enter an area for the first time, the game still pauses
briefly: 0.25 to 0.8 seconds per new effect (items, bombs, a new area), and new effects can pop in
a moment late. With an empty shader cache many of these come close together, so the first hour
feels rougher. It happens once per shader; afterwards it is cached. - ASTC Recompression: BC1 breaks textures in Ocarina of Time (dark faces, banding). Use BC3.
- AMD graphics cards run slower than NVIDIA here, and RDNA2 cards can lose the device. Not addressed
in this release. - FSR can silently fall back to the game's own rendering where FSR 3.1 is not supported.
- Switching to a build with different shaders recompiles them once. Recompiling on every launch is a
bug; report it if you see it.
Automatic build of next at 8bd0f84.
Linux
Linux packages come as an AppImage and a tar.gz. Both are self-contained and need glibc 2.39 or newer (Ubuntu 24.04, Fedora 40, Debian 13, Arch). The tar.gz holds the same files unpacked, for systems without FUSE: extract it and run lichii/lichii.
| Build Type | Standard | PGO (Recommended) | Notes |
|---|---|---|---|
| amd64 | AppImage · tar.gz | AppImage · tar.gz | Make the AppImage executable (chmod +x) and run it |
Windows
Windows packages are in-place zip files: extract and run lichii.exe, or eden-cli.exe from a terminal.
| Build Type | Standard | PGO (Recommended) | Notes |
|---|---|---|---|
| amd64 / x86_64 | zip | PGO zip | Both built with clang-cl and ThinLTO; the PGO zip adds a profile trained on Ocarina of Time |
macOS
The PGO builds are the same programs compiled with profile-guided optimization. Linux uses clang with Eglantine's profile; Windows uses clang-cl and ThinLTO with a profile trained in Lichii on Ocarina of Time, so other games gain less. Prefer them when your CPU supports it.
Lichii next build 1 (6f85ea7)
Automatic build of next at 6f85ea7.
Linux
Linux packages come as an AppImage and a tar.gz. Both are self-contained and need glibc 2.39 or newer (Ubuntu 24.04, Fedora 40, Debian 13, Arch). The tar.gz holds the same files unpacked, for systems without FUSE: extract it and run lichii/lichii.
| Build Type | Standard | PGO (Recommended) | Notes |
|---|---|---|---|
| amd64 | AppImage · tar.gz | AppImage · tar.gz | Make the AppImage executable (chmod +x) and run it |
Windows
Windows packages are in-place zip files: extract and run lichii.exe, or eden-cli.exe from a terminal.
| Build Type | Standard | PGO (Recommended) | Notes |
|---|---|---|---|
| amd64 / x86_64 | zip | PGO zip | Both built with clang-cl and ThinLTO; the PGO zip adds a profile trained on Ocarina of Time |
macOS
The PGO builds are the same programs compiled with profile-guided optimization. Linux uses clang with Eglantine's profile; Windows uses clang-cl and ThinLTO with a profile trained in Lichii on Ocarina of Time, so other games gain less. Prefer them when your CPU supports it.