mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-19 15:09:58 -04:00
Tell a start that was closed or stopped during the boot's builds from a driver crash, and limit the whole warm.
A marker or a journal left by a start that died in the boot's builds was always read as a driver crash. Since the whole warm those builds run for minutes, so a start ended from outside in that time (the task manager, a program that stops the game, the power) switched the pipeline prebuild off for that driver for good, or put up to 32 variants on the skip list that the driver had merely been building. Closing the window was already an orderly end and still is. The crash handler now leaves a note while the boot's builds run. With the note the next start does what it did: it skips the prebuild, or the variants the journal names. Without it the end is taken for a stopped start: the pipelines are built again and the journal's variants are blamed on nothing. Three such ends in a row still skip the prebuild, for a driver that ends the process without a fault the handler sees. The boot's journal has a file of its own, so the preparation's keeps its meaning. The whole warm waits prewarm_full_s seconds at most (600): when they are up the game starts, the builders step down to the background's thread counts and priority, and the file says "done", so the boot screen has one turn per driver. tests\boot_warm_check.py covers what a leftover marker means with and without the note. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -474,7 +474,8 @@ as short. With the executable it also runs `--probe-memneed` (it prints the mach
|
||||
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 when a start does the whole warm on the boot screen (`runtime/boot_warm.h`, `runtime/vk_pipeline.c`
|
||||
`bf_decide`) passes `python tests\boot_warm_check.py`, which builds the header alone: the warm after a driver change,
|
||||
its continuation by a later start, the end of the tries, and no second warm once one is done. The warm itself shows
|
||||
its continuation by a later start, the end of the tries, no second warm once one is done, and what a marker left by
|
||||
a start that ended in the boot's builds means with and without the crash handler's note. The warm itself shows
|
||||
in `--probe-prewarm` on a copy of an install's caches whose `pipeline-cache.bin` has another driver's header (bytes
|
||||
8 to 15 of the file are the vendor and device ids, the 16 after them the driver's cache id): the log names the whole
|
||||
warm, the compute pipelines on every core and the library warm's answer, and `boot-warm-owed.txt` ends as "done".
|
||||
|
||||
Reference in New Issue
Block a user