mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-20 06:09:58 -04:00
Turn the lazy write-back on by default on Windows and take its row out of the settings menu.
The user asked for this once the flicker fix was measured. The single-frame flicker that kept it off in 0.7.0 came from frames drawn before the game's signal that their data was written, which the previous commit fixes; the lazy write-back only made the frames come faster, so the signal fell into the replay more often. wb_lazy = 0 in nx2navi.ini still turns it off, and an ini that already holds the key keeps its value. Elsewhere than Windows the default stays 0, as its fetch inside the access-fault handler has never run there. Measured on the build of the previous commit, 1,800 presented frames a run, standing in Hyrule Field by day with DLSS Performance, frame generation 4x and HDR. With the lazy write-back on and eight busy threads beside the game: 38 and 0 single-frame spikes with the fix switched off (408 and 44 frames whose signal came during the replay), 0 and 0 with it on (667 and 724 such frames). With it off and the same load: 0 spikes in four runs, two with the fix and two without, 86 to 140 such frames each. Without load, one run each: 88.5 frames a second with the fix against 93.3 without it with the lazy write-back on (GPU 7.2 against 6.8 ms a frame, 6.53 against 6.48 submissions a frame), 71.0 against 65.6 with it off, so the fix's cost is inside the run-to-run spread; every run ended cleanly without a fatal error. This build was started once with no setting anywhere: the lazy write-back was on, and the Screen tab shows no row for it. Not measured: play by hand with the lazy write-back on and the fix (the user's sessions so far ran with it off), other areas than Hyrule Field, and more than one run for the frame rates. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -684,12 +684,11 @@
|
||||
# first submission ends when that submission's passes are through, without waiting for the copy back (3 to 4 ms of
|
||||
# every frame). 0: the copy back is part of the submission, and the wait covers it.
|
||||
# wb_split = 1
|
||||
# 0: what the game's shaders write into its memory is copied back from the video card at the end of every GPU
|
||||
# submission. 1 (experimental): copied back once, and after that only when the game's CPU code touches it (most of it
|
||||
# never is: 66 MiB a frame in Hyrule Field), for about a third more frames a second in open areas. With 1, single
|
||||
# frames of the scene can flicker; tell us what you see if you try it. In the settings menu: Experimental FPS boost
|
||||
# (Screen tab). With shadow storage (Linux, Wine) it stays off.
|
||||
# wb_lazy = 0
|
||||
# 1 (the default on Windows): what the game's shaders write into its memory is copied back from the video card once,
|
||||
# and after that only when the game's CPU code touches it (most of it never is: 66 MiB a frame in Hyrule Field), for
|
||||
# about a third more frames a second in open areas. 0: copied back at the end of every GPU submission, as in 0.7.0.
|
||||
# With shadow storage (Linux, Wine) it stays off.
|
||||
# wb_lazy = 1
|
||||
# Linux, shadow storage: 1 clears the write watch's protection of a range in one call before the GPU's bytes are copied
|
||||
# back into the game's memory, instead of taking a fault at the first store into each page.
|
||||
# shadow_bulk_write = 0
|
||||
|
||||
Reference in New Issue
Block a user