Game: RX 7600 on Windows loses device entering world with native mesh shaders #1938

Open
opened 2026-11-20 23:33:58 +00:00 by BeanBot · 1 comment
Member

Reported on Discord

Longshot version

Longshot v3.0.0 stable (source 87cb36aa); also reproduced on v3.0.0-rc.7 and Hookshot v2.3.2.

Channel

Stable release.

What kind of problem

Crash / GPU device lost.

What happened

The game crashes every time when entering the playable world, whether starting a new game or loading any save. Menus and cutscenes work. RX_VK_NO_MESH=1 avoids the crash, but this disables mesh draws; RX_VK_MESH_OPT=1 did not help. On v3.0.0 with default settings and no environment file, the startup log reports native mesh shaders, and the crash remains.

The reporter observes GPU waits of about 14–16 seconds, followed by submit 58332 failed (-4) and VK_ERROR_DEVICE_LOST; the hang follows loading two 1365x1365x90-layer ASTC arrays, with mesh draw log lines shortly beforehand.

Where in the game

Loading into the playable world, for a new game or any save.

How often

Every attempt.

Graphics card and driver version

AMD Radeon RX 7600 (PCI ID 1002:7480), Windows 10; AMD proprietary drivers 26.10.1 and 26.11.2 (LLPC), same result.

CPU, RAM and operating system

Xeon E5-2667 v4, 48 GB DDR4, Windows 10.

Changes from the defaults

For the stable reproduction: no environment file and default settings. RX_VK_NO_MESH=1 is a workaround that avoids the crash, and RX_VK_MESH_OPT=1 was also tested without fixing it.

longshot_log.txt

Attached conversation log; startup reports vk: mesh shaders: Automatic, from the default: native and identifies AMD Radeon RX 7600. The reporter offered checkpoint-enabled logs if needed.

Longshot #583 tracked the analogous native-mesh device loss on Navi 23 / Windows for RX 6600 and was closed following PR #219. PR #219's default policy is specifically Navi 21–23? Its description and listed IDs cover RDNA 2/Navi 23; the RX 7600 is Navi 33 (RDNA 3), not covered by that default. PR #1650 extends the mesh-only routing policy only to Windows Navi 21–23. PR #1833 addresses long ASTC GPU upload submissions and WDDM TDRs on integrated GPUs; the reporter's GPU is a discrete RX 7600 and the log suggests native mesh routing, so its applicability is not established.

Expected

The game enters the world without losing the GPU, or a documented supported setting is available to select the compute fallback on this GPU while retaining mesh draws.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1573476833666539693/1573477995862294680) ### Longshot version Longshot v3.0.0 stable (source 87cb36aa); also reproduced on v3.0.0-rc.7 and Hookshot v2.3.2. ### Channel Stable release. ### What kind of problem Crash / GPU device lost. ### What happened The game crashes every time when entering the playable world, whether starting a new game or loading any save. Menus and cutscenes work. `RX_VK_NO_MESH=1` avoids the crash, but this disables mesh draws; `RX_VK_MESH_OPT=1` did not help. On v3.0.0 with default settings and no environment file, the startup log reports native mesh shaders, and the crash remains. The reporter observes GPU waits of about 14–16 seconds, followed by `submit 58332 failed (-4)` and `VK_ERROR_DEVICE_LOST`; the hang follows loading two 1365x1365x90-layer ASTC arrays, with mesh draw log lines shortly beforehand. ### Where in the game Loading into the playable world, for a new game or any save. ### How often Every attempt. ### Graphics card and driver version AMD Radeon RX 7600 (PCI ID 1002:7480), Windows 10; AMD proprietary drivers 26.10.1 and 26.11.2 (LLPC), same result. ### CPU, RAM and operating system Xeon E5-2667 v4, 48 GB DDR4, Windows 10. ### Changes from the defaults For the stable reproduction: no environment file and default settings. `RX_VK_NO_MESH=1` is a workaround that avoids the crash, and `RX_VK_MESH_OPT=1` was also tested without fixing it. ### longshot_log.txt Attached conversation log; startup reports `vk: mesh shaders: Automatic, from the default: native` and identifies AMD Radeon RX 7600. The reporter offered checkpoint-enabled logs if needed. ### Related issue Longshot #583 tracked the analogous native-mesh device loss on Navi 23 / Windows for RX 6600 and was closed following PR #219. PR #219's default policy is specifically Navi 21–23? Its description and listed IDs cover RDNA 2/Navi 23; the RX 7600 is Navi 33 (RDNA 3), not covered by that default. PR #1650 extends the mesh-only routing policy only to Windows Navi 21–23. PR #1833 addresses long ASTC GPU upload submissions and WDDM TDRs on integrated GPUs; the reporter's GPU is a discrete RX 7600 and the log suggests native mesh routing, so its applicability is not established. ### Expected The game enters the world without losing the GPU, or a documented supported setting is available to select the compute fallback on this GPU while retaining mesh draws.
Author
Member

Files from the Discord report:

Files from the Discord report: - [longshot_log.txt](https://git.magicbean.dev/attachments/4b25acec-d365-4929-93b5-d0c9b0fa982d)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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#1938
No description provided.