mirror_hot: only pools the CPU does not write go back to system memory

A pool read in place gives the GPU the game's bytes as they are when it reads them. The demoted pools were ones the
CPU refills every frame, which the game rewrote for the next frame while the replay and the GPU still drew the last:
small grass and moss flickered and slid over the ground, and with 0.8.0's mesh fallback every mesh flashed. Pools with
more than 64 KiB of CPU writes a frame (written pages and flushes) now stay mirrored.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Tobim6
2026-11-12 16:23:18 +01:00
parent 39db2ae2a1
commit ccd7fb14c2
2 changed files with 18 additions and 1 deletions

View File

@@ -105,6 +105,10 @@ static const char *const text_en[UI_TEXT_COUNT] = {
"its own. Fixes the teal splotches in Kokiri Forest's fog.",
[UI_MENU_LAMA_MIRROR_HOT] = "Pools copied every frame stay in system memory",
[UI_MENU_LAMA_MIRROR_HOT_DESC] = "A game memory pool whose copies to and from video memory each frame reach this "
"percentage of its size is read by the GPU from system memory instead, if the "
"CPU does not write it (a pool it refills each frame stays in video memory: read "
"in place, the GPU saw the next frame's data). For GPUs and buses short of "
"bandwidth; 25 suits an RX 580. 0: off.",
[UI_MENU_LAMA_RESERVE] = "Video memory kept free",
[UI_MENU_LAMA_RESERVE_DESC] = "Room kept free in each video memory heap for what FidelityFX (FSR 3.1, frame generation) and the "
"driver allocate on their own: a heap with less than this left takes no new allocation while "