MagicBeanDev/Longshot

Watch

Fork 98

RX 6600 (Navi 23, Windows): device lost in Dodongo's Cavern with native mesh shaders, compute fixes it #583

New issue

Open

opened 2026-11-14 20:39:13 +00:00 by ferblaz · 2 comments

ferblaz commented

2026-11-14 20:39:13 +00:00

Longshot version

v3.0.0-rc.3

Channel

Release candidate

What kind of problem

Crash, freeze or black screen

What happened

With the default mesh shader mode ("Automatic, from the default: native"),
the game reliably loses the GPU a few seconds after entering Dodongo's Cavern
(child). The log shows "the GPU has finished nothing for 10 s", then
"submit failed (-4)", "device fault: No fault detected" and
VK_ERROR_DEVICE_LOST. VRAM was not the issue (about 5.2 of 7.4 GB used).
Before the hang there are capture write-back timeouts and memory sync
stalls of 185-250 ms.

Workaround that works:
RX_VK_MESH_SHADERS=compute in longshot_env.txt. With it I played most of
Dodongo's Cavern with no crash and a clean exit (avg ~47 fps).

Notes:

RX_VK_NO_MESH=1 also avoids the crash but leaves much of the scene missing.
mesh_shaders=2 in longshot_options.ini is ignored (the log says it is no longer read).
The README says RX 6000 cards (Navi 21 and 22) default to the compute
fallback on Windows. Navi 23 seems to be missing from that list and still
defaults to native. Could Navi 23 be added to the compute default?

Logs attached:, one good session with compute.

Where in the game

Dodongo's Cavern

How often

Every time

Graphics card and driver version

GPU: AMD Radeon RX 6600 (Navi 23) Driver: AMD Adrenalin 26.11.1 (clean install after DDU)

CPU, RAM and operating system

OS: Windows Longshot: v3.0.0-rc.3 (source cb01b5a3) RAM: 16 GB ryzen 5 2600x

Changes from the defaults

RX_VK_MESH_SHADERS=compute

longshot_log.txt

longshot_log

Screenshots or video

No response

Before you send it

The problem is still there on the newest release or nightly.
I searched the open issues for it.
I'm not attaching game files, keys, the game's executable, its .bin caches or saves.

### Longshot version v3.0.0-rc.3 ### Channel Release candidate ### What kind of problem Crash, freeze or black screen ### What happened With the default mesh shader mode ("Automatic, from the default: native"), the game reliably loses the GPU a few seconds after entering Dodongo's Cavern (child). The log shows "the GPU has finished nothing for 10 s", then "submit failed (-4)", "device fault: No fault detected" and VK_ERROR_DEVICE_LOST. VRAM was not the issue (about 5.2 of 7.4 GB used). Before the hang there are capture write-back timeouts and memory sync stalls of 185-250 ms. Workaround that works: RX_VK_MESH_SHADERS=compute in longshot_env.txt. With it I played most of Dodongo's Cavern with no crash and a clean exit (avg ~47 fps). Notes: - RX_VK_NO_MESH=1 also avoids the crash but leaves much of the scene missing. - mesh_shaders=2 in longshot_options.ini is ignored (the log says it is no longer read). - The README says RX 6000 cards (Navi 21 and 22) default to the compute fallback on Windows. Navi 23 seems to be missing from that list and still defaults to native. Could Navi 23 be added to the compute default? Logs attached:, one good session with compute. ### Where in the game Dodongo's Cavern ### How often Every time ### Graphics card and driver version GPU: AMD Radeon RX 6600 (Navi 23) Driver: AMD Adrenalin 26.11.1 (clean install after DDU) ### CPU, RAM and operating system OS: Windows Longshot: v3.0.0-rc.3 (source cb01b5a3) RAM: 16 GB ryzen 5 2600x ### Changes from the defaults RX_VK_MESH_SHADERS=compute ### longshot_log.txt [longshot_log](/attachments/fe9851c5-37a2-4264-8ee6-1f041c2645fa) ### Screenshots or video _No response_ ### Before you send it - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.

longshot_log.txt

6.1 MiB

ferblaz added the

kind

bug

label

2026-11-14 20:39:13 +00:00

ferblaz changed title from ~~Game: Ocarina of time~~ to RX 6600 (Navi 23, Windows): device lost in Dodongo's Cavern with native mesh shaders, compute fixes it

2026-11-14 20:42:39 +00:00

ferblaz commented

2026-11-14 20:45:38 +00:00

Author

Crash log with native mesh shaders attached (same machine, v3.0.0-rc.3). Possibly related: #422 (RX 6700 XT, GPU timeout in Dodongo's Cavern).

longshot_log_native_crash.txt

197 KiB

BeanIssues commented

2026-11-15 09:59:28 +00:00

Collaborator

From sincerity on Discord:

Additional report: the same AMD mesh-shader GPU timeout occurs on Linux. The reporter says compute mode is the default there; removing the longshot_env.txt override they had created restores compute mode and works around the issue.

From [sincerity on Discord](https://discord.com/channels/1569849200047427645/1569849200617726065/1571463980348604427): Additional report: the same AMD mesh-shader GPU timeout occurs on Linux. The reporter says compute mode is the default there; removing the `longshot_env.txt` override they had created restores compute mode and works around the issue.