Game: A opens up start menu #1992

Open
opened 2026-11-21 03:16:52 +00:00 by TrustyJedi · 6 comments

Longshot version

476

Channel

Nightly

What kind of problem

Controls

What happened

Every time that I press the A button on my Xbox One controller it opens up the start menu as if I have multiple controls bound to one button. I have checked to make sure it's not an issue with the controller in other programs and disabled XInput in Steam just in case, though I'm not running it through Steam.

Where in the game

Kokiri Forest, walking out of Link's house

How often

Every time

Graphics card and driver version

RTX 3080

CPU, RAM and operating system

Ryzen 9 5900X

Changes from the defaults

No response

longshot_log.txt

Let me know if I have to upload any other logs, but I don't imagine the solution is in there

Screenshots or video

No response

Before you send it

  • The problem is still there on the newest release or nightly.
  • I searched the open issues for it.
  • I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
### Longshot version 476 ### Channel Nightly ### What kind of problem Controls ### What happened Every time that I press the A button on my Xbox One controller it opens up the start menu as if I have multiple controls bound to one button. I have checked to make sure it's not an issue with the controller in other programs and disabled XInput in Steam just in case, though I'm not running it through Steam. ### Where in the game Kokiri Forest, walking out of Link's house ### How often Every time ### Graphics card and driver version RTX 3080 ### CPU, RAM and operating system Ryzen 9 5900X ### Changes from the defaults _No response_ ### longshot_log.txt Let me know if I have to upload any other logs, but I don't imagine the solution is in there ### Screenshots or video _No response_ ### Before you send it - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
Member

Possibly related, for context:

  • issue #1563 Game: Steam Input causes incorrect controller and camera behavior — Related input overlap, but that report concerns Steam Input misrouting, not this Xbox A-button symptom.
  • PR #152 WIP: feat(input): share Keyboard Auto/On/Off policy with menu navigation — Open keyboard-input policy may address injected keyboard events, but not confirmed for this controller report.
Possibly related, for context: - issue #1563 Game: Steam Input causes incorrect controller and camera behavior — Related input overlap, but that report concerns Steam Input misrouting, not this Xbox A-button symptom. - PR #152 WIP: feat(input): share Keyboard Auto/On/Off policy with menu navigation — Open keyboard-input policy may address injected keyboard events, but not confirmed for this controller report.
Contributor

The log shows one controller, the Xbox One Controller through SDL (hid: 1 controller through SDL), so the game isn't seeing two pads. What it doesn't show is the bindings. Longshot keeps them in longshot_options.ini, which the log puts at %USERPROFILE%\AppData\Roaming\Longshot\longshot_options.ini. Each of the Switch's buttons has a pad_<button>=<the pad input> line there (pad_a=, pad_plus=, ...). Each line can hold two pad inputs, separated by a comma. If A's input is one of pad_plus's two, pressing A opens the pause menu, exactly as described.

To pin it down, from the reporter please:

  1. The pad_ lines of that file (they hold nothing personal).
  2. Whether it still happens on the newest nightly. nightly-476 is about 150 nightlies old, and the controls have changed since (Sprint, the HUD shortcut, rebinding by slot).
  3. Meanwhile: the Insert menu's Controls page shows what each button is bound to. Setting Plus back to Start there (or deleting the pad_ lines with the game closed, which brings back the defaults) should end it.

Posted by an AI agent (Claude Code) for d4nkn3ss. Not claimed: I can't drive a physical Xbox pad on this PC.

The log shows one controller, the Xbox One Controller through SDL (`hid: 1 controller through SDL`), so the game isn't seeing two pads. What it doesn't show is the bindings. Longshot keeps them in `longshot_options.ini`, which the log puts at `%USERPROFILE%\AppData\Roaming\Longshot\longshot_options.ini`. Each of the Switch's buttons has a `pad_<button>=<the pad input>` line there (`pad_a=`, `pad_plus=`, ...). Each line can hold two pad inputs, separated by a comma. If A's input is one of `pad_plus`'s two, pressing A opens the pause menu, exactly as described. To pin it down, from the reporter please: 1. The `pad_` lines of that file (they hold nothing personal). 2. Whether it still happens on the newest nightly. nightly-476 is about 150 nightlies old, and the controls have changed since (Sprint, the HUD shortcut, rebinding by slot). 3. Meanwhile: the Insert menu's Controls page shows what each button is bound to. Setting Plus back to Start there (or deleting the `pad_` lines with the game closed, which brings back the defaults) should end it. *Posted by an AI agent (Claude Code) for d4nkn3ss. Not claimed: I can't drive a physical Xbox pad on this PC.*
Author

I made a copy of the options and turned it into a .txt

I'm updating atm and that might resolve it. I thought I was on the newest version, so that's my bad.
But here's the txt

I made a copy of the options and turned it into a .txt I'm updating atm and that might resolve it. I thought I was on the newest version, so that's my bad. But here's the txt
Contributor

Thanks. That rules out a binding. Your pad_ lines are the defaults: A on one input only, and Plus on 6, which is SDL's Start. The log's SDL mapping for the pad is SDL's standard one for XInput pads (a:b0, start:b7, guide:b10), so A reaches the game as A.

Two things would tell us where it comes from, once the update is in:

  1. Does it still happen on the new nightly?
  2. Which menu opens when you press A:
    • the game's own pause menu (the inventory, map and quest screens Plus opens);
    • Longshot's settings menu (the overlay that F1 or Insert opens, which the pad's Home/Xbox button also opens);
    • or the Windows Start menu?

If it's Longshot's settings menu, the pad is reporting its Xbox button with A. That's what to look at next, and longshot_log.txt from a run where you press A a few times would show it.

Posted by an AI agent (Claude Code) for d4nkn3ss.

Thanks. That rules out a binding. Your `pad_` lines are the defaults: A on one input only, and Plus on `6`, which is SDL's Start. The log's SDL mapping for the pad is SDL's standard one for XInput pads (`a:b0`, `start:b7`, `guide:b10`), so A reaches the game as A. Two things would tell us where it comes from, once the update is in: 1. Does it still happen on the new nightly? 2. Which menu opens when you press A: - the game's own pause menu (the inventory, map and quest screens Plus opens); - Longshot's settings menu (the overlay that F1 or Insert opens, which the pad's Home/Xbox button also opens); - or the Windows Start menu? If it's Longshot's settings menu, the pad is reporting its Xbox button with A. That's what to look at next, and `longshot_log.txt` from a run where you press A a few times would show it. *Posted by an AI agent (Claude Code) for d4nkn3ss.*
Author
  1. I'm on nightly 665 now
  2. It appears to be the plus button standard start menu, not the longshot menu
1. I'm on nightly 665 now 2. It appears to be the plus button standard start menu, not the longshot menu
Contributor

Thanks. Two things from your settings and the code:

  • The buttons go by position, as on a Switch. Your pad_a=1 and pad_b=0 are Longshot's defaults: the game's A is the pad's right face button (on an Xbox pad, the one labelled B), and the game's B is the bottom one (labelled A). So the button labelled A acts as the game's B. It shouldn't open the pause menu, but it isn't the game's A either. On the Insert menu's Controls page you can put A on the bottom button and B on the right one if you prefer Xbox labels.
  • nightly-476 read some pads twice. It read them through SDL and through XInput together; newer nightlies read XInput only when SDL has no pad open. Your old log shows both (hid: controller 0 connected and the SDL line).

If the pause menu still opens on 665, please attach the new longshot_log.txt from a run where you press the A-labelled button a few times in Kokiri Forest, and say whether the B-labelled button does what A should (talk, open doors).

Posted by an AI agent (Claude Code) for d4nkn3ss.

Thanks. Two things from your settings and the code: - **The buttons go by position, as on a Switch.** Your `pad_a=1` and `pad_b=0` are Longshot's defaults: the game's A is the pad's right face button (on an Xbox pad, the one labelled B), and the game's B is the bottom one (labelled A). So the button labelled A acts as the game's B. It shouldn't open the pause menu, but it isn't the game's A either. On the Insert menu's Controls page you can put A on the bottom button and B on the right one if you prefer Xbox labels. - **nightly-476 read some pads twice.** It read them through SDL and through XInput together; newer nightlies read XInput only when SDL has no pad open. Your old log shows both (`hid: controller 0 connected` and the SDL line). If the pause menu still opens on 665, please attach the new `longshot_log.txt` from a run where you press the A-labelled button a few times in Kokiri Forest, and say whether the B-labelled button does what A should (talk, open doors). *Posted by an AI agent (Claude Code) for d4nkn3ss.*
Sign in to join this conversation.
No milestone
No project
No assignees
3 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#1992
No description provided.