Merge GitHub main into the 0.7.0 release line: uniform blocks copied at the submit call with the replay on its own thread, the overlay's frame times measured where the pictures go out, and early pictures kept back.

The two commits main gained since the last merge. docs/releases/v0.6.2.md stays removed; the two notes they added to
it are in docs/releases/v0.7.0.md. Checked on a dev build of the merged tree: the settings, self-test, graphics ABI,
input and kernel probes pass, and a scripted run with six DLSS mode changes presents no dark or black frame, makes the
area's textures in one frame at the load and ends without a fatal error.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-10 07:17:01 -05:00
9 changed files with 199 additions and 19 deletions

View File

@@ -81,6 +81,18 @@ cards).
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).
- The performance overlay's frame rate, lows and frame-time graph are now those of the pictures as they reach the
screen. They were measured at the game's present calls, which come in uneven steps although the pictures do not: in
a village the calls came 36 and 9 ms apart in turn and the graph drew a sawtooth with a 1% low of 14 fps, while the
pictures went out about 20 ms apart and changed by 4 ms from one to the next. A picture that arrives early now also
waits until seven eighths of the recent interval have passed (`pace_smooth`, on by default; not with frame
generation), which brought that change down to 3 ms at the same frame rate.
- *GPU frame prep on its own thread* (`replay_async`, off by default): the shader constants of a frame are now
copied when the game hands the frame over, not when the other thread gets to it up to a frame later, by which time
the game had sometimes reused that memory (a shadow pass got another block's values about every 364 frames in one
graveyard). The option can still show a dark or flickering frame: vertex, storage and index data are read late in
the same way, and this game rewrites them without waiting for the GPU. The menu says so now. It gave 15 to 18
percent more frames per second in a graveyard and a village.
- Textures that turned dark or blank for a moment: textures out of view were dropped after 11 seconds at 165 fps (30
seconds were meant) and came back as a stand-in for a few frames. The wait is two minutes of real time at any frame
rate now, and the scene's textures are kept through a pause.