Game: Menu cannot be closed on nightly-695 after changing its shortcut #2127
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#2127
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
Longshot version
nightly-695-96caf2f2 (source e78e3645), nightly build.
What happened / steps
After the game menu was opened, it could not be closed. The reporter changed the menu shortcut from Esc to Insert only, then to F1 only, but the problem persisted. The report says this was reproduced in two video clips; the menu remained impossible to close. Expected: the game menu closes with its configured shortcut. The menu was set automatically to three hotkeys, including Esc. While the menu was open, it looped with the game menu. The reporter used the Windows key to show the taskbar and closed Longshot from there.
Where in the game
ForestTemple (adult), according to the bug report. The attached logs include this run and the preceding run.
Graphics card and driver version
NVIDIA GeForce RTX 5060 Ti, NVIDIA 621.24.
CPU, RAM and operating system
AMD Ryzen 7 PRO 6850H with Radeon Graphics (16 threads), 29 GB, Windows 11 (build 26300).
Changes from defaults
Menu shortcut was changed first to Insert only, then to F1 only; the issue persisted. Other reported setting changes include frame generation 2x, fullscreen on, V-Sync on, and Present queue on. See attached report.txt for the full settings list.
Logs and media
The attachment includes report.txt, longshot_log.txt and longshot_log.1.txt, a screenshot, and two video clips; the report was made after the clips.
Missing details
Please clarify the exact steps to open the menu, whether this is reproducible every time, and whether the menu responds to any other input.
Files from the Discord report:
Updated with more from Discord: Added the clarification that Esc was among the automatically configured three hotkeys and the reporter exited via the Windows taskbar after the menu loop persisted with Insert-only and F1-only shortcuts.
I read the tick and the report, and the Insert menu cannot get stuck this way: I compiled
menu_tick's key block and close paths game-free and every configured shortcut closes the open menu, including right after the Menu shortcut row is changed: Insert and F1 in "Insert or F1", F1 in "F1 only", Insert and F1 in the default, Esc while it is open, the pad's back, and a right click. The row takes no restart, so no restart question stands in front of the close.What the picture and the settings point at is the game's own pause menu plus two input overlaps from controller software, and both together match the report. Steam Input's Desktop layout, which stays over a game started outside Steam, sends the pad's A as Enter, B and Menu as Esc and View as Tab, on top of the pad SDL reads:
Two things would settle it: does it still happen with Steam closed (or Steam → Settings → Controller → Desktop Layout → Steam Input disabled), and what do the
pad_plus=andkey_plus=lines oflongshot_options.inisay (they hold nothing personal)? If this report's pad also sends those keys, nothing is wrong in the menu's own code and the two fixes above are the ones to wait for.