MagicBeanDev/Longshot

Watch

Fork 99

Game: Longshot keeps crashing at launch #278

New issue

Open

opened 2026-11-13 19:11:13 +00:00 by arukod · 7 comments

arukod commented

2026-11-13 19:11:13 +00:00

Longshot version

nightly-80-7315957c (source cdf3d9d8)

Channel

Nightly

What kind of problem

Crash, freeze or black screen

What happened

I click on Play in the launcher, window opens up, it says it's loading pipelines/shaders but then it closes automatically.
I'm on the latest AMD Drivers 26.10.1

Where in the game

At launch

How often

Every time

Graphics card and driver version

RX 9060XT

CPU, RAM and operating system

Ryzen 7 7700, 32GB DDR5, Windows 11 26H2

Changes from the defaults

On Discord I've been told to add this is inside longshot_env.txt, I didn't have this file so I created it:

RX_VK_MESH_SHADERS=compute

longshot_log.txt

Here are the logs.

Screenshots or video

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 nightly-80-7315957c (source cdf3d9d8) ### Channel Nightly ### What kind of problem Crash, freeze or black screen ### What happened I click on Play in the launcher, window opens up, it says it's loading pipelines/shaders but then it closes automatically. I'm on the latest AMD Drivers 26.10.1 ### Where in the game At launch ### How often Every time ### Graphics card and driver version RX 9060XT ### CPU, RAM and operating system Ryzen 7 7700, 32GB DDR5, Windows 11 26H2 ### Changes from the defaults On Discord I've been told to add this is inside longshot_env.txt, I didn't have this file so I created it: RX_VK_MESH_SHADERS=compute ### longshot_log.txt Here are the logs. ### Screenshots or video ![Screenshot 2026-11-13 201402](/attachments/e2d181b0-f8a8-46b7-9200-000e65230079) ### 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

13 KiB

longshot_log.1.txt

11 KiB

arukod added the

kind

bug

label

2026-11-13 19:11:13 +00:00

arukod commented

2026-11-13 20:46:59 +00:00

Author

Built it again, for the third time I think, with v3.0.0-rc.3, keeps crashing.

longshot_log.txt

11 KiB

Screenshot 2026-11-13 214422.png

85 KiB

mooki added the

gpu/amd

platform/windows

labels

2026-11-14 18:13:32 +00:00

BeanIssues referenced this issue

2026-11-15 11:41:10 +00:00

Game: Longshot closed unexpectedly during the start #776

ChronoEpoch referenced this issue

2026-11-15 11:43:15 +00:00

Game: Longshot closed unexpectedly during the start #776

BeanIssues referenced this issue

2026-11-15 11:48:09 +00:00

Game: Longshot closed unexpectedly during the start #778

BeanIssues commented

2026-11-15 11:48:09 +00:00

Collaborator

From #778 (closed as a duplicate of this one):

The launch crash still occurs on v3.0.0-rc.4 (source b784a40c), with the same RX 9060 XT / AMD driver 26.10.1 and Windows 11; the report includes a crash record showing an access violation at uptime 0. The user has RX_VK_MESH_OPT=1 set and reports CPU Ryzen 5 8600G.

From #778 (closed as a duplicate of this one): The launch crash still occurs on v3.0.0-rc.4 (source b784a40c), with the same RX 9060 XT / AMD driver 26.10.1 and Windows 11; the report includes a crash record showing an access violation at uptime 0. The user has RX_VK_MESH_OPT=1 set and reports CPU Ryzen 5 8600G.

Zopiac commented

2026-11-15 12:43:50 +00:00

I seem to have the exact same issue myself, built v3.0.0-rc.4, but with Nvidia RTX 3060 Ti and AMD Ryzen 7 5800X3D on Windows 10. Crash log looks practically identical to the one shared in #778, with a bunch of "mem" lines followed immediately by a crash dump.

SocialWare referenced this issue

2026-11-15 13:27:34 +00:00

Game: Crash in Hyrule field after opening and closing map #809

BeanIssues referenced this issue

2026-11-15 14:26:35 +00:00

Game: Longshot closed unexpectedly during the start #814

BeanIssues commented

2026-11-15 14:26:35 +00:00

Collaborator

From #814 (closed as a duplicate of this one):

The launch crash persists on v3.0.0-rc.4/source b784a40c with an RX 9060 XT 16 GB and Windows 11 build 22631, on a Ryzen 7 5700G system. The report confirms default game options and contains a 0-second access violation before a Vulkan device is named.

From #814 (closed as a duplicate of this one): The launch crash persists on v3.0.0-rc.4/source b784a40c with an RX 9060 XT 16 GB and Windows 11 build 22631, on a Ryzen 7 5700G system. The report confirms default game options and contains a 0-second access violation before a Vulkan device is named.

BeanIssues referenced this issue

2026-11-15 15:38:14 +00:00

Game: Longshot couldn't start during the start #821

BeanIssues referenced this issue

2026-11-15 16:21:46 +00:00

Game: Longshot closed unexpectedly during the start #827

BeanIssues commented

2026-11-15 16:21:46 +00:00

Collaborator

From #827 (closed as a duplicate of this one):

This launch-time crash also reproduces on v3.0.0-rc.4 (source b784a40c) with an AMD Radeon RX 9070 XT using AMD proprietary driver 25.10.36 (LLPC), Windows 10 build 19044, Ryzen 7 9800X3D, and FSR 4 loader configured. Unlike the prior reports' immediate startup failures, this run lasted 44 seconds and the crash record shows an access violation in amdvlk64.dll (+0x3f2807) after reaching Hyrule Field.

From #827 (closed as a duplicate of this one): This launch-time crash also reproduces on v3.0.0-rc.4 (source b784a40c) with an AMD Radeon RX 9070 XT using AMD proprietary driver 25.10.36 (LLPC), Windows 10 build 19044, Ryzen 7 9800X3D, and FSR 4 loader configured. Unlike the prior reports' immediate startup failures, this run lasted 44 seconds and the crash record shows an access violation in amdvlk64.dll (+0x3f2807) after reaching Hyrule Field.

BeanIssues referenced this issue

2026-11-15 17:54:44 +00:00

Game: Longshot closed unexpectedly during the start #856

BeanIssues commented

2026-11-15 17:54:45 +00:00

Collaborator

From #856 (closed as a duplicate of this one):

Additional report on RX 6700 XT with AMD proprietary driver 26.10.1, Windows 11, in Hyrule Field on v3.0.0-rc.4. The crash record is an unhandled exception with a backtrace through longshot_vk.dll; it occurred after 395 seconds of uptime.

From #856 (closed as a duplicate of this one): Additional report on RX 6700 XT with AMD proprietary driver 26.10.1, Windows 11, in Hyrule Field on v3.0.0-rc.4. The crash record is an unhandled exception with a backtrace through longshot_vk.dll; it occurred after 395 seconds of uptime.

BeanIssues referenced this issue

2026-11-15 18:01:01 +00:00

Game: Longshot closed unexpectedly during the start #858

llun commented

2026-11-15 18:29:17 +00:00

Member

The reports in this thread are at least three different crashes, from reading each one's log:

1. A crash 0 s into the start, before any Vulkan device is named: #778, #814, and very likely @Zopiac's (same as #778). Also #776 and #689, outside this thread. They all have the same signature: exception 0xc0000005 (write 0x100000000000, guest 0), guest backtrace 0x80c4afcc 0x83bb705c 0x83b7b47c 0x83b7a838 .... The cause is the game files: the build's romfs has no System folder, so System/HeapSize/Product.Nin_Ounce_NVN2.HeapDef.byml.zs is missing and the game sets up its heaps with no room in them. Removing that one file from a complete romfs reproduces it exactly (RTX 5080), on any GPU and with any settings.

What fixes it: check the build's romfs folder for System\HeapSize\Product.Nin_Ounce_NVN2.HeapDef.byml.zs and System\RegionLangMask.txt. A complete romfs has 186,583 files, about 23.8 GB. If they're missing, build again from a complete dump: the .nup, or a romfs folder that holds both System and Pack. Since #534 and #863 the builder refuses game files without them, naming what's missing.

2. #827: a crash inside AMD's driver (amdvlk64.dll+0x3f2807, a read of 0xffffffffffffffff) 44 s in, with the renderer already running. That's a different crash.

3. #856: an unhandled exception in longshot_vk.dll after 395 s in Hyrule Field. That's a different crash too.

This issue's own report (nightly-80, RX 9060 XT) closed while its window showed the pipeline-loading screen, which is later than crash 1 and has no log here, so it can't be matched yet. @arukod, if it still happens on a current build, please attach logs/longshot_log.txt from the game folder.

#827 and #856 would be easier to follow up as issues of their own.

The reports in this thread are at least three different crashes, from reading each one's log: **1. A crash 0 s into the start, before any Vulkan device is named:** #778, #814, and very likely @Zopiac's (same as #778). Also #776 and #689, outside this thread. They all have the same signature: `exception 0xc0000005 (write 0x100000000000, guest 0)`, guest backtrace `0x80c4afcc 0x83bb705c 0x83b7b47c 0x83b7a838 ...`. The cause is the game files: the build's romfs has no `System` folder, so `System/HeapSize/Product.Nin_Ounce_NVN2.HeapDef.byml.zs` is missing and the game sets up its heaps with no room in them. Removing that one file from a complete romfs reproduces it exactly (RTX 5080), on any GPU and with any settings. What fixes it: check the build's `romfs` folder for `System\HeapSize\Product.Nin_Ounce_NVN2.HeapDef.byml.zs` and `System\RegionLangMask.txt`. A complete romfs has 186,583 files, about 23.8 GB. If they're missing, build again from a complete dump: the `.nup`, or a romfs folder that holds both `System` and `Pack`. Since #534 and #863 the builder refuses game files without them, naming what's missing. **2. #827:** a crash inside AMD's driver (`amdvlk64.dll+0x3f2807`, a read of `0xffffffffffffffff`) 44 s in, with the renderer already running. That's a different crash. **3. #856:** an unhandled exception in `longshot_vk.dll` after 395 s in Hyrule Field. That's a different crash too. This issue's own report (nightly-80, RX 9060 XT) closed while its window showed the pipeline-loading screen, which is later than crash 1 and has no log here, so it can't be matched yet. @arukod, if it still happens on a current build, please attach `logs/longshot_log.txt` from the game folder. #827 and #856 would be easier to follow up as issues of their own.