Game: Longshot closed unexpectedly while you were playing #1535
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1535
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
v3.0.0-rc.7 (source e5cea4aa)
Channel
Release
What kind of problem
Crash, freeze or black screen
What happened
Longshot closed unexpectedly while you were playing. The graphics driver failed. Update your graphics driver, and turn off overlays and tools hooked into the game. (The report from the crash window is pasted below.)
Where in the game
HyruleField_Child (child); was running fine until I swiped at one grass patch and it froze. May have been an issue related to sliding down a rock? Into water?
How often
Once so far
Graphics card and driver version
NVIDIA GeForce GTX 1660 Ti, NVIDIA 610.88
CPU, RAM and operating system
Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 threads), 8 GB; Windows 11 (build 26200)
Changes from the defaults
No response
longshot_log.txt
Longshot crash report, made by the window Longshot shows after a crash (20261118T023239Z 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 you were playing.
What went wrong: The graphics driver failed. Update your graphics driver, and turn off overlays and tools hooked into the game.
It had run for 225 s.
Crash and unclean-end records in the last day: 1.
Summary (what Report automatically sends, too)
Version: v3.0.0-rc.7
Release build: Yes
Operating system: Windows 11 (build 26200)
Renderer: Vulkan
Graphics card: NVIDIA GeForce GTX 1660 Ti, NVIDIA 610.88
CPU and RAM: Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 threads), 8 GB
Map: HyruleField_Child (child)
Settings: 90, 0 changed from the defaults
Crash: unknown
Log: its end, below
Longshot version
v3.0.0-rc.7 (source e5cea4aa)
Channel (from the version): Release candidate, or built from source
Graphics card and driver version
NVIDIA GeForce GTX 1660 Ti, NVIDIA 610.88
Devices the log lists: NVIDIA GeForce GTX 1660 Ti
CPU, RAM and operating system
Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 threads), 8 GB, Windows 11 (build 26200)
Built for: this PC's CPU (skylake_skylake_4fada1d4fa)
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=0
ultrawide=1
output_res=2560x1440
handheld_profile=1
dlss=0
dlss_model=0
resolution=0
sharpness=30
frame_generation=0
frame_generation_by=0
frame_pacing=1
frame_rate_cap=0
nvidia_reflex=0
fullscreen=1
vsync=0
upscaling=1
ultrawide_menus=1
hdr=0
hdr_paper_white=200
hdr_peak_brightness=1000
hdr_contrast=100
hdr_tone_mapper=0
anisotropic_filtering=0
gpu_device=0
threaded_rendering=0
vram_budget=2
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=2
text_size=0
skip_title_screen=1
microphone=1
menu_language=0
discord_status=1
skip_opening=0
controller_in_background=0
mouse_camera=1
disable_camera_centering=0
mouse_sensitivity=100
invert_mouse_vertical=0
invert_camera_x=0
invert_camera_y=0
camera_speed=125
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=1
walk_speed=50
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=0
auto_for=(value left out)
auto_tuned=(value left out)
auto_steps=(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
Crash record: crash-20261118T023202Z.txt
The end of longshot_log.txt
Its last 200 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
No response
Before you send it
Possibly related, for context:
To be clear, my driver is indeed fully updated, so the error message seems faulty. The fern caused no problem the second time around. I just updated the launcher, and everything is running beautifully compared to before; props to you all!
@BeanIssues wrote in #1535 (comment):
This is now happening for me as well, though if I look at the ground for long enough it gets back up to 30 for a bit.
Possible fix: #2082 (commit
8941d01b) lets the textures' floors give way past the driver's allowance, so a 6 GB card's VRAM stays under it instead of spilling into system memory; it is in nightly-738 and later, and v3.1.0 — please retest on the latest build and say whether it still happens.