Home / Lichii troubleshooting

|Symptoms first · sources on each row

Lichii troubleshooting

Start from the symptom, not from a single setting. A driver popup, a black 3D world with the HUD still drawn, and a crash in one game are different problems. Updating a driver is the first line in the project troubleshooting note, and it is not a cure-all: issue 238 still showed that popup on a current RX 9070 XT driver.

Lichii mark

Symptom table

SymptomWhat is knownStatus
Black screenSeveral patterns: HUD-visible 3D black, full black with audio, init error, shader stallOwn page · multiple sources
Shader compile hitchBuild 83 moved compile off the foreground. Build 93 new configs default to async compile. New areas can still hitch2–3 sources
Missing or flashing texturesBuild 83 repaired some Ocarina vegetation and sky issues. Build 93 still lists AMD black textures, haze, and HUD flicker as openRelease notes plus reports
Crash in one gameOcarina issues 205, 209, 247; Mario Kart 234; other titles have single issues1 source each
Low frame rateOcarina CPU limit on issue 117; Intel Arc 8–10 fps; Steam Deck 8–9 fps on the title1–2 sources
ControllerSteam Deck ABXY mapping failed in one Ocarina report. Build 70 used HID 300 for controller input2 sources
Audio or green videoIssue 115 desync; issue 105 robot-like audio; issue 106 green AV1, closed1 source each
Stuck on exitBuild 88 fence-worker shutdown race; issue 222 Windows hang on build 832 sources
Linux shader load stallBuild 93 issue 290 says the initial Linux shader-load stall is a separate open problemRelease notes

What I will not tell you to do

I do not suggest turning off antivirus. The project notes do not say that. I also do not suggest a keys or firmware download. The README says the project does not supply them.

Logs live at File → Open Lichii Folders → Log Folder → eden_log.txt. That file is the useful attachment when you open a GitHub issue.

FAQ

Where do I start?

Match your symptom in the table. Black screens have their own page because the fixes depend on the pattern.

Does a closed issue mean it is fixed?

No. A later build can still show the same symptom. I keep the issue number either way.

Which driver should I install?

The project says to use the latest driver and, if needed, a clean removal. It does not name a version number I can repeat.

Sources

Checked 2026-11-07.