mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-15 19:19:58 -04:00
cde143c5d9
The review of 9071dfc3 found that nx2navi.ini.example, cfg.c's metas comment, the commit message and docs/architecture.md said the rollback switch works "as up to 0.10.1", which it does not exactly. With 1, every place that lets something go waits for the device again, C-5's queue-lock hazard with it, but what was let go of still goes through vk_dlaa.c's list and vk_memory.c's deferred destruction, the motion vectors and the HUD-less picture keep their 8-present gate, vk_upscaler_settle leaves what the submission being recorded names, stale_sizes waits once per call, and a refused DLSS creation with features let go of still listed waits and tries again, where 0.10.1 turned DLAA off. Each difference is the safer side. The ini line now says that the game waits at each change as up to 0.10.1 while what was let go of still goes once the card is past it; cfg.c, vk_dlaa.c's "what the upscalers let go of" and docs/architecture.md say the same. Comments and docs only. Checks that passed: cfg_rows_check (0 problems), upscaler_idle_check, cfg.c and vk_dlaa.c compile with -Wall -Wextra and no warning, tools/check_content.py --staged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>