Zelda's new Switch 2 remake already has an experimental PC emulator update built around a familiar promise: smoother gameplay. Published on November 6, 2026 at 09:07 UTC, Lichii build 88 integrates Dark's Dynamic FPS modification for The Legend of Zelda: Ocarina of Time, enabled by default for the supported game build.
But the developer's warning is just as important as the feature: this is not a guaranteed 60 FPS unlock, and correct gameplay speed across different frame rates remains unverified. Build 88 also changes Vulkan pipeline caching, GPU synchronization and FSR3 interpolation. Here is what those changes actually mean for players.
Our previous GameLogNews report covered Lichii build 75 finally reaching gameplay despite rendering problems. This follow-up tackles a different question: can the game keep the right timing while the emulator's performance fluctuates?
What is Dynamic FPS actually doing?
A high frame-rate counter and correctly paced gameplay are not automatically the same thing. Some game routines assume particular frame intervals; simply rendering extra frames can affect movement speed, animations or timing.
According to Lichii's implementation notes, Dark's routine reads an elapsed-time counter, smooths changes and selectively adjusts the frame-step calculation. It caps the measured interval at 50 milliseconds, limiting how much a long frame can influence the result.
Those decisions make the routine more controlled, but they are also why it cannot promise perfect speed at every FPS. The documentation says the original game step still acts as a floor in part of the calculation, and full gameplay timing needs live verification.
A short clip displaying 60 FPS in a quiet scene therefore tells us little about how combat, cutscenes and long sessions behave.
Enabled by default, but not for every version of the game
Pull request #240, merged on November 6, bundles “Dynamic FPS by Dark (built-in)” under Ocarina of Time's Add-Ons. It is on by default. Players can switch it off independently of Max Resolution, another built-in add-on.
Dynamic FPS addresses timing. Max Resolution affects presentation. Turning off one does not automatically turn off the other.
The patch is also deliberately restricted to the supported main executable. Before applying it, the emulator checks the original instruction bytes, available executable padding, timer memory and possible conflicts with user modifications. An incompatible game update should not be patched blindly.
Those safeguards matter because a visible checkbox does not prove the patch supports every revision of the remake. The routine was written by Dark; Frizti integrated it, and Lichii credits both contributors.
Why CPU Clock: Normal matters
The build-88 release notes specifically recommend CPU Clock: Normal when evaluating Dynamic FPS. Boost and Overclock can alter the timing counter that Dark's routine relies on.
Lichii's documentation explains the risk: if the counter no longer represents elapsed time consistently, the routine's attempt to adjust game speed may itself be distorted. A setting that helps one aspect of emulation can interfere with another.
That is why “more CPU clock” is not necessarily “better Dynamic FPS.” Results should be compared with the emulator build, game version, GPU, scene and clock settings clearly documented.
No legitimate testing claim can be made from a screenshot of an FPS overlay alone. GameLogNews has not independently benchmarked build 88.
Vulkan improvements target the work between frames
Beyond the Zelda-specific mod, Lichii integrated reviewed performance work from contributor Frizti. The release describes cached storage-buffer bindings, direct uploads of eligible uniform-bank data and batched GPU command-page readbacks.
Other changes reduce redundant tracking and can submit native desktop GPU work earlier while preserving synchronization checks. The Vulkan cache moves to version 53, with support for migrating compatible version-52 data. Some graphics pipelines can also be prepared in bounded background tasks.
These are meaningful engineering improvements: spending less CPU time preparing graphics work can reduce stalls or overhead. But the changelog does not contain a controlled, universal before-and-after FPS test for Zelda. Promising a particular percentage gain on every PC would be speculation.
Don't confuse Dynamic FPS with FSR3
Build 88 also repairs FSR3 frame-generation handling, including temporal history, motion interpolation, image transitions and resource retirement. FSR3 frame generation is still disabled by default.
The distinction is crucial. Dynamic FPS attempts to change how the game advances its timing. Frame generation creates additional displayed frames between rendered frames; it does not make the game itself simulate more quickly or automatically fix input latency.
The underlying performance and FSR3 changes passed technical checks, but their contributors did not claim a fully validated gameplay-wide FPS increase.
What is still missing?
Lichii's release heading explicitly says AMD fixes will be in the next build. That means they are not part of build 88. Hardware and scene differences continue to matter.
The team also documents an existing fence-worker shutdown race that can leave the emulator hanging when closing. It was reproduced during testing and remains unresolved by this release.
The Dynamic FPS integration PR reports a strict test run of 760 passing cases, including checks for patch compatibility and saved add-on preferences. That supports the implementation's safety checks, not the claim that every boss fight now runs smoothly at exactly the intended speed.
| Build 88 feature | What is confirmed |
|---|---|
| Zelda Dynamic FPS | Enabled by default on the supported build |
| Max Resolution | Separate, independently switchable add-on |
| Stable 60 FPS | Not established |
| FSR3 frame generation | Fixes included, off by default |
| Vulkan cache / pipeline work | Included; impact varies by hardware |
| AMD-specific fixes | Planned for a later build |
| Shutdown race | Still unresolved |
The next benchmark should be about game speed
For emulator enthusiasts, the speed of development is impressive. One day after the remake's Switch 2 release, Lichii's conversation has advanced from merely rendering Hyrule to controlling frame timing and removing GPU overhead.
But the most useful future demonstration will be repeatable gameplay across different scenes with correct simulation speed, documented settings and stable visuals—not the highest number an overlay briefly shows.
Nintendo's official remake remains a Switch 2 game; Lichii is an experimental community emulator, not an authorized Windows port. The official Nintendo artwork illustrating this story is not an emulator screenshot.
Dynamic FPS appearing this quickly is news. Proving it makes the whole adventure play correctly will be the real breakthrough.
Source date: November 6, 2026