[X] I searched the existing issues and did not find anything similar.
Current Behavior
Controllers do not retain the last assigned .gamecontroller profile between app reboots
Expected Behavior
No response
Steps To Reproduce
Plug in two or more controllers (currently I've got 4)
Create mappings for two controllers and save them to .gamecontroller files. I named mine P1 Controller and P2 Controller.
Assign them to their respective controllers using the drop down.
Close and reopen AntiMicroX using the quit menu item.
One of the controllers has inherited the other's profile. This means that both now have the same profile, rather than distinct profiles as I last left it.
Environment
Program Version 3.3.4
Compiled from packaging: GitHub Windows Release
Built Against SDL 2.26.5
Running With SDL 2.26.5
Using Qt 5.15.2
Using Event Handler: SendInput
Host OS: windows Version: 10 Architecture: x86_64
Anything else?
I've got an ultimarc ipac ultimate I/O board (https://www.ultimarc.com/control-interfaces/i-pacs/i-pac-ultimate-i-o/), which creates two distinct dinput controllers through one usb. This may be the root of the problem, since it may think that both controllers are actually the same controller, despite it creating two separate entries in the UI.
Upvote & Fund
If you find this issue important, mark it with 👍. It lets us see which fixes and features are demanded by the most users.
We're using Polar.sh so you can upvote and help fund this issue. It may incentivize some developers to contribute to this project and fix some bugs.
Funded developer receives the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.
Is there an existing issue for this?
Current Behavior
Controllers do not retain the last assigned .gamecontroller profile between app reboots
Expected Behavior
No response
Steps To Reproduce
Environment
Anything else?
I've got an ultimarc ipac ultimate I/O board (https://www.ultimarc.com/control-interfaces/i-pacs/i-pac-ultimate-i-o/), which creates two distinct dinput controllers through one usb. This may be the root of the problem, since it may think that both controllers are actually the same controller, despite it creating two separate entries in the UI.
Upvote & Fund