Emulator Issues #7536
closed
d3d_fullscreen breaks input for some devices on OS X
0%
Description
Game Name?
All Games (At least Gamecube games, haven't been able to try Wii games yet)
Game ID?
N/A
What's the problem? Describe what went wrong in few words.
When under the GCPad configuration settings, it recognizes all of my control inputs like mouse, keyboard, generic USB gamepad, etc. I can also map buttons perfectly fine, however the indicator lights at the bottom do not light up at all and when in-game the controller simply doesn't work and it's as if I am not pressing any buttons at all.
However even on the working versions of Dolphin that I have tried this, the indicator lights also do not light up, even when it works in-game. So it's not that big of a deal, just a minor detail.
What did you expect to happen instead?
The controller to work
What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]
- Boot up a game (I've only been able to test Gamecube for the time being)
- Go to GCPad and reselect the controller (because even on working versions I have to reselect the controller even if it's already selected to make it work)
- Now in-game the control inputs should not work whatsoever.
Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
4.0-2380
4.0-2368
4.0-2330
4.0-2299
4.0-2317
4.0-2286
4.0-2295
4.0-2289
4.0-2286
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
4.0-2227
4.0-2229
4.0-2238
4.0-2250
4.0-2263
Seems like all builds after 4.0-2263 have this problem.
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
OS: Mac OS X 10.9.4
CPU: Intel Core i7 3930K @ 4.6GHz
GPU: MSi Lightning GTX680
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
I've tried a USB N64 controller and my keyboard on my front USB 2.0 and 3.0 ports as well as my back USB 2.0 and USB 3.0 ports with no change.
Here is a screenshot of my GCPad settings
https://www.dropbox.com/s/k9wfwghijnquii0/Screenshot%202014-08-02%2014.43.52.png
Updated by pauldacheez over 10 years ago
- Status changed from New to Accepted
- Regression set to Yes
- Operating system OS X added
I dunno how the hell D3D fullscreen changes managed to break input on OS X for you, but, well, I've seen weirder things.
Input works for me with my Wii U Pro Controller connected via WJoy, though I do have the same issue with the input configs (both GCPad/emu-'mote) not displaying any input for any device (this used to work, not too long ago). I'll make a separate issue for that since it doesn't seem to be related.
https://github.com/dolphin-emu/dolphin/commit/8e865f38489f204ea2fabf2cee3acad1a215deff
https://dolphin-emu.org/download/dev/8e865f38489f204ea2fabf2cee3acad1a215deff/
Updated by Armada over 10 years ago
Please try this build: http://dl.dolphin-emu.org/prs/pr-683-dolphin-latest.dmg
Updated by Blaziken584 over 10 years ago
I'm very confused as well, it doesn't seem correlated at all. I haven't tried input through Bluetooth yet as all of my bluetooth stuff is not with me, so I'll try that as soon as possible. It could be just related to USB devices. Though the issue could have been a build between 4.0-2263 and 4.0-2286 since between those two builds there is a gap where it skips quite a few revisions, so it was probably something in-between.
As for the 4.0-2374-dirty build, it works perfectly fine, so it must be something after that build.
Updated by Armada over 10 years ago
Blaziken584, the reason the revisions are skipped is because a new feature was merged which has some revisions internally. I implemented that feature and we've since found a few issues with it.
One of those that seems related to your issue is fixed in the build I posted above, please test it.
Updated by Blaziken584 over 10 years ago
Just noticed that the build given to me was uploaded today. I decided to try a few more dirty builds to help narrow it down, so here is what I came up with.
Works
pr-683 (4.0-2374-dirty)
pr-669 (4.0-2250-dirty)
pr-672 (4.0-2258-dirty)
Issue
pr-684 (4.0-2301-dirty)
pr-695 (4.0-2324-dirty)
pr-673 (4.0-2286-dirty)
pr-678 (4.0-2299-dirty)
pr-682 (4.0-2299-dirty)
pr-673 seems to be the first version that I encounter the issue, as pr-672 works fine for me. However pr-683 also works for me which was just uploaded today.
I might be butchering my findings since I don't know exactly how this system works, but that's what I could gather.
But yes you are correct, the issue I am encountering is completely fixed in the build that you posted above. (I did the rest of that testing up above before you commented)
Updated by JMC4789 over 10 years ago
Hey um, PRs are unrelated to one another; it's just that the bug was put into master at 2286, so every PR based on a newer build would have the issue. If 2374 works, then all you need to do is wait for it to be merged.
Updated by Blaziken584 over 10 years ago
Alright, thanks for clearing it up, I figured that I had been butchering it. Looking forward to the merge, keep up the good work =)
Updated by Armada over 10 years ago
- Status changed from Accepted to Fix pending
Fixed in PR683: https://github.com/dolphin-emu/dolphin/pull/683
Updated by Armada over 10 years ago
However even on the working versions of Dolphin that I have tried this, the indicator lights also do not light up, even when it works in-game. So it's not that big of a deal, just a minor detail.
This part of the issue is not yet fixed and unrelated to the D3D exclusive fullscreen merge. Please refer to ticket 7537 for more information: https://code.google.com/p/dolphin-emu/issues/detail?id=7537
Updated by MayImilae over 10 years ago
- Status changed from Fix pending to Fixed
Merged in 4.0-2394 -> https://dolphin-emu.org/download/dev/d8d99f919cd3f14f1b450e1f36f4a7e21cc64e0a/