mirror of
https://github.com/gopher64/gopher64.git
synced 2026-04-25 15:06:00 +03:00
[GH-ISSUE #612] Problem with xinput configuration, it is not remembered. #86
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/gopher64#86
Loading…
Add table
Add a link
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?
Originally created by @williansti on GitHub (Nov 7, 2025).
Original GitHub issue: https://github.com/gopher64/gopher64/issues/612
We have an issue with input specifically in the settings with Xbox controllers using Xinput; I don't know if this occurs with other controllers, that's the problem.
I use Xbox Series X controllers connected via Bluetooth; there are four controllers in total. With all of them connected, I opened Gopher64 and, in Controller Config > Controller, selected each of the four in their respective fields.
So far everything is fine and working normally, so I closed the emulator and let's check the config.json file.
Here we see the 4 controllers configured correctly, and even the 4 Xbox profiles with buttons that I remapped are also perfectly configured.
I've now disconnected 3 controllers, leaving only 1 connected, and reopened the emulator. Note that the 4 profiles are correctly remembered, but the other 3 controls were forgotten; only 1 remains configured.
I've now disconnected all 4 controllers and reopened the emulator. Note that the profiles are remembered, but now all 4 controllers have been forgotten. This is terrible, because if you don't keep all 4 controllers connected, they are simply forgotten. You need to see what's happening with SDL/Xinput in this emulator. Other projects like Flycast, Dolphin, Duckstation, Ymir, Ares, PCSX2, among others, manage to remember the configured controllers.
@loganmc10 commented on GitHub (Nov 7, 2025):
Yes I understand the problem. Basically, when you open the emulator and there isn't a controller connected, the dropdown defaults to "None", and when you close the emulator, that is what is saved to the settings file, rather than the last connected controller. It would be better for it to keep the last connected controller in the settings.