Game: Longshot closed unexpectedly while it prepared the shaders #1717
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1717
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 (source 87cb36aa)
Channel
Release candidate
What kind of problem
Crash, freeze or black screen
What happened
Longshot closed unexpectedly while it prepared the shaders. Longshot ended without a crash report: it was closed from outside (Task Manager, a kill), or the system stopped it, often for running out of memory. (The report from the crash window is pasted below.)
Where in the game
Preparing shaders
How often
Once so far
Graphics card and driver version
Intel(R) Arc(TM) A730M Graphics, Intel Corporation 101.9175
CPU, RAM and operating system
12th Gen Intel(R) Core(TM) i7-12700H (20 threads), 16 GB; Windows 11 (build 26300)
Changes from the defaults
No response
longshot_log.txt
Longshot crash report, made by the window Longshot shows after a crash (20261119T064905Z 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: Longshot ended without a crash report: it was closed from outside (Task Manager, a kill), or the system stopped it, often for running out of memory.
Crash and unclean-end records in the last day: 2.
Summary (what Report automatically sends, too)
Version: v3.0.0
Release build: Yes
Operating system: Windows 11 (build 26300)
Renderer: not known
Graphics card: Intel(R) Arc(TM) A730M Graphics, Intel Corporation 101.9175
CPU and RAM: 12th Gen Intel(R) Core(TM) i7-12700H (20 threads), 16 GB
Map: Preparing shaders
Settings: 111, 0 changed from the defaults
Crash: unknown
Log: its end, below
Longshot version
v3.0.0 (source 87cb36aa)
Channel (from the version): Release
Graphics card and driver version
Intel(R) Arc(TM) A730M Graphics, Intel Corporation 101.9175
Devices the log lists: Intel(R) Arc(TM) A730M Graphics; Microsoft Direct3D12 (Intel(R) Arc(TM) A730M Graphics); Intel(R) Iris(R) Xe Graphics; Microsoft Direct3D12 (Intel(R) Iris(R) Xe Graphics); Microsoft Direct3D12 (Microsoft Basic Render Driver)
CPU, RAM and operating system
12th Gen Intel(R) Core(TM) i7-12700H (20 threads), 16 GB, Windows 11 (build 26300)
Built for: this PC's CPU (alderlake_alderlake_f6a2063451)
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=1280x800
handheld_profile=1
dlss=6
dlss_model=0
dlss_pre_bloom=0
resolution=4
sharpness=0
frame_generation=0
frame_generation_by=1
frame_rate_cap=0
nvidia_reflex=0
fullscreen=1
vsync=2
upscaling=0
crt_filter=0
crt_lines=0
ultrawide_menus=2
hud_layout=0
hdr=0
hdr_paper_white=200
hdr_peak_brightness=1000
hdr_contrast=100
hdr_tone_mapper=0
anisotropic_filtering=0
shadow_resolution=1
gpu_device=1
volume=100
mute_in_background=0
audio_output=0
microphone=10
microphone_gain=100
fps_counter=1
fps_counter_position=0
fps_counter_size=1
version_and_hardware_at_every_level=0
vram_line=1
textures_line=1
draws_line=1
dispatches_line=1
render_passes_line=1
draws_skipped_line=1
texture_uploads_line=1
pipelines_built_line=1
gpu_slot_waits_line=1
queue_submits_line=1
cpu_and_gpu_lines=1
menu_size=2
game_speed=0
field_of_view=100
text_speed=0
text_size=0
skip_title_screen=0
menu_language=0
discord_status=0
skip_opening=0
controller_in_background=0
mouse_camera=0
disable_camera_centering=0
mouse_sensitivity=100
invert_mouse_vertical=0
invert_mouse_horizontal=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=1
walk_mode=0
walk_speed=45
menu_shortcut=2
controller_menu_button=1
compact_menu_key=0
nfc_tag=0
debug_tools=0
damage_taken=1
frame_pacing=0
threaded_rendering=0
descriptor_reuse=0
sampler_cache=0
robust_buffers=1
present_queue=0
astc_as_rgba8=0
intel_shader_compiles=2
intel_quick_compute_builds=1
microphone_device=(value left out)
audio_output_device_id=(value left out)
audio_output_device_name=(value left out)
memory_budget=2
gpu_device_id=(value left out)
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_NO_INTEL_SERIAL=1
Crash record: unclean-20261119T064843Z.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
This looks like the same problem as #1706 (Install: Intel Arc A730 shader and pipeline preparation takes hours), so I'm closing this one to keep the discussion in one place.
Both report extreme shader/pipeline preparation duration on an Intel Arc A730 under Windows; this issue supplies the same-device report with a detailed log and an unexpected termination.
If it's different, say how and a maintainer will reopen it.