MagicBeanDev/Longshot

Watch

Fork 98

Game: #271

New issue

Closed

opened 2026-11-13 18:43:28 +00:00 by Oldtimer · 3 comments

Oldtimer commented

2026-11-13 18:43:28 +00:00

Longshot version

v3.0.0 rc.3 and nightly 77

Channel

Nightly

What kind of problem

Crash, freeze or black screen

What happened

Random frequent crashes. Happens on both release and nightly. Same issue with Hookshot.

Tried updating graphics driver from 621.14 to 621.24 - no change.
Tried fiddling with various settings both in-game and control panel - no change.

Where in the game

Most areas, most frequently when entering a new area. Not 100% but 80%ish

How often

Every time

Graphics card and driver version

RTX 4080 Super

CPU, RAM and operating system

Intel 12700K, Windows 10 LTSC IOT (fully updated)

Changes from the defaults

I cant find the file. Closest would be the option.ini i suppose?

quality_preset=0
ultrawide=1
output_res=1920x1080
handheld_profile=0
dlss=0
dlss_model=0
resolution=0
sharpness=0
frame_generation=0
frame_generation_by=1
frame_pacing=0
frame_rate_cap=0
nvidia_reflex=0
amd_anti-lag_2=0
fullscreen=0
vsync=0
upscaling=2
ultrawide_menus=1
hdr=0
hdr_paper_white=200
hdr_peak_brightness=1000
hdr_contrast=100
hdr_tone_mapper=0
anisotropic_filtering=4
gpu_device=0
vram_budget=7
volume=100
mute_in_background=0
audio_output=0
fps_counter=0
fps_counter_position=0
menu_size=2
game_speed=1
field_of_view=100
text_speed=0
text_size=0
microphone=1
menu_language=0
discord_status=1
skip_opening=0
controller_in_background=0
mouse_camera=0
disable_camera_centering=0
mouse_sensitivity=100
invert_mouse_vertical=0
invert_camera_x=0
invert_camera_y=0
camera_speed=150
stick_dead_zone=0
rumble_strength=100
motion_controls=1
motion_sensitivity_x=100
motion_sensitivity_y=100
invert_motion_x=0
invert_motion_y=0
motion_deadzone=1
layout_preset=0
button_prompts=0
menu_shortcut=2
compact_menu_key=0
debug_tools=0
descriptor_reuse=1
sampler_cache=0
robust_buffers=0
astc_as_rgba8=0
memory_budget=5
auto_for=cd79c99fa513b069
auto_tuned=cd79c99fa513b069
options_version=6
pad_a=1
key_a=69,0
pad_b=0
key_b=16,0
pad_x=3
key_x=32,0
pad_y=2
key_y=1,0
pad_ls=7
key_ls=17,0
pad_rs=8
key_rs=67,0
pad_l=9
key_l=81,0
pad_r=10
key_r=82,0
pad_zl=15
key_zl=90,2
pad_zr=16
key_zr=88,70
pad_plus=6
key_plus=9,13
pad_minus=4
key_minus=77,0
pad_left=13
key_left=49,0
pad_up=11
key_up=50,0
pad_right=14
key_right=51,0
pad_down=12
key_down=52,0
key_move_up=87,0
key_move_down=83,0
key_move_left=65,0
key_move_right=68,0
key_cam_up=38,73
key_cam_down=40,75
key_cam_left=37,74
key_cam_right=39,76
pad_note_l=-1
key_note_l=0,0
pad_note_r=-1
key_note_r=99,0
pad_note_a=-1
key_note_a=98,0
pad_note_y=-1
key_note_y=100,0
pad_note_x=-1
key_note_x=104,0

longshot_log.txt

Attaching file.

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 and nightly 77 ### Channel Nightly ### What kind of problem Crash, freeze or black screen ### What happened Random frequent crashes. Happens on both release and nightly. Same issue with Hookshot. Tried updating graphics driver from 621.14 to 621.24 - no change. Tried fiddling with various settings both in-game and control panel - no change. ### Where in the game Most areas, most frequently when entering a new area. Not 100% but 80%ish ### How often Every time ### Graphics card and driver version RTX 4080 Super ### CPU, RAM and operating system Intel 12700K, Windows 10 LTSC IOT (fully updated) ### Changes from the defaults I cant find the file. Closest would be the option.ini i suppose? quality_preset=0 ultrawide=1 output_res=1920x1080 handheld_profile=0 dlss=0 dlss_model=0 resolution=0 sharpness=0 frame_generation=0 frame_generation_by=1 frame_pacing=0 frame_rate_cap=0 nvidia_reflex=0 amd_anti-lag_2=0 fullscreen=0 vsync=0 upscaling=2 ultrawide_menus=1 hdr=0 hdr_paper_white=200 hdr_peak_brightness=1000 hdr_contrast=100 hdr_tone_mapper=0 anisotropic_filtering=4 gpu_device=0 vram_budget=7 volume=100 mute_in_background=0 audio_output=0 fps_counter=0 fps_counter_position=0 menu_size=2 game_speed=1 field_of_view=100 text_speed=0 text_size=0 microphone=1 menu_language=0 discord_status=1 skip_opening=0 controller_in_background=0 mouse_camera=0 disable_camera_centering=0 mouse_sensitivity=100 invert_mouse_vertical=0 invert_camera_x=0 invert_camera_y=0 camera_speed=150 stick_dead_zone=0 rumble_strength=100 motion_controls=1 motion_sensitivity_x=100 motion_sensitivity_y=100 invert_motion_x=0 invert_motion_y=0 motion_deadzone=1 layout_preset=0 button_prompts=0 menu_shortcut=2 compact_menu_key=0 debug_tools=0 descriptor_reuse=1 sampler_cache=0 robust_buffers=0 astc_as_rgba8=0 memory_budget=5 auto_for=cd79c99fa513b069 auto_tuned=cd79c99fa513b069 options_version=6 pad_a=1 key_a=69,0 pad_b=0 key_b=16,0 pad_x=3 key_x=32,0 pad_y=2 key_y=1,0 pad_ls=7 key_ls=17,0 pad_rs=8 key_rs=67,0 pad_l=9 key_l=81,0 pad_r=10 key_r=82,0 pad_zl=15 key_zl=90,2 pad_zr=16 key_zr=88,70 pad_plus=6 key_plus=9,13 pad_minus=4 key_minus=77,0 pad_left=13 key_left=49,0 pad_up=11 key_up=50,0 pad_right=14 key_right=51,0 pad_down=12 key_down=52,0 key_move_up=87,0 key_move_down=83,0 key_move_left=65,0 key_move_right=68,0 key_cam_up=38,73 key_cam_down=40,75 key_cam_left=37,74 key_cam_right=39,76 pad_note_l=-1 key_note_l=0,0 pad_note_r=-1 key_note_r=99,0 pad_note_a=-1 key_note_a=98,0 pad_note_y=-1 key_note_y=100,0 pad_note_x=-1 key_note_x=104,0 ### longshot_log.txt Attaching file. ### 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

958 KiB

Oldtimer added the

kind

bug

label

2026-11-13 18:43:28 +00:00

Amateurwizrd commented

2026-11-13 20:34:28 +00:00

Contributor

The attached log shows a GPU device loss, and what leads up to it.

The driver's budget for system memory the GPU can reach is 2937 MB on this PC: heap 1 (system) ... used 674 of 2937 MB (line 769 of the log). The log of #203, also an NVIDIA card, has 46432 MB there, and this PC has 64 GB of RAM, so the budget is unusually small.
The game's memory pools are imported into that heap. It passes the budget in Hyrule Field (used 3016 of 2937 MB, line 3034) and ends at 3050 MB.
Entering Kakariko Village (line 6050), new imports fail: pool ... not imported (VkResult -2), which is VK_ERROR_OUT_OF_DEVICE_MEMORY. The buffers that needed them are left out (storage buffer NOT bound (reads zeros), 40 lines).
22 frames later: submit 78696 failed (-4) and VK_ERROR_DEVICE_LOST.

That fits "most often when entering a new area": a new area is when new pools are imported.

Longshot can give idle imports back when that heap is nearly full (imports_give_back in gpu/vk/vk_memory.cpp), but it is off by default on Windows: RX_VK_IMPORT_HIGH defaults to 0 there, after device losses on Intel Arc and AMD cards.

Two things would confirm this, if you have time:

Task Manager, Performance, GPU, with the game closed: what does "Shared GPU memory" show (used and total)? And is anything else open that uses the GPU (a browser, a recorder, an overlay)?
A line RX_VK_IMPORT_HIGH=85 in longshot_env.txt in the game folder, then the same route (Market, Hyrule Field, Kakariko). Does it still crash? The log from that run would help either way. This switch was turned off on Windows for crashes on other vendors' cards, so treat it as a test, not a fix.

I have not reproduced this: my PC's budget for that heap is about 15 GB, so the same route stays under it.

The attached log shows a GPU device loss, and what leads up to it. - The driver's budget for system memory the GPU can reach is 2937 MB on this PC: `heap 1 (system) ... used 674 of 2937 MB` (line 769 of the log). The log of #203, also an NVIDIA card, has 46432 MB there, and this PC has 64 GB of RAM, so the budget is unusually small. - The game's memory pools are imported into that heap. It passes the budget in Hyrule Field (`used 3016 of 2937 MB`, line 3034) and ends at 3050 MB. - Entering Kakariko Village (line 6050), new imports fail: `pool ... not imported (VkResult -2)`, which is `VK_ERROR_OUT_OF_DEVICE_MEMORY`. The buffers that needed them are left out (`storage buffer NOT bound (reads zeros)`, 40 lines). - 22 frames later: `submit 78696 failed (-4)` and `VK_ERROR_DEVICE_LOST`. That fits "most often when entering a new area": a new area is when new pools are imported. Longshot can give idle imports back when that heap is nearly full (`imports_give_back` in `gpu/vk/vk_memory.cpp`), but it is off by default on Windows: `RX_VK_IMPORT_HIGH` defaults to 0 there, after device losses on Intel Arc and AMD cards. Two things would confirm this, if you have time: 1. Task Manager, Performance, GPU, with the game closed: what does "Shared GPU memory" show (used and total)? And is anything else open that uses the GPU (a browser, a recorder, an overlay)? 2. A line `RX_VK_IMPORT_HIGH=85` in `longshot_env.txt` in the game folder, then the same route (Market, Hyrule Field, Kakariko). Does it still crash? The log from that run would help either way. This switch was turned off on Windows for crashes on other vendors' cards, so treat it as a test, not a fix. I have not reproduced this: my PC's budget for that heap is about 15 GB, so the same route stays under it.

Oldtimer commented

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

Author

I think you are 100% onto something. I had lowered the amount of shared memory via a registry setting earlier when i was poking around with AI stuff. I will change it back to the default 50% (of system ram) and test again before reporting back here.

Oldtimer commented

2026-11-13 21:43:13 +00:00

Author

Played an hour. 0 crashes. Some light flickering in Hyrule field in one of the streams where the water falls down a little. And a bit more flickering inside Goron City. But, thats minor and im confident in saying the crashes were related to the smaller shared memory size I had set.

Oldtimer closed this issue

2026-11-13 21:43:36 +00:00