Emulator Issues #13066
closedmouse/trackpad buttons don't work for emulated Wii Remote
0%
Description
Game Name?
N/A
Game ID? (right click the game in the game list, Properties, Info tab)
N/A
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
N/A
What's the problem? Describe what went wrong.
I have right-click set to A button and left-click set to B button for an emulated Wii Remote. When I launch a game, clicking the mouse buttons does nothing. Also in the controller configuration (Options -> Controller Settings -> Wii Remote 1: Emulated Wii Remote -> Configure -> General and Options), I cannot record mouse button clicks. That is, I press on the button to set a mapping for the A button, and then clicking the left or right mouse button does nothing; instead, the mapping goes back to what it was before after a ~5 second timeout. I also tried trackpad buttons and that has the same issue.
What steps will reproduce the problem?
Go to Options -> Controller Settings. Select Emulate the Wii's Bluetooth adapter. Set Wii Remote 1 to Emulated Wii Remote, and then select Configure. In the General and Options tab, in the Buttons section, beside A, click the button to set a new binding. Press the left mouse button.
Expected: binding for A gets set to the left mouse button
Actual: nothing
Set the binding for the A button of an emulated Wii Remote to a mouse button. Start a game.
Expected: can use emulated A button be pressing the mouse button.
Actual: the mouse button does nothing
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes, it is present in the latest development release: version 5.0-17556. It is not present in version 5.0-16793.
Is the issue present in the latest stable version?
I get an error when I try to checkout the stable branch:
error: The following untracked working tree files would be overwritten by checkout:
Externals/libusb/libusb/Makefile.am
Please move or remove them before you switch branches.
Aborting
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
I was able to run version 5.0-16793 by downgrading with my package manager, and this does not have the issue. In Help -> About, this version says it is Revision 3cd82b619388d0877436390093a6edc2319a6904. Unfortunately, when I try to checkout this version in git, it does not compile. I get an error:
Source/Core/Common/MsgHandler.h:44:22: error: ‘is_compile_string’ is not a member of ‘fmt’
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
N/A
What are your PC specifications? (CPU, GPU, Operating System, more)
CPU: Intel Core i7-8850H
graphics: Intel UHD Graphics 630
OS: Arch Linux
mouse: Logitech M585
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Let me know if I can be of further help. Though so far, I've only been able to compile the master branch from source.
Updated by JosJuice about 2 years ago
- Is duplicate of Emulator Issues #12913: Mouse clicks not recognized on Linux + Qt6 added
Updated by JosJuice about 2 years ago
- Status changed from New to Duplicate
Sounds like issue 12913. Please let me know if you think it's a separate issue.
Updated by dbear496 about 2 years ago
I suppose it could be a duplicate -- the symptoms are the same. However, the version numbers don't match up: I determined that Dolphin 5.0-16793 is fine whereas issue #12913 reports Dolphin 5.0-16393 or newer is broken.
Updated by JosJuice about 2 years ago
According to #12913, it's caused by using Qt 6 instead of Qt 5, and that's not tightly coupled to which revision of Dolphin you're using. Which version of Qt you're getting depends on where you're getting Dolphin from, or how you're building it.
Updated by dbear496 about 2 years ago
Oh, that makes sense. In that case, it probably is a duplicate.