Turn the lazy write-back off by default and offer it in the settings menu as Experimental FPS boost.

With it on, single frames come out with the whole scene lit differently (brighter, shadows off). The flight recorder's
thumbnails of 1,800 presents standing in Hyrule Field show none with it off in every run, and with it on 43 to 181
while four other threads keep the CPU busy (10 to 97 in earlier runs, 0 on an idle machine); the cause is not found.
Two candidate fixes (arming only against a sync whose copies were handed over, and snapshots waiting for GPU writes in
flight) did not change the count, and fetching at every release made it far worse.

So wb_lazy is 0 unless set, on every platform (mem_init loses its special case), and the Screen tab has the row
Experimental FPS boost for it on Windows, with its text in the four menu languages; like every setting read at the
start it notes "after restart". The 0.7.0 notes describe it as experimental and off, say about 1.6 GiB for the video
memory a full shader cache no longer holds (2,484 to 846 MiB at the title screen in the measured run), and list the
two fixes before this one.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-10 07:12:23 -05:00
parent 71eb5fbe26
commit 9dbfed207f
8 changed files with 52 additions and 22 deletions

View File

@@ -1,5 +1,5 @@
A performance and feature release for *The Legend of Zelda: Ocarina of Time* for Nintendo Switch 2 (game version
1.1.1): a much higher frame rate in open areas and towns, less memory, DLSS Multi Frame Generation, save sharing, a
1.1.1): a higher frame rate in towns and less stutter, less memory, DLSS Multi Frame Generation, save sharing, a
launcher you can restyle, and many fixes. **No game files are included**: the setup builds the game on your PC from
your own dump.
@@ -21,11 +21,6 @@ cards).
## Faster
- **Open areas.** What the game's shaders write into its memory was copied back from the video card after every GPU
submission, in case the game's CPU code reads it: 66 MiB a frame in Hyrule Field, more than half of the frame's GPU
time. It is now copied once and after that only when the CPU touches it. Standing in Hyrule Field on our test PC
(RTX 5090, 3416x1440, DLAA) that is 76 fps instead of 57. `wb_lazy = 0` in `nx2navi.ini` brings the old behaviour
back; on Linux it is off unless you set `wb_lazy = 1`.
- **Towns.** Large towns release and take back thousands of textures a second, and every one made the game's texture
table look up about 10,000 entries again. A texture that comes back unchanged now leaves the table alone.
- **Every frame.** The wait after a frame's first GPU submission no longer includes the copy back to memory (3 to 4 ms
@@ -33,7 +28,13 @@ cards).
- **Less stutter.** Textures are created over several frames instead of all at once, shaders are read from the disk
off the render thread, a controller that connects or disconnects no longer stalls the game for 100 ms and more, and
DLSS Frame Generation no longer makes 100 to 150 ms frames after menus and cutscenes.
- **Less memory.** With a full shader cache the game holds about 1.7 GiB less video memory from the title screen on
- **Experimental FPS boost** (Screen tab of the settings menu, off by default, takes effect after a restart; `wb_lazy`
in `nx2navi.ini`). What the game's shaders write into its memory is copied back from the video card after every GPU
submission, in case the game's CPU code reads it: 66 MiB a frame in Hyrule Field, more than half of the frame's GPU
time. With the boost on it is copied once and after that only when the CPU touches it: standing in Hyrule Field on
our test PC (RTX 5090, 3416x1440, DLAA) that is 76 fps instead of 57. It is experimental because single frames of the
scene can flicker with it on, more when other programs keep the processor busy; tell us what you see if you try it.
- **Less memory.** With a full shader cache the game holds about 1.6 GiB less video memory from the title screen on
(twenty very large shaders the game never runs were created at every start), video memory blocks are smaller, DLSS
models that are not in use are freed, textures no shader has sampled for two minutes give way when memory runs low,
and textures give way before the game's buffers lose their place in video memory.
@@ -72,6 +73,12 @@ cards).
pass among them once its 50 ms were spent, and the frame was shown without it. Such a frame is no longer shown:
the previous picture stays for the frame or two it takes, while the game runs on (`frame_hold_ms`, 120 by default;
0 shows every frame as before).
- A dark or black flash when a DLSS or FSR 3.1 mode was picked in the settings menu. The game makes its scene images
again at the new size and the first frames drawn into them came out dark or black; the previous picture now stays
on screen for those few frames, with frame generation on as well.
- The ground, walls and buildings drawn black for the first second or seconds after a load screen (longer on a busy or
slower processor). An area's textures were made a few dozen a frame like textures that stream in during play; after a
load they are now made at once, before the area fades in.
- The performance overlay's VRAM line counted every program on the graphics card as if it were the game. It now
shows the game's own share beside it (*game 6.8 GB* of 10.4 GB in use, in one measurement).
- Textures that turned dark or blank for a moment: textures out of view were dropped after 11 seconds at 165 fps (30
@@ -114,9 +121,7 @@ cards).
- Integrated AMD GPUs can fail at the title screen (their host memory heap is too small for the game's memory).
- Opening the game's settings menu can crash on some AMD Radeon GPUs.
- A rare crash in the game's particle code.
- The new copy-on-touch of shader-written memory is the largest change in this release. If something behaves wrong
that did not before (physics, effects, a picture), set `wb_lazy = 0` in `nx2navi.ini`, and tell us whether that
cures it.
- With *Experimental FPS boost* on (off by default) single frames of the scene can flicker.
## For builders