Game: RX 7600 on Windows loses device entering world with native mesh shaders #1938
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1938
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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=1avoids the crash, but this disables mesh draws;RX_VK_MESH_OPT=1did 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)andVK_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=1is a workaround that avoids the crash, andRX_VK_MESH_OPT=1was also tested without fixing it.longshot_log.txt
Attached conversation log; startup reports
vk: mesh shaders: Automatic, from the default: nativeand 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.
Files from the Discord report: