fix(vk): the presents' own queue is opt-in again: RX_VK_PRESENT_QUEUE=1 #1549

Merged
llun merged 2 commits from pmwork-personal/Longshot:fix/present-queue-opt-in into main 2026-11-18 04:53:39 +00:00
Member

Type: fix · Risk: low · Tested on: Windows 11, RTX 5090 (NVIDIA 621.24), the queue choice only (see Testing) · Needs: the tester's RTX 5080 on the first nightly with it; #1491's RTX 5080

TL;DR

Since #1476, NVIDIA's driver 621.24 and newer on Windows put the presents on a GPU queue of their own by default. A tester's
RTX 5080 then lost the GPU seconds after frame generation started, at 2x and 3x, with every maker and V-Sync mode, and at
every start with frame generation saved; with RX_VK_PRESENT_QUEUE=0 the crashes stopped. This PR makes that queue
opt-in again, as before #1476: RX_VK_PRESENT_QUEUE=1 turns it on. The cost: with V-Sync Off and a fixed frame
generation multiplier, made frames bunch up again on the screen unless a player sets that line.

Breakdown

  • Who it helps: players on NVIDIA cards whose GPU is lost with frame generation on (an RTX 5080 confirmed; #1491
    another RTX 5080 that looks the same).
  • What was wrong: the presents' compute queue loses the GPU on some cards with frame generation on (a fault never
    placed; Hookshot issue 1161 gave an RTX 4090 a black screen with it, before the fork); #1476 made it the default.
  • What changes: create_device takes the compute family only when RX_VK_PRESENT_QUEUE asks for it, on every PC.
  • What does not change: #1476's other parts (the switch's yes/no rule, the device-lost message naming =0 while the
    queue is on, DLSS Frame Gen's exit wait on the queues' own locks); with =1 everything as on main; Linux, AMD and Intel
    (off already); saves, settings and caches.
  • How it was checked: a game-free check that compiles the queue choice and fails on main; the queue-off path in the
    game on an RTX 5090 and, by the tester, on his RTX 5080.
  • What is still open: this branch's own build on the tester's PC; #1491's answer.
  • Risk: low for stability (the path main had before #1476). The cost: on an RTX 5090 at V-Sync Off and 3x, a third of
    the made frames reach the screen under 2 ms after the one before without the queue, 0.1% or less with it; each
    present's call to the screen 6.6 ms instead of 1.3 (#1476's runs). RX_VK_PRESENT_QUEUE=1 keeps that where it works.

Why

The tester (RTX 5080, NVIDIA 621.24, 1920x1080 at 360 Hz, Reflex On, V-Sync Auto) lost the GPU with frame generation on
from nightly-458 (#1476) on: at 3x (fixed for the overlay's part in #1536), then on nightly-469 at 2x as well, with
Built-in FG under mailbox (5 s after every start, the replay's queue done to its last checkpoint, so the fault was not
there) and with DLSS FG under FIFO; 11 crash and unclean-end records in a day. With frame generation off the queue ran on
his PC for minutes. With RX_VK_PRESENT_QUEUE=0 in longshot_env.txt his crashes stopped. #1491 (another RTX 5080 on
621.24, DLSS FG 2x, HDR) loses the GPU at the start-up logo since nightly-458 ("455 works") and was asked to try =0.

Reported by null (nullifyshot) on Discord, with logs, crash records and the =0 test.

See #1476, #1491, #1536, #1362.

How to reproduce

Seen on: Windows 11 build 26300, RTX 5080, NVIDIA 621.24, 1920x1080 at 360 Hz (the tester; nightly-464 and
nightly-469)
Settings and switches: Frame generation 2x or 3x (Built-in FG, or DLSS FG), V-Sync Auto, NVIDIA Reflex On; no
RX_VK_PRESENT_QUEUE; main 9af4808f
Steps: save Frame generation at 2x and start the game; or in play, set Frame generation to 2x or 3x in the Insert menu.
Expected: the game runs.
Actual: vk: FATAL: the GPU device was lost, seconds later. With RX_VK_PRESENT_QUEUE=0, the game runs.

What changed

The presents' compute queue is off by default on every PC again; RX_VK_PRESENT_QUEUE=1 turns it on.

  • gpu/vk/vk_main.cpp create_device: no NVIDIA driver default; the switch decides, by the switches' yes/no rule. The
    comment says why, with the history.
  • gpu/vk/switches.def: RX_VK_PRESENT_QUEUE is an attempt again (off on every PC).
  • docs/development.md, docs/design.md section 13 rule 5, README.md: opt-in, why, and what it gives on an RTX 5090;
    rule 6 and the development guide's row say that #1476's and #1496's recorded runs had the queue on (the default then).
  • tests/test_present_queue_default.py: cuts the queue choice out of create_device, Windows branch included, compiles
    it and asks which family it takes for NVIDIA 621.14, 621.24 and 630 and AMD, with the switch unset, empty, on and off.
    Fails on main: "NVIDIA, the switch unset: family 2, expected -1".

Measurements

Verdict: fixed on the tester's RTX 5080 by the same queue choice (his =0 run); this branch's build was not run on
his PC. The cost on an RTX 5090 is #1476's own numbers, the other way round.

Hardware: the tester's Windows 11 build 26300, RTX 5080, NVIDIA 621.24, AMD Ryzen 9 9900X3D, 61 GB; for the cost, Windows 11
Pro build 26300, RTX 5090, NVIDIA 621.24, AMD Ryzen 7 9800X3D, 64 GB
Scene: the tester's: the start-up screen and Hyrule Market (child), 1920x1080 at 360 Hz, Frame generation 2x and 3x
(Built-in FG, DLSS FG), V-Sync Auto, Reflex On; the cost: Hyrule Market (child), 5120x2160 at 165 Hz with G-Sync, DLSS
Frame Gen 3x, V-Sync Off
Method: the tester's crash reports and logs on nightly-469 (main 9af4808f) without the switch, then his play with
RX_VK_PRESENT_QUEUE=0 (the queue choice this PR makes the default); the cost from #1476's PresentMon runs (two a side,
interleaved: docs/tested/2026-11-17-present-queue-default-vsync-off-*)
Baseline: the tester ran main's nightly with and without the switch, not this branch's build (he builds nightlies only),
and =0 on main is exactly this PR's default; the cost columns are #1476's own before and after, which this PR undoes
How to reproduce: the settings above; RX_VK_PRESENT_QUEUE=0 in longshot_env.txt beside longshot.exe for the After
column; for the cost, #1476's method (PresentMon 2.x --process_name longshot.exe --timed 30, DisplayedTime)

Before: main @ 9af4808f (nightly-469) After, the same queue choice (RX_VK_PRESENT_QUEUE=0): main @ 9af4808f
the tester's RTX 5080, frame generation 2x and 3x the GPU lost: 5 s after each start with 2x saved; ~20 s after DLSS FG 2x no crash (his report)
an RTX 5090, 165 Hz G-Sync, DLSS Frame Gen 3x, V-Sync Off (#1476's runs) Before: main @ 415a8944 (queue off, as this PR) After: #1476 @ b897bc79 (queue on, as main)
made frames on the screen under 2 ms after the one before 33.0-33.7% 0.0%
each present's call to the screen, median 6.5-6.7 ms 1.3 ms
(the tester, nightly-469, Built-in FG 2x saved, 5 s after the start)
vk: presents on a queue of their own, of compute family 2 (RX_VK_PRESENT_QUEUE=0: off)
vk: swapchain 1920x1080, 6 images, mailbox (V-Sync Auto)
vk: device lost: 2 checkpoints (225 markers set)

Flags and settings

One switch changes its default: RX_VK_PRESENT_QUEUE.

Flag What it is Before this PR After this PR Effect Helps / doesn't help / untested Recommendation
RX_VK_PRESENT_QUEUE env, renderer (attempt) on with NVIDIA's driver 621.24+ on Windows (hw) off on every PC; =1 on the presents on a compute family's queue of their own helps: even frames with V-Sync Off on an RTX 5090; doesn't help: RTX 5080 (the GPU lost), RTX 4090 (a black screen) off; =1 where it is known to run

Testing

Tested:

  • The queue choice this PR makes the default, in the game: on Windows 11, RTX 5090, NVIDIA 621.24, main 310e7c9d with
    RX_VK_PRESENT_QUEUE=0, Built-in FG 2x, 3x and 4x at V-Sync Auto (mailbox), the start-up screen and the title, about
    2.5 minutes: no device lost (docs/tested/2026-11-17-overlay-frees-title-main-pq0-pmwork-personal-run01.md); and the
    tester's RTX 5080 on nightly-469 with RX_VK_PRESENT_QUEUE=0: no crash.
  • tests/test_present_queue_default.py passes here and fails on main. python -I -B tests/run_all.py on the branch before
    its last rebase (aa1bf65e, Windows, llvm-mingw clang 23): 665 passed, 55 failed, 50 skipped; each of the 55 also fails
    on main (the newest two, test_capture_readback_visibility and test_present_source_crop, run on main's tree here; none
    reads a file this PR changes).

Not testable by hand: the tester's RTX 5080 and #1491's.

Not tested: this branch's own build in the game (the queue choice is the one above); Linux, AMD and Intel (off before
and after).

Must be tested:

  • The tester's RTX 5080: the first nightly with this, without RX_VK_PRESENT_QUEUE, Frame generation 2x and 3x, a start
    and a few minutes in play, expecting no device lost (by hand: the reporter).
  • #1491's RTX 5080: the first nightly with this, Frame generation 2x by DLSS FG with HDR as saved, a start, expecting no
    device lost (by hand: the reporter, asked on the issue).

Risks

What could break: frame generation's pacing with V-Sync Off on cards where the queue worked (an RTX 5090): made frames
bunch on the screen again unless RX_VK_PRESENT_QUEUE=1 is set. Stability: none known; this is main's path before #1476.

Turning it off: RX_VK_PRESENT_QUEUE=1 brings the queue back, per PC.

Compatibility: Nothing changes: saves, longshot_options.ini, caches and the vk ABI as before.

Issues

See #1476, #1491, #1536, #1362

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what
    can't be run by hand is in Testing's Not testable by hand, with why.
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and
    in Risks.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value.
  • A check under tests/ that reads changed source updated in this PR, not weakened.
  • A game-free test added for the fix, failing on main and passing here.
  • Docs updated.

🤖 Generated with Claude Code

Assisted-by: Claude Code
Co-Authored-By: Claude Opus 5.5 [email protected]

**Type:** fix · **Risk:** low · **Tested on:** Windows 11, RTX 5090 (NVIDIA 621.24), the queue choice only (see Testing) · **Needs:** the tester's RTX 5080 on the first nightly with it; #1491's RTX 5080 ## TL;DR Since #1476, NVIDIA's driver 621.24 and newer on Windows put the presents on a GPU queue of their own by default. A tester's RTX 5080 then lost the GPU seconds after frame generation started, at 2x and 3x, with every maker and V-Sync mode, and at every start with frame generation saved; with `RX_VK_PRESENT_QUEUE=0` the crashes stopped. This PR makes that queue opt-in again, as before #1476: `RX_VK_PRESENT_QUEUE=1` turns it on. The cost: with V-Sync Off and a fixed frame generation multiplier, made frames bunch up again on the screen unless a player sets that line. ## Breakdown - **Who it helps:** players on NVIDIA cards whose GPU is lost with frame generation on (an RTX 5080 confirmed; #1491 another RTX 5080 that looks the same). - **What was wrong:** the presents' compute queue loses the GPU on some cards with frame generation on (a fault never placed; Hookshot issue 1161 gave an RTX 4090 a black screen with it, before the fork); #1476 made it the default. - **What changes:** `create_device` takes the compute family only when `RX_VK_PRESENT_QUEUE` asks for it, on every PC. - **What does not change:** #1476's other parts (the switch's yes/no rule, the device-lost message naming `=0` while the queue is on, DLSS Frame Gen's exit wait on the queues' own locks); with `=1` everything as on main; Linux, AMD and Intel (off already); saves, settings and caches. - **How it was checked:** a game-free check that compiles the queue choice and fails on main; the queue-off path in the game on an RTX 5090 and, by the tester, on his RTX 5080. - **What is still open:** this branch's own build on the tester's PC; #1491's answer. - **Risk:** low for stability (the path main had before #1476). The cost: on an RTX 5090 at V-Sync Off and 3x, a third of the made frames reach the screen under 2 ms after the one before without the queue, 0.1% or less with it; each present's call to the screen 6.6 ms instead of 1.3 (#1476's runs). `RX_VK_PRESENT_QUEUE=1` keeps that where it works. ## Why The tester (RTX 5080, NVIDIA 621.24, 1920x1080 at 360 Hz, Reflex On, V-Sync Auto) lost the GPU with frame generation on from nightly-458 (#1476) on: at 3x (fixed for the overlay's part in #1536), then on nightly-469 at 2x as well, with Built-in FG under mailbox (5 s after every start, the replay's queue done to its last checkpoint, so the fault was not there) and with DLSS FG under FIFO; 11 crash and unclean-end records in a day. With frame generation off the queue ran on his PC for minutes. With `RX_VK_PRESENT_QUEUE=0` in `longshot_env.txt` his crashes stopped. #1491 (another RTX 5080 on 621.24, DLSS FG 2x, HDR) loses the GPU at the start-up logo since nightly-458 ("455 works") and was asked to try `=0`. Reported by null (nullifyshot) on Discord, with logs, crash records and the `=0` test. See #1476, #1491, #1536, #1362. ## How to reproduce **Seen on:** Windows 11 build 26300, RTX 5080, NVIDIA 621.24, 1920x1080 at 360 Hz (the tester; nightly-464 and nightly-469) **Settings and switches:** Frame generation 2x or 3x (Built-in FG, or DLSS FG), V-Sync Auto, NVIDIA Reflex On; no `RX_VK_PRESENT_QUEUE`; main 9af4808f **Steps:** save Frame generation at 2x and start the game; or in play, set Frame generation to 2x or 3x in the Insert menu. **Expected:** the game runs. **Actual:** `vk: FATAL: the GPU device was lost`, seconds later. With `RX_VK_PRESENT_QUEUE=0`, the game runs. ## What changed The presents' compute queue is off by default on every PC again; `RX_VK_PRESENT_QUEUE=1` turns it on. - `gpu/vk/vk_main.cpp` `create_device`: no NVIDIA driver default; the switch decides, by the switches' yes/no rule. The comment says why, with the history. - `gpu/vk/switches.def`: `RX_VK_PRESENT_QUEUE` is an `attempt` again (off on every PC). - `docs/development.md`, `docs/design.md` section 13 rule 5, `README.md`: opt-in, why, and what it gives on an RTX 5090; rule 6 and the development guide's row say that #1476's and #1496's recorded runs had the queue on (the default then). - `tests/test_present_queue_default.py`: cuts the queue choice out of `create_device`, Windows branch included, compiles it and asks which family it takes for NVIDIA 621.14, 621.24 and 630 and AMD, with the switch unset, empty, on and off. Fails on main: "NVIDIA, the switch unset: family 2, expected -1". ## Measurements **Verdict:** fixed on the tester's RTX 5080 by the same queue choice (his `=0` run); this branch's build was not run on his PC. The cost on an RTX 5090 is #1476's own numbers, the other way round. Hardware: the tester's Windows 11 build 26300, RTX 5080, NVIDIA 621.24, AMD Ryzen 9 9900X3D, 61 GB; for the cost, Windows 11 Pro build 26300, RTX 5090, NVIDIA 621.24, AMD Ryzen 7 9800X3D, 64 GB Scene: the tester's: the start-up screen and Hyrule Market (child), 1920x1080 at 360 Hz, Frame generation 2x and 3x (Built-in FG, DLSS FG), V-Sync Auto, Reflex On; the cost: Hyrule Market (child), 5120x2160 at 165 Hz with G-Sync, DLSS Frame Gen 3x, V-Sync Off Method: the tester's crash reports and logs on nightly-469 (main 9af4808f) without the switch, then his play with `RX_VK_PRESENT_QUEUE=0` (the queue choice this PR makes the default); the cost from #1476's PresentMon runs (two a side, interleaved: `docs/tested/2026-11-17-present-queue-default-vsync-off-*`) Baseline: the tester ran main's nightly with and without the switch, not this branch's build (he builds nightlies only), and `=0` on main is exactly this PR's default; the cost columns are #1476's own before and after, which this PR undoes How to reproduce: the settings above; `RX_VK_PRESENT_QUEUE=0` in `longshot_env.txt` beside `longshot.exe` for the After column; for the cost, #1476's method (PresentMon 2.x `--process_name longshot.exe --timed 30`, `DisplayedTime`) | | Before: main @ 9af4808f (nightly-469) | After, the same queue choice (RX_VK_PRESENT_QUEUE=0): main @ 9af4808f | |---|---|---| | the tester's RTX 5080, frame generation 2x and 3x | the GPU lost: 5 s after each start with 2x saved; ~20 s after DLSS FG 2x | no crash (his report) | | an RTX 5090, 165 Hz G-Sync, DLSS Frame Gen 3x, V-Sync Off (#1476's runs) | Before: main @ 415a8944 (queue off, as this PR) | After: #1476 @ b897bc79 (queue on, as main) | |---|---|---| | made frames on the screen under 2 ms after the one before | 33.0-33.7% | 0.0% | | each present's call to the screen, median | 6.5-6.7 ms | 1.3 ms | ``` (the tester, nightly-469, Built-in FG 2x saved, 5 s after the start) vk: presents on a queue of their own, of compute family 2 (RX_VK_PRESENT_QUEUE=0: off) vk: swapchain 1920x1080, 6 images, mailbox (V-Sync Auto) vk: device lost: 2 checkpoints (225 markers set) ``` ### Flags and settings One switch changes its default: `RX_VK_PRESENT_QUEUE`. | Flag | What it is | Before this PR | After this PR | Effect | Helps / doesn't help / untested | Recommendation | |---|---|---|---|---|---|---| | `RX_VK_PRESENT_QUEUE` | env, renderer (attempt) | on with NVIDIA's driver 621.24+ on Windows (hw) | off on every PC; `=1` on | the presents on a compute family's queue of their own | helps: even frames with V-Sync Off on an RTX 5090; doesn't help: RTX 5080 (the GPU lost), RTX 4090 (a black screen) | off; `=1` where it is known to run | ## Testing **Tested:** - The queue choice this PR makes the default, in the game: on Windows 11, RTX 5090, NVIDIA 621.24, main 310e7c9d with `RX_VK_PRESENT_QUEUE=0`, Built-in FG 2x, 3x and 4x at V-Sync Auto (mailbox), the start-up screen and the title, about 2.5 minutes: no device lost (`docs/tested/2026-11-17-overlay-frees-title-main-pq0-pmwork-personal-run01.md`); and the tester's RTX 5080 on nightly-469 with `RX_VK_PRESENT_QUEUE=0`: no crash. - `tests/test_present_queue_default.py` passes here and fails on main. `python -I -B tests/run_all.py` on the branch before its last rebase (aa1bf65e, Windows, llvm-mingw clang 23): 665 passed, 55 failed, 50 skipped; each of the 55 also fails on main (the newest two, test_capture_readback_visibility and test_present_source_crop, run on main's tree here; none reads a file this PR changes). **Not testable by hand:** the tester's RTX 5080 and #1491's. **Not tested:** this branch's own build in the game (the queue choice is the one above); Linux, AMD and Intel (off before and after). **Must be tested:** - The tester's RTX 5080: the first nightly with this, without `RX_VK_PRESENT_QUEUE`, Frame generation 2x and 3x, a start and a few minutes in play, expecting no device lost (by hand: the reporter). - #1491's RTX 5080: the first nightly with this, Frame generation 2x by DLSS FG with HDR as saved, a start, expecting no device lost (by hand: the reporter, asked on the issue). ## Risks **What could break:** frame generation's pacing with V-Sync Off on cards where the queue worked (an RTX 5090): made frames bunch on the screen again unless `RX_VK_PRESENT_QUEUE=1` is set. Stability: none known; this is main's path before #1476. **Turning it off:** `RX_VK_PRESENT_QUEUE=1` brings the queue back, per PC. **Compatibility:** Nothing changes: saves, longshot_options.ini, caches and the vk ABI as before. ## Issues See #1476, #1491, #1536, #1362 ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what can't be run by hand is in Testing's Not testable by hand, with why. - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. - [x] A game-free test added for the fix, failing on `main` and passing here. - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Assisted-by: Claude Code Co-Authored-By: Claude Opus 5.5 <[email protected]>
test_present_queue_default now cuts create_device's queue choice out, Windows branch included, compiles it and asks which
family it takes: with the switch unset, none, for NVIDIA's driver 621.24 and newer too; =1 (any on value) the first compute
family without graphics; =0 none; none with no such family. The device-lost message and DLSS Frame Gen's exit wait keep
their text checks; the switch's rows are an attempt, off on every PC.

Fails on main: with NVIDIA's driver 621.24 or newer and the switch unset it takes the compute family (#1476). A tester's
RTX 5080 on 621.24 lost the GPU with frame generation on and the queue on (2x and 3x), and the crashes stopped with
RX_VK_PRESENT_QUEUE=0; #1491, another RTX 5080, looks the same.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Assisted-by: Claude Code
fix(vk): the presents' own queue is opt-in again: RX_VK_PRESENT_QUEUE=1
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 7s
PR description / Description follows the template (pull_request_target) Successful in 9s
Website / Website on Cloudflare (pull_request_target) Has been skipped
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 9s
CI / Workflow lint (actionlint) (pull_request) Successful in 11s
Third-party parts / As their notes say (pull_request) Successful in 11s
bc516279da
#1476 made the presents' compute queue the default with NVIDIA's driver 621.24 and newer on Windows. A tester's RTX 5080 on
621.24 then lost the GPU seconds after frame generation started (2x and 3x, Built-in FG and DLSS FG, mailbox and FIFO, 5 s
after every start with it saved; the replay's queue done to its last checkpoint), while frame generation off ran on the
queue, and the crashes stopped with RX_VK_PRESENT_QUEUE=0. #1491, another RTX 5080 on 621.24 (DLSS FG 2x, HDR, from
nightly-458 on), looks the same. Hookshot issue 1161 (an RTX 4090 on 621.14, a black screen) had it turned off in v2.0.9,
a fault never placed.

create_device takes the compute family only when RX_VK_PRESENT_QUEUE asks for it (the switches' yes/no rule), on every PC.
#1476's other parts stay: the switch's yes/no rule, the device-lost message that names =0 while the queue is on, and DLSS
Frame Gen's exit wait on the queues' own locks. The switch's row is an attempt again; docs/development.md, design.md section
13 rule 5 and the README say it is opt-in, why, and what it gives on an RTX 5090; rule 6 and the development guide's row say
that #1476's and #1496's recorded runs had the queue on.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Assisted-by: Claude Code
Author
Member

Tested in game: This branch's own build was not run in the game. The queue choice it makes the default (the presents on the replay's queue, as RX_VK_PRESENT_QUEUE=0 on main) was: Windows 11 Pro 26300, RTX 5090, NVIDIA 621.24, 5120x2160 at 165 Hz, main 310e7c9d with RX_VK_PRESENT_QUEUE=0, Built-in FG 2x, 3x and 4x at V-Sync Auto (mailbox), the start-up screen and the title for about 2.5 minutes: no device lost (docs/tested/2026-11-17-overlay-frees-title-main-pq0-pmwork-personal-run01.md). And by the reporter: RTX 5080, NVIDIA 621.24, Windows 11 26300, nightly-469 with RX_VK_PRESENT_QUEUE=0, frame generation on: no crash, where without it the GPU was lost at 2x and 3x.

Tested in game: This branch's own build was not run in the game. The queue choice it makes the default (the presents on the replay's queue, as RX_VK_PRESENT_QUEUE=0 on main) was: Windows 11 Pro 26300, RTX 5090, NVIDIA 621.24, 5120x2160 at 165 Hz, main 310e7c9d with RX_VK_PRESENT_QUEUE=0, Built-in FG 2x, 3x and 4x at V-Sync Auto (mailbox), the start-up screen and the title for about 2.5 minutes: no device lost (docs/tested/2026-11-17-overlay-frees-title-main-pq0-pmwork-personal-run01.md). And by the reporter: RTX 5080, NVIDIA 621.24, Windows 11 26300, nightly-469 with RX_VK_PRESENT_QUEUE=0, frame generation on: no crash, where without it the GPU was lost at 2x and 3x.
llun scheduled this pull request to auto merge when all checks succeed 2026-11-18 04:53:29 +00:00
llun approved these changes 2026-11-18 04:53:37 +00:00
llun merged commit 79d4a14362 into main 2026-11-18 04:53:39 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!1549
No description provided.