Which symptom are you actually seeing?
Start with a screenshot, a repeatable scene and a short description. Missing textures, wrong lighting, motion trails and delayed sound are not interchangeable bugs. A fix for one may have no effect on another.
The Ocarina texture report #808 describes corrupted textures and missing face textures after the opening cutscene on a specific setup. It is a community report, not proof that every graphics card has that problem.
| Symptom | Record before changing anything |
|---|---|
| Missing or corrupted textures | Build, exact GPU, driver, scene and screenshot |
| Bright sky or incorrect lighting | The area, time or scene, settings and whether it repeats |
| Trails around moving effects | Whether an upscaler replacement is enabled and which release introduced the symptom |
| Audio behind the picture | Whether gameplay is also slow, the scene and audio settings |
| Black screen or driver reset | Whether the app remains responsive and what the log says |
What do the DLSS trail notes apply to?
The build 117 release notes mention white streaks or trails at night around effects such as Navi, fireflies and smoke in Ocarina of Time. For that release, they advise turning off Use NVIDIA DLSS in place of a game’s DLSS under Emulation → Configure → Graphics while a fix is tested.
That is a release-specific recommendation for a named feature and symptom. Check the current notes before following it. Do not assume it is relevant when the option is absent, the GPU is different, or the problem is texture corruption rather than trails.
How should you isolate the cause?
- Preserve the current log, screenshot and settings.
- Read the release notes for the build you actually use.
- Search issues using the game, GPU and symptom rather than only “Lichii broken.”
- Change one relevant option, then return to the same scene.
- Compare the output and stability as well as FPS. Restore the original setting if there is no useful improvement.
If you are using mods or patches, record them. A test without add-ons can be a useful comparison, but back up data and do not delete the only copy of your files.
What if audio is out of sync?
Observe whether the picture is also running slowly, whether the problem starts in a movie or gameplay, and whether it continues in a repeatable scene. A slow rendering path and an audio configuration error need different investigation; the reviewed sources do not prove that all audio desync has one cause.
Use low FPS diagnosis when the whole game is slow. Use the intro crash guide for a driver reset or failure during the movie-to-3D transition. Keep the exact timestamp and log for a reproducible bug report.
Where should you report an unresolved issue?
Search the official issue tracker for duplicates and provide build, OS, GPU, driver, game version, settings and steps to reproduce. Check logs for personal data first. Do not attach games, keys or firmware.
Return to the Ocarina guide for the broader test sequence or compatibility reports to compare a matching setup. The concept artwork on this site should never be used as a visual target for the emulator: it is not rendered gameplay.