Merge GitHub main into the 0.7.0 release line: frames that lack draws are held back, and the overlay shows the game's own video memory.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-10 05:37:45 -05:00
11 changed files with 132 additions and 6 deletions

View File

@@ -145,6 +145,10 @@ of them.
93 ms (vertex) and 242 ms (fragment) on average against 0.3 and 0.6 ms from the cache, and a first walk through a
village skipped 11,180 draws and made 94 draws wait 5.5 s in all, against 1,605 skipped (1,473 of them in the
scene's first frames) and 60 ms of waits with the cache warm.
A frame that still lacks draws when it is presented is not shown: the previous picture stays on screen
(`runtime/vk_backend.c` `frame_hold`, `NX2NAVI_FRAME_HOLD_MS`, an allowance of 120 ms that fills again at an eighth
of the clock's rate). On a first walk through a village with nothing recorded, 21 of the 23 such frames were held
back; in a player's session a hit by a boulder had shown one black frame, its lighting pass skipped after 50 ms.
When the driver's shader compiler crashes on a variant (NVIDIA 615.78.08 on an RTX 5080 does, issue #30),
`prepare_shaders.py` runs the driver step again with `--warm-shaders`, up to three times, without the variants the
driver was building at the crash. `shader-prepare-skip.txt` next to the exe lists them with the GPU and driver

View File

@@ -67,6 +67,13 @@ cards).
where it also ends the 20 second start). The game now checks the driver's cache at every start and fills it again
in the background by itself, an update fills it again before you play, draws wait a moment for a pipeline that only
needs linking instead of being left out, and lighting passes are no longer left out at all.
- A black or unlit frame, or a light or a piece of ground missing for a frame, when something new came on screen (a
hit, a new effect, a new enemy). A draw whose pipeline was not ready in time was left out of that frame, a lighting
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).
- 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
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.