From fb648acef9ca0c06918935f76c1c6189f7f8f733 Mon Sep 17 00:00:00 2001 From: chrg6 Date: Fri, 13 Nov 2026 17:53:38 -0500 Subject: [PATCH] Say where frame generation's acquire queue comes from when the graphics family has one queue. The review found vk_fg.cpp's header saying both of frame generation's queues come from another family that can present when the graphics family lacks them. vk_device.c create_device takes only the present queue from a family that can present; the acquire queue, which needs no capability, is a second queue of that family or of any other family, or the present queue itself when there is none. The header now says so. Comment only: vk_fg.cpp compiles, check_content passes. Co-Authored-By: Claude Opus 5.5 --- runtime/vk_fg.cpp | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/runtime/vk_fg.cpp b/runtime/vk_fg.cpp index 5765d762..c9c798f3 100644 --- a/runtime/vk_fg.cpp +++ b/runtime/vk_fg.cpp @@ -8,8 +8,9 @@ // vk_dlaa.c makes for DLSS and FSR 3.1 upscaling, and without an upscaler for frame generation alone (vk_dlaa.c // fg_only_frame: the same pass at the scene's size, no jitter). The HUD is kept out through the picture without it // (vk_dlaa.c hudless); the menu is not generated, since generation pauses while it is open. The device creates two more -// queues for it (vk_device.c create_device, vk_fg_queue_count): of the graphics family where it has them, else of -// another family that can present. +// queues for it (vk_device.c create_device, vk_fg_queue_count): of the graphics family where it has them; else the +// present queue comes from another family that can present, and the acquire queue is a second queue of that family or +// of any other, or the present queue itself when there is none. #ifdef _WIN32 #include #endif