Ghost inputs from pad #2 and later to pad #1 - AppleTV
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
When multiple controllers are connected on tvOS, RetroArch seems to treat some small parts of their inputs as if they belonged to Player 1 / Port 1. This causes inputs from pad 2 and pad 3 to “bleed into” Player 1, even in the main menu, with no core or game loaded. It happens when controller #2, #3 or #4 quickly presses d-pad. What is funny - pressing left/right shows up on Player 1 as up/down, and the opposite. It's not that all the moves are copied, only some small parts that are enough to rotate direction of Player 1.
All controllers are properly assigned to their corresponding port #s.
The same controllers work correctly in the Apple TV system UI and other apps (no cross-interference), so the behavior appears specific to RetroArch’s input handling on tvOS.
Only Player 1 is affected.
Expected behavior
Controller inputs are isolated to their port / player and do not affect each other.
Steps to reproduce the bug
1. Connect 2 or 3 controllers to Apple TV (e.g., two 8BitDo pads or two DualSense pads).
2. Launch RetroArch.
3. Make sure you are in the main RetroArch menu (no game loaded).
4. Configure input so that only Player 1 should control the menu:
• Settings → Input → Menu Controls → All users control the menu = OFF
• Settings → Input → Maximum Users = 1 (also tested with 2+)
• Settings → Input → Port 1 Binds → Device Index explicitly set to pad #1
• Settings → Input → Port 2 Binds → Device Index set to None / not used
5. Use pad 1 and verify it can navigate the menu (expected).
6. Now, on pad 2 (and pad 3 if available), rapidly press D-pad directions (left/right/up/down).
Version/Commit
1.22.2
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
tvOS 26.0.1, AppleTV 4K 3rd gen, A2843
Affected Cores
No response
Environment information
No response
Relevant log output
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the RetroArch main menu on tvOS 26.0.1 with multiple controllers and the listed port settings. Start by tracing the frontend input handling for tvOS and controller port assignment; done means d-pad input from pads 2–4 no longer affects Player 1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100