Triforce v0.5.0

In-game mods (GameBanana browser, search and installs, with the Mask Salesman), code-patch and cheat mods, the devs' test18 to test45 work (full performance overlay, frame pacing on, steady frame rate, save export and import, bug capture, new options rows, Setup's Mods page and Add to Steam), occlusion queries and new defaults, Auto resolution that scales, replay helper threads and robust buffers off by default, the options in sections.
This commit is contained in:
ruckus7382sfgsgdf
2026-11-17 22:40:50 -06:00
parent 93eeb714c2
commit 6f338c8f56
600 changed files with 116254 additions and 2522 deletions

View File

@@ -29,3 +29,24 @@ It needs Vulkan headers but no GPU, SDK vendor runtime or game assets.
Injected failures in these tests do not prove actual driver OOM recovery or
device-loss handling. A successful game smoke validates integration, not a fault
injection into the player's GPU.
## AMD FSR 4's frame generation
The Frame generation row's AMD FSR 4 (`vk_fsr4.cpp`, `fsr4fg`) holds one frame generation context of AMD's library and
one image the made frame is written into. They follow the same rules:
- The image is made first, then the context; both are published together, only when both exist. A failure destroys
what was made, turns AMD's frame generation off for the session (the row then shows what runs, 2x by the renderer's
own interpolation) and is logged once. Nothing is retried per frame.
- A context is replaced (another picture size, a scene larger than it was made for, another kind of depth range) before
anything of the new frame is recorded: the queue and the device idle, AMD's context destroyed, then the image.
- A context that failed while a frame was being recorded stays until the second present after it, since that frame's
commands name it and are not on the queue yet; a context the row has left stays 120 presents. Both go at the
present's tick (`framegen_present_tick`), in the same order.
- At the process's exit (`HOS_OPT_EXITING`) nothing of AMD's is destroyed and nothing of it is called again: there is no
swapchain or thread of AMD's to stop, and the context goes with the process, as the upscaler's does.
The order is one function, `framegen_rows.h` `teardown`, which the real code and `tests/test_framegen_fsr4.py` both
run; the test also runs the real section against a stand-in for AMD's library and checks each of the cases above. It
does not prove what AMD's library or a driver does with these calls: nobody has run them on a card with FSR 4's frame
generation.