Game: Menu cannot be closed on nightly-695 after changing its shortcut #2127

Open
opened 2026-11-21 21:31:11 +00:00 by BeanBot · 3 comments
Member

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.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1573812795160395776/1573812795160395776) ### 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.
Author
Member
Files from the Discord report: - [report.txt](https://git.magicbean.dev/attachments/c967a0ea-5037-4795-b48d-5f4fdd01ddcf) - [longshot_log.txt](https://git.magicbean.dev/attachments/b6c455f7-9388-4d4f-b850-60aaffcc4af0) - [longshot_log.1.txt](https://git.magicbean.dev/attachments/5f792b70-362f-4da9-a05a-b497520ddc6d) - [picture.png](https://git.magicbean.dev/attachments/90e4946e-6dad-4672-a688-d2ecdfc0b1e8)
Author
Member

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.

Updated with more from [Discord](https://discord.com/channels/1569849200047427645/1573812795160395776/1573841043789455383): 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.
Contributor

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:

  • The game's Plus (pause) is Tab and Enter by default, so a pad's A opens and closes the pause menu as well. On the game's Options screen the game's own Back is A (the picture shows "Back A"), so one A press goes back and reopens the pause: the game's menu comes back however often it is closed. This is #1992, and its fix (Plus is Tab alone, Enter no longer its second key) is in progress.
  • Menu shortcut moved to "Insert, F1 or Esc" on its own, because a file from before options_version 5 wrote the old "Insert or F1" whether it was chosen or not. With Esc among the shortcuts, controller software's B and Menu open this menu, and while it is open the game gets no keys, so the game's pause menu cannot take the pad's B either. Switching the row to "Insert or F1" fixes this half only, which is why the problem looked like it persisted.
  • The general fix for keys other software synthesizes is #152 (a Keyboard row on the Controls page: Auto counts the keyboard only while no controller is connected), claimed for #1563.

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= and key_plus= lines of longshot_options.ini say (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.

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 <kbd>Enter</kbd>, B and Menu as <kbd>Esc</kbd> and View as <kbd>Tab</kbd>, on top of the pad SDL reads: - The game's Plus (pause) is <kbd>Tab</kbd> and <kbd>Enter</kbd> by default, so a pad's A opens and closes the pause menu as well. On the game's Options screen the game's own Back is A (the picture shows "Back A"), so one A press goes back and reopens the pause: the game's menu comes back however often it is closed. This is https://git.magicbean.dev/MagicBeanDev/Longshot/issues/1992, and its fix (Plus is Tab alone, Enter no longer its second key) is in progress. - Menu shortcut moved to "Insert, F1 or Esc" on its own, because a file from before options_version 5 wrote the old "Insert or F1" whether it was chosen or not. With Esc among the shortcuts, controller software's B and Menu open *this* menu, and while it is open the game gets no keys, so the game's pause menu cannot take the pad's B either. Switching the row to "Insert or F1" fixes this half only, which is why the problem looked like it persisted. - The general fix for keys other software synthesizes is https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/152 (a Keyboard row on the Controls page: Auto counts the keyboard only while no controller is connected), claimed for https://git.magicbean.dev/MagicBeanDev/Longshot/issues/1563. 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=` and `key_plus=` lines of `longshot_options.ini` say (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.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#2127
No description provided.