Emulator Issues #4532
closedReal wiimote rumble becomes stuck now (r7559 regression)
0%
Description
What steps will reproduce the problem?
- Play a game. This repros in RE:UC, RE:DC, Ghost Squad and HOD:Overkill.
- Get in game and start firing (trigger a bunch of rumble events).
What is the expected output? What do you see instead?
Very, very frequently the wiimote will rumble but never stop. It'll last indefinetely until you go the Home screen or in some cases trigger another rumble event. But then it usually just gets stuck again.
Dolphin version with the problem? Other Dolphin version without the
problem?
This does not repro for me with the speaker enabled.
32-bit or 64-bit and any other build parameters?
64bit
OS version and versions of tools/libraries used?
Win7
Please provide any additional information below.
None.
Updated by wespipes69 over 13 years ago
Can anyone confirm this? It's pretty serious regression. I would think it would have behaved like it did before the speaker functionality went in place, but apparantly not.Probably happens in more games than this obviously.
It even happens to extent in SMG in certain places - it does recover in that game though, but the rumble persists for a loooooong time.
Updated by skidau over 13 years ago
Yes, I can reproduce it in HOD:Overkill. Dunno how to fix it tho.
Updated by hatarumoroboshi over 13 years ago
Problem confirmed with Disney Epic Mickey: for example using r7251 and disabling Wiimote speaker in the general Wii tab, you feel the rumble on the Wiimote every time you spindle with it; with r7559 and Wiimote speaker disabled in the game properties instead, the rumble doesn't work in 95% of cases when you spindle, and when it randomly rumbles, the rumble get stuck so you have to go to the menu to make it stop.
Updated by wespipes69 over 13 years ago
That's a good point hatarumo. I noticed that, but you just confirmed it. Not only does the rumble get stuck sometimes, but other times it does not function when it should. So looks like real wiimote rumble in general is just fubar. :)
Updated by pascal.jouy over 13 years ago
I can confirm this with DKCR with Disable Wiimote speaker ticked.
It did not happen before this option shown up (although DKCR was unplayable before, due to big Wiimote lag).
Updated by manu2.05 over 13 years ago
Hello :)
I confirm too exactly the same issue with DKCR & same OS (with 7559 & 7564).
but also, I have a similar issue with rumble becomes stuck (if this can be help):
- I open Sport Island 2 / Wii Party / Wii Sport (certainly others)
- I hover and hover again in game menu (with rumble effect) with 1 or 2 wiimotes
- when there are lot of rumble effect during few times => the rumble becomes stuck
& no way for stop that !!! (here, enter wii menu don't stop rumble) - if there are 2 wiimotes, it's always the second wiimote which stuck ! ( i have tested with my 3 wiimotes in any sense)
- I must turn off the crazy wiimote, delete driver & pairing again.
before write, I have retested today in Sport Island 2 with 7555 & 7564 - but I didn't note if this issue has began before 7555 when I played with Wii Party / Wii Sport.
excuse me for my approximative english and if my comment is useless... ^^'
Updated by hatarumoroboshi over 13 years ago
With and without the option "Disable Wiimote speaker" I don't have problems in Wii Sports and Wii Party, they both seem to work perfectly here (r7559 - WinXP 32-bit - original Nintendo Wii Remote Plus).
In fact from my tests I can reproduce the rumble problem only with the games that don't work since the introduction of the speaker and need the option to be enabled (like Disney Epic Mickey and Red Steel 2), other games instead work for me the same way with or without that option enabled (like for example Wii Sports, Wii Party, Dead Rising, NSMB, Goldeneye and Ivy the Kiwy).
Updated by manu2.05 over 13 years ago
Yes, yes I think too that this is not exactly the same bug (I said in my first sentence that I had this specific issue too )
but good for you you don't have my issue :)
it was just for reporting potential link between this 2 bugs (I had never read in the forum others cases like mine).
in my case, I need to try and try again with lot of rumble effect for reproduce this issue (with or without option speaker) but in your case it's an immediat & constant bug (first enemy).
You right, it's also possible that my generic bluetooth 2.0 or my generic wiimotes are in fault ^^'...
I will receive quickly an official fourth wiimote & a bluetooth dongle 2.1 => I will test again after that ;)
but - why I can resolve the wiimote speaker issue in Dk (by enter the wii menu) if my wiimotes are bad - this would be a constant stuck like in others games, no ?
it's for that I decided to post ^^' - this is not logic for me.
Updated by wespipes69 over 13 years ago
Hate to say it (trust me) but shouldn't this be a 3.0 blocker? It's a definete regression which effectively breaks wiimote rumble. I have to turn off the motor to play games now.
Updated by BillFleming11 over 13 years ago
I also had the rumbling get stuck in RE4 in one of the recent revs. (Using LLE recompiler)
Updated by manu2.05 over 13 years ago
new again test with official wiimote and bluetooth 2.1 (Belkin - F8T016ng like here http://www.dolphin-emulator.com/support.html#wiimote ) & r7577 & r7589
for DK : wiimote rumble turns too long time, but doesn't stuck !! (no need to enter home)
for other issue I said (stuck when lot of consecutive "IR rumble" => bug apparently disappear too
Finally, I think my bluetooth 2.0 was in fault :/ & now with 2.1, no problem for the moment :) .
Updated by hatarumoroboshi over 13 years ago
Is there a reason why the option in the Wii general tab for removing the Wiimote speaker used until r7271 (included) worked perfectly, while the new one in the game properties doesn't work the same way and causes rumble problems?
Using the old option instead of the new one wouldn't fix this problem?
If not, maybe there are other "line codes" that were added in r7272 and that have to be disabled by the option.
Updated by MofoMan2000 over 13 years ago
Good. Now that this is a 3.0 blocker (actually the only remaining 3.0 blocker) maybe it'll actually get some attention. It's a pretty big regression and wiimote speaker stuff shouldn't be causing this kind of bug.
Updated by Anonymous over 13 years ago
I agree this should be a blocker. I also think we should just revert all the wiimote crap (essentially killing speaker support), obviously no one is going to fix it. Then we can release and maybe the project will be unstuckified.
Updated by MofoMan2000 over 13 years ago
Though I generally disapprove of removing such an awesome feature, for the purposes of the release it may be best. It can be added back at a later date (after 3.0). Certainly it shouldn't be discarded, but it should only be added back into trunk if it is intended to be fixed/maintained. Just my two cents.
This is you guys' project, really you can do whatever the hell you want with it.
Updated by Billiard26 over 13 years ago
- Priority set to Urgent
The problem is known, I have explained it to skidau.
He almost had a working fix.
The wiimote can be told to stop/start rumbling within speaker reports.
When wiimote speaker is disabled, those dropped speaker reports need to be replaced with rumble stop/start reports, complicating the real wiimote code further.
Updated by skidau over 13 years ago
I think we should wrap all of the wiimote speaker stuff with the game properties option. Bit ugly for now, but it'll let us get 3.0 out the door.
Updated by skidau over 13 years ago
I'll try to find some time to test that out and commit it in a few hours. If that doesn't work, I'll remove all of the speaker code.
Updated by skidau over 13 years ago
- Status changed from New to Fixed
This issue was closed by revision r7597.