Game: Longshot closed unexpectedly while it prepared the shaders #741
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
beanstalk: approved @ 1697603
beanstalk: approved @ 2c5a62e
beanstalk: approved @ 4fd82b7
beanstalk: approved @ 64d6d09
beanstalk: approved @ 6f91fae
beanstalk: approved @ 70a78f9
beanstalk: approved @ 8d361dc
beanstalk: approved @ 9d8356e
beanstalk: approved @ abf2227
beanstalk: approved @ d82f202
beanstalk: approved @ e5f1e40
beanstalk: approved @ ee8ab5f
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
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#741
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?
Longshot version
nightly-182-5274fb72 (source 0e893537)
Channel
Nightly
What kind of problem
Crash, freeze or black screen
What happened
Longshot closed unexpectedly while it prepared the shaders. An unexpected error. (The report from the crash window is pasted below.)
Where in the game
Starting the Game
How often
Every time
Graphics card and driver version
AMD Radeon RX 6900 XT (RADV NAVI21), radv Mesa 26.2.6-arch3.1
CPU, RAM and operating system
AMD Ryzen 7 5700X3D 8-Core Processor (16 threads), 31 GB, CachyOS (Linux 7.3.4-1-cachyos-bore), KDE (wayland)
Changes from the defaults
No response
longshot_log.txt
Longshot crash report, made by the window Longshot shows after a crash (20261115T084548Z UTC). Longshot sent nothing: paste this into the issue form, and attach the game folder's logs/longshot_log.txt if you can.
What happened
Longshot closed unexpectedly while it prepared the shaders.
What went wrong: An unexpected error.
It had run for 4 s.
Crash and unclean-end records in the last day: 1.
Longshot version
nightly-182-5274fb72 (source 0e893537)
Channel (from the version): Nightly
Graphics card and driver version
AMD Radeon RX 6900 XT (RADV NAVI21), radv Mesa 26.2.6-arch3.1
Devices the log lists: AMD Radeon RX 6900 XT (RADV NAVI21)
CPU, RAM and operating system
AMD Ryzen 7 5700X3D 8-Core Processor (16 threads), 31 GB, CachyOS (Linux 7.3.4-1-cachyos-bore), KDE (wayland)
Built for: this PC's CPU (znver3_znver3_32c1d074b4)
Upscalers (the log's first line of each)
NVIDIA DLSS: not named in the log
AMD FSR 4: no amd_fidelityfx_upscaler_vk.so in ~/Games/Longshot/nightly-182-5274fb72/bin, ~/Games/Longshot/nightly-182-5274fb72 (the readme says where AMD's files come from)
Changes from the defaults
longshot_options.ini (a value only when it is a number or on/off; the controls' bindings left out):
quality_preset=6
ultrawide=1
output_res=2560x1440
handheld_profile=0
dlss=0
dlss_model=0
resolution=1
sharpness=50
frame_generation=0
frame_generation_by=0
frame_pacing=1
frame_rate_cap=0
nvidia_reflex=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
threaded_rendering=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
skip_title_screen=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=100
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
walk_mode=0
walk_speed=45
menu_shortcut=2
compact_menu_key=0
debug_tools=0
damage_taken=1
descriptor_reuse=1
sampler_cache=0
robust_buffers=0
astc_as_rgba8=0
intel_shader_compiles=0
intel_quick_compute_builds=1
memory_budget=5
auto_for=(value left out)
options_version=6
Switches set (the environment and longshot_env.txt; a value only when it is a number or on/off, and never for a name with TOKEN, KEY, ROOM, SECRET, PASS, SERVER or USER in it):
LONGSHOT_NO_UPDATE_CHECK=1
MANGOHUD=1
Crash record: crash-20261115T084425Z.txt
The end of longshot_log.txt
Its last 145 lines (the home folder written ~, the user's name ):
Not in this report
Saves, game files, the game's executable and caches, memory dumps, keys, the options file itself and the path of your home folder.
Screenshots or video
No response
Before you send it
Possibly related, for context:
Launching in The stable branch has the same issue. Game opens, starts to load, completely fills the Physical memory and swap, and then crashes
From ZombieTarou on Discord:
Another reproduction on RX 6900 XT (RADV NAVI21), Mesa 26.2.6-arch3.1, CachyOS/KDE Wayland: nightly-189-aa95d35f (source c8e8dce4) crashes every launch shortly after mounting the save. The attached log ends with a write access violation at guest address 0xfffffffffffffed8. The user reports stable also exhausts RAM/swap before crashing; system monitor showed 29.5/31.3 GiB physical RAM and 9.6/31.2 GiB swap used. Log attached in Discord.