isXander / isXander/Controlify
[Feature] Disable "Map Controller" for specific device
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 341
- Forks
- 97
- Avg merge
- 1h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
I have a flightstick I use for Elite Dangerous, it has... like no deadzone, which causes Controlify to spasm the fek out when I launch the game and refuse to let me use it until Controlify detects a mouse-input/controller conflict and disables controller input
Describe the solution you'd like
Add a "Disable this Device" button on this screen, which permanently disables the device until re-enabled in controlify menu
Describe alternatives you've considered
Unplugging the flightstick.
Contributor guide
No contributing guide indexed for this repository
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 at the device screen shown in the issue and trace how Controlify detects devices and exposes its menu. Add a per-device disable action that persists until re-enabled in the Controlify menu, and verify that the selected flightstick no longer supplies controller input after launching the game.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100