mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-16 09:39:58 -04:00
Merge the stutter fixes: a pipeline cache past 2 GB is read, the prepared shader list knows its seed, the pipeline cache is written only when it changed with a small file for what play adds, and a queued build a draw waits for goes first.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -155,6 +155,12 @@ keeps per-core data without locks and relies on that, so the host models it (`ru
|
||||
is built ahead only when a run has dispatched it: a pipeline of one holds about 100 MiB of device memory whether it
|
||||
is used or not, also after it is destroyed, and the list has about twenty of them that the game never dispatches
|
||||
(`runtime/vk_pipeline.c`, "compute pipelines the boot keeps").
|
||||
The pipeline cache is two files beside the game. `pipeline-cache.bin` holds what the preparation built and what
|
||||
earlier runs made; what a run compiles goes into `pipeline-cache-play.bin`, so one new pipeline in play writes a
|
||||
small file and not hundreds of megabytes. A cache is written only when its data grew. The small file is merged
|
||||
into the large one at a start once it reached `pipeline_cache_play_mb`, and by every preparation; the stage
|
||||
libraries the library warm builds in play go to the driver's own cache alone (`runtime/vk_pipeline.c`, "the play
|
||||
cache", `cache_save`).
|
||||
- The game's tensor-core upscaler is replaced by a decode-and-scale pass (`vk_tonemap.c`); `vk_fsr.c` runs AMD FSR 1
|
||||
(EASU, RCAS) on the present when the window is larger than the picture.
|
||||
- HDR (`vk_hdr.c`): the game tonemaps its scene into a float target, upscales it, draws the HUD into a second float
|
||||
|
||||
@@ -409,6 +409,15 @@ A change to the start's memory warning (`runtime/mem_need.h`, `runtime/memory.c`
|
||||
`python tests\mem_need_check.py [<game exe>]`, which builds the header alone and checks when the game's need counts
|
||||
as short. With the executable it also runs `--probe-memneed` (it prints the machine's commit and the answer and
|
||||
starts nothing) with `mem_need_mb` at 0, at 1 and at a value no machine has, and reads the warning line of the last.
|
||||
A change to how `pipeline-cache.bin` is read (`runtime/vk_cache_file.h`, `runtime/vk_pipeline.c` `cache_load`) passes
|
||||
`python tests\pipeline_cache_file_check.py`, which builds the header alone and reads a sparse file just over 2 GB
|
||||
through it: measured and read whole without a size limit, refused by its real size under one. No game files, no GPU;
|
||||
about 2 GB of memory for a few seconds.
|
||||
|
||||
A change to the layout of `shader-prepared.bin` (`runtime/prp_file.h`, `runtime/gfx_shader.c`
|
||||
`gfx_shader_prepare_seed`, `tools/make_game.py` `prepared_from`) passes `python tests\prp_file_check.py`, which builds
|
||||
the header alone, checks the parse of both versions and has `make_game.py` read the list the C side wrote. No game
|
||||
files, no GPU.
|
||||
|
||||
A change to where the lazy write-back is on by default (`runtime/wb_lazy_choice.h`, `runtime/vk_memory.c`
|
||||
`vk_mem_lazy_decide`) passes `python tests\wb_lazy_check.py`, which builds the header alone and checks the choice and
|
||||
|
||||
@@ -263,7 +263,11 @@ The stub swaps `python.next` in while no Python runs, then starts the new versio
|
||||
game files are already unpacked builds on from them as well (`jobs.InstallJob.args`).
|
||||
7. **Prepare the Shaders** is skipped once shaders were prepared before (`shader-prepared.bin`): the game keeps using
|
||||
them and translates them again with the new translator in the background (`NX2NAVI_SHADER_CARRY`). With
|
||||
`shader_carry = 0`, or nothing prepared yet, the step prepares them all as at the install. The step still builds
|
||||
`shader_carry = 0`, or nothing prepared yet, the step prepares them all as at the install. So it does when the
|
||||
list was prepared from another shader seed than the one this kit writes: `shader-prepared.bin` carries the digests
|
||||
of the two seed files and the translator identity (`runtime/prp_file.h`), the step writes the seed first
|
||||
(`prepare_shaders.py --no-run`, seconds) and compares (`make_game.py` `seed_changed`); a list from before it
|
||||
recorded its seed is prepared again once. Another translator alone does not prepare again. The step still builds
|
||||
the prepared shaders into the graphics driver's cache again (`make_game.py` `warm_driver_cache`): seconds while
|
||||
the driver has them, 20 minutes on a player's PC when the update changed what they are built with. Its bar
|
||||
follows that count from 0 to 100 %, and the Updates row says an update takes from a few minutes to half an hour
|
||||
|
||||
Reference in New Issue
Block a user