Dolphinbar Mouse click won't bind as lightgun trigger input
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
I am using Mayflash Dolphinbar in mode 2 where it simulates a mouse. 1.9.1 is the last version that the mouse click (left and right) from Dolphinbar's simulated mouse can be bound in Input settings AND works in game (say Alien 3 using the FBNeo core). from 1.9.2 onwards, the click can be bound / detected in the Input settings but not working in game. In the latest version (tested in 1.11.1), the click cannot be bound in the Input settings at all. The UI however responds to the mouse click for drag gestures.
Expected behavior
Dolphinbar simulated mouse click should be able to be bound in Input settings and works in game.
Actual behavior
Input settings either would not bind the mouse click from Dolphinbar or it does not work in game
Steps to reproduce the bug
- Use a Dolphinbar in mode 2 to use Wii-mote to simulate a mouse
- Try to bind Wii-mote trigger as P1 gun trigger
- If it can be bound, test in FBNeo with any light gun games with P1 input set to lightgun
Bisect Results
1.9.1 is the last working version, breaks in 1.9.2 until the latest 1.11.1 as of now.
- RetroArch: 1.11.1
Environment information
- OS: Windows 10 64 bit
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 Dolphinbar mode 2 setup on Windows 10, comparing RetroArch 1.9.1, 1.9.2, and 1.11.1. Start with the Input settings binding path and then test the bound trigger in an FBNeo lightgun game. Done means the simulated mouse click can be bound and works in-game as the P1 lightgun trigger.
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