Video memory: every VMA allocation by the heaps' live budgets, with room kept for FidelityFX

The heap limits were fixed at device creation, and only texture images looked at the budget. FidelityFX allocates
outside VMA (FSR 3.1 contexts, frame generation): 882 MiB of it with 4644 MiB of VMA's filled the 5526 MiB budget of
heap 0 while heap 2 had 1757 MiB free, and an upload submit failed with VK_ERROR_OUT_OF_DEVICE_MEMORY. vmaCreateImage,
vmaCreateBuffer and vmaAllocateMemory now go through vk_vma_budget.c, which leaves out a device-local heap whose
driver-reported use is within NX2NAVI_VRAM_RESERVE_MB (default 512) of its budget; a Lama patches row sets it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Tobim6
2026-11-12 16:23:16 +01:00
parent 81cdd67086
commit 39db2ae2a1
6 changed files with 149 additions and 0 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 "
[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 "
"another heap can. Off: video memory can fill up with frame generation on, and the game ends.",
[UI_MENU_LAMA_HEAP_LIMIT] = "Video memory heap limit",
[UI_MENU_LAMA_HEAP_LIMIT_DESC] = "Auto: on GPUs with a second video memory heap (an RX 580 shows 6 GB and 2 GB), "
"each heap is filled only to its budget before the next one is used, so the "