Game: Longshot closed unexpectedly during the start #776
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#776
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-189-aa95d35f (source 719431ac)
Channel
No response
What kind of problem
No response
What happened
Longshot closed unexpectedly during the start. 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
9060XT 16GB Driver 26.10.1
CPU, RAM and operating system
AMD Ryzen 5 8600G w/ Radeon 760M Graphics (12 threads), 32 GB, Windows 11 (build 26200)
Changes from the defaults
Default, first time opening the port
longshot_log.txt
Longshot crash report, made by the window Longshot shows after a crash (20261115T113524Z 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 during the start.
What went wrong: An unexpected error.
It had run for 0 s.
Crash and unclean-end records in the last day: 1.
Longshot version
nightly-189-aa95d35f (source 719431ac)
Channel (from the version): Nightly
Graphics card and driver version
Not known: the log names no Vulkan device in use
CPU, RAM and operating system
AMD Ryzen 5 8600G w/ Radeon 760M Graphics (12 threads), 32 GB, Windows 11 (build 26200)
Built for: this PC's CPU (znver4_znver4_12580dcbde)
Upscalers (the log's first line of each)
NVIDIA DLSS: not named in the log
AMD FSR 4: not named in the log
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=1920x1080
handheld_profile=0
dlss=4
dlss_model=0
resolution=3
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
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
RX_VK_MESH_OPT=1
Crash record: crash-20261115T113514Z.txt
The end of longshot_log.txt
Its last 69 lines (the home folder written %USERPROFILE%, 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
Nothing to show, just closed
Before you send it
Possibly related, for context:
@BeanIssues wrote in #776 (comment):
Yes, same as #278 but newer version
This crash comes from the game files the build was made from. The log's crash (guest backtrace
0x80c4afcc 0x83bb705c 0x83b7b47c ..., "write 0x100000000000, guest 0") is the same as #689's and another player's on v3.0.0-rc.4. In each case the build's romfs had noSystemfolder. WithoutSystem/HeapSize/Product.Nin_Ounce_NVN2.HeapDef.byml.zsthe game sets up its memory heaps with no room in them, and it crashes at start every time, whatever the settings or GPU. Removing just that file from a complete romfs gives the same crash with the same backtrace.What to try:
builds\nightly-189-aa95d35f\romfsin the launcher's data folder. Check that it hasSystem\HeapSize\Product.Nin_Ounce_NVN2.HeapDef.byml.zsandSystem\RegionLangMask.txt. A complete romfs has 186,583 files, about 23.8 GB..nup, or a romfs folder that holds both theSystemandPackfolders.Changing settings or drivers won't help with this one. #863 makes the builder refuse game files without that file, naming what's missing, instead of building a game that can't start.
From xMichax on Discord:
xMichax's report is distinct from the startup-crash symptom: on nightly-189-aa95d35f (source 719431ac), RX 9070 XT with AMD proprietary driver 26.9.2 (LLPC), Ryzen 5 7500F, 32 GB, Windows 11 build 26200, default settings, the menu displays correctly; every time after starting a new game, the screen goes black when the opening cinematic ends while music and sound effects continue. Attached log is in the Discord post. PR #769 merged after this report and addresses black frames with threaded rendering off; it is not clearly the same full-scene black screen, so this may need separate tracking.