Read the tag and the boundary of the change
- Tag and revision
- For example, build-130 identifies a release built from commit 3dae119. A feature merged on the development branch after that commit requires a release that actually includes it.
- What changed
- Find the game, graphics path or problem that matters to you in the release notes. A speed improvement measured at Kokiri in Ocarina of Time says little about a crash at a different transition.
- What comes next
- Build 130 lists some work under Coming next. Items in that section describe future work. Check the notes for a later tag before looking for those features in the application.
Read the fixed build 130 release notesBrowse other release tags
Preserve a working installation
- Stop the game and back up its save directory to a separate location. Keep any controller profiles or custom settings you depend on. Lichii can share its user data folders with earlier builds.
- Keep the old package and give the new one its own program folder or filename. Write down the previous build, game update, driver and one short scene you can reproduce.
- Read the new tag’s migration notes. Build 130 introduced shader cache v2. For that migration, the project directs you to right-click each affected game and select Remove → Remove All Pipeline Caches once. Read the confirmation for the selected game.
That cache instruction belongs to this particular shader-cache change. A pipeline cache can be rebuilt during play. Your save holds your progress, so verify which item is selected before confirming.
Build 130 cache migration instructionsProject notes on retained user data
Compare the same scene and keep a way back
Launch the new copy and confirm the build identifier. Load your comparison scene with the same settings and driver. After a cache rebuild, record the first pass separately from a second trip through the same area. The first pass may include extra shader compilation.
If the scene now fails, close the new build and reopen your retained older application. Confirm its build and repeat the same steps. Preserve any newer save separately before restoring a backup. A result that follows the build on repeated runs gives a developer a narrower regression report.
Release updates FAQ
A fix appears on GitHub. How can I tell if it is in my download?
Check the tag and revision on the release you downloaded and look for the fix in its notes. A merged change may be newer than the tagged build. Items listed as Coming next were outside the release being described.
Should I clear every game’s pipeline cache whenever I update?
Follow the instructions for the specific upgrade. Build 130 called for a one-time reset for each affected game when moving to shader cache v2. That instruction alone does not establish a cache reset for a later update.
Why might the first pass through a scene stutter more after the build 130 cache reset?
The first pass can include rebuilding shaders. Repeat the same route on the same build and record both passes separately before comparing them with your previous results.