mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-18 04:49:57 -04:00
Keep the previous picture on screen instead of showing a frame that lacks draws, and show the game's own VRAM in the overlay.
A draw whose shader or pipeline is still building is left out of its frame, and the frame was shown without it: a black or unlit picture with the interface intact when it was a lighting pass, a light going out, or ground missing for a frame. In a player's session a full-screen draw was skipped after its 50 ms and the frame came out black as a boulder hit. The frame's present is now left out when draws were skipped (vk_backend.c frame_hold, NX2NAVI_FRAME_HOLD_MS, 120 by default, 0 off). The game runs on, so nothing waits. The hold comes from an allowance that fills again at an eighth of the clock's rate, so a long build or a run of them shows its frames as before and does not freeze the picture; a full-screen draw that would be skipped with the allowance spent waits on instead, 500 ms at most. Not with DLSS Frame Generation. On a first walk through a village with no pipeline recorded, 21 of the 23 frames with skipped draws were held back; in the Lost Woods, 7 of 8. The performance overlay: the VRAM line is the card's dedicated memory in use, which counts every program on it: a player read 14.5 GB as the game's while the game held 7.3 GB. The line's third cell now gives what this process holds on the device-local heaps (the driver's budget figure), in place of the GPU clock, which stays where the driver gives no budget. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -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
|
||||
|
||||
@@ -22,6 +22,13 @@ Draft notes for the release after 0.6.1. The version number is not decided yet.
|
||||
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 out of view for 11 seconds at 165 fps (30 seconds were meant) could show a blank stand-in for a few frames
|
||||
when they came back while memory was short. The wait is now two minutes of real time at any frame rate.
|
||||
- Settings menu, mouse: a setting changes only on the two framed arrows beside its value, and the arrows stay in one
|
||||
|
||||
Reference in New Issue
Block a user