Game: Crash during the opening cutscene on Intel UHD Graphics (Tiger Lake) #1676
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1676
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?
Reported on Discord
Version / channel
The attached log identifies Longshot nightly-486-09a20cd6 on Windows 11.
What happened / steps
The reporter says Longshot crashes during the intro cutscene. They note the frame rate is nearly locked at 30 fps before/during the report. The log records the map as Title and intro and an access violation in Intel's Vulkan driver:
Hardware
Reporter says 11th-gen Intel Core i3, 16 GB RAM, Intel UHD integrated graphics (Tiger Lake), with 8 GB VRAM reported. Exact GPU model and driver version are unknown.
Reproduction details
Exact point in the cutscene and whether the crash happens every time are unknown. Confirming whether the same nightly is still affected is also unknown.
Logs
The log says this crash was automatically sent to the crash-report tracker: #81 (comment). The attached longshot_log.txt is useful; other attached launcher/play logs are available in the Discord report.
Files from the Discord report:
From Discord:
Reporter added: Intel UHD integrated graphics, Tiger Lake; Intel graphics driver 32.0.101.7088; Vulkan API 1.4.323; 8 GB reported VRAM. Previously provided CPU/RAM: 11th-gen Intel Core i3, 16 GB RAM. Exact GPU model, cutscene point, and whether the crash reproduces every time remain unknown.