Retroarch fails to save controller config for virtual devices
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
Controller configs fail to save when using virtual controllers. Due to the nature of my cabinet build, my two "controllers" are actually 4 different players' buttons wired into 2 gamepad boards. To make these compatible with retroarch, I'm creating 4 virtual joysticks with evsieve and mapping events from my 2 controllers to those virtual devices (which is tested and working).
Due to these being virtual devices, they don't have serial numbers, versions, product numbers, or vendor identifiers, which I believe is causing issues with saving configurations within retroarch.
I ran into issues with not being able to manually create configurations for this reason as well.
Expected behavior
To be able to save configurations or autoconfig any joystick, regardless of if it is physical or siimulated
Actual behavior
Retroarch throws errors or crashes, but generally does not save the configuration for the joysticks.
Steps to reproduce the bug
- Create an
evsievescript to map events from some input device to a new virtual joystick - Try to create and save a controller configuration for the new joystick
For reference, my evsieve script can be found here
Version/Commit
You can find this information under Information/System Information
Environment information
- OS: Ubuntu
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
Start by reproducing the failure with the linked evsieve setup and a virtual joystick, then trace RetroArch's controller configuration and autoconfig handling. Done means a virtual joystick can be configured and saved without errors or crashes, but the issue names no source files or tests to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux, ubuntu
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100