Wiimote and save states don't work?

02-07-2013, 01:42 AM #1

I've tried searching forums, but nothing comes up... Just asking if anyone else is having this problem:
When playing ANY Wii game perfect or otherwise, wiimote will not work after loading a save state, even though it shows as connected in Dolphin. Switching to a different controller works, then switching back to real wiimote still does not work.

Dolphin 3.5-367 x64

Windows 7 x64

Core i5-3570k 3.40ghz

8gb RAM

Nvidia Geforce GTX 560Ti

**ExtremeDude2** · 02-07-2013, 01:44 AM #2

Do you have reconect on state load enabled? Also why even use save states?

02-07-2013, 02:14 AM #3

I have 2 Wii consoles.. I play emulators most of the time because they have save states. Yes, I do have the reconnect at state load checked, I just read older posts about how this was an older issue and thought it was fixed.

**mbc07** · 02-07-2013, 02:35 AM #4

Using Alt+F5 twice after loading a save state works for me...

02-07-2013, 03:35 AM #5

Yeah, tried that and dolphin then seems to freeze then crash... I might try deleting all files except for ISO's and starting over. I thought other folks might be having similar issues

**RachelB** · (This post was last modified: 02-07-2013, 05:55 AM by RachelB.)

Disable the reload wiimote hack. If it still stops working, then just reconnect it manually.

02-09-2013, 02:57 AM #7

Hi.. Been lurking for a long time but joined to give feedback on this issue. It seems that this problem has returned with recent builds (sometime after 3.5-33x). I've tried all of the obvious and other suggested fixes and work-arounds with no luck. Once this issue occurs, the only way I've found to fix it is to stop/restart emulation and not use the save-state.

I thought that it may be an issue with my 'user' folder that I copy from build-to-build so I unpacked 3.5-392, setup ISO folder and paired my Wiimote (left everything else default); The issue still persists with a 'clean' copy of Dolphin. I'd go back to pre-33x build but I noticed a performance improvement in some games since then and I'm reluctant to go back Undecided

I'm running Win7 x64 SP1, AMD Trinity APU A10-5800K (using APU graphics) 8GB DDR3-1866Mhz, OCZ Vertex3 OS SSD, 4x 1TB WD 7200RPM Black RAID5 (where the emu and ISO files are located), Asus Xonar DS 7.1 Audio.

I've seen the issue in all of the current games that I'm playing: DKC Returns, Wii Mario Kart, New SMB, Resident Evil 4.

02-10-2013, 05:29 AM #8

@ ajcz66 - I reverted back to 3.5-332 and save states work. When I get a few minutes I intend to find the exact version where the issue appeared (or reappeared) if someone hasn't done it already; hopefully that will help the problem get some more traction.

**RachelB** · (This post was last modified: 02-10-2013, 07:44 AM by RachelB.)

You may want to test right before 3.5-367. There were some changes to real wiimotes there. You may also want to test the latest, as there have been more fixes for them after that.

02-22-2013, 05:39 AM **#10**

(02-10-2013, 07:43 AM)RachelB Wrote: You may want to test right before 3.5-367. There were some changes to real wiimotes there. You may also want to test the latest, as there have been more fixes for them after that.

OK. I finally had time to test this. It seems that 367 (or maybe 358.. going off of memory) is the version where the issue crops up. With further experimentation I've found that disabling 'reconnect wiimote on state load' fixes the issue (occasionally have the nunchuck issue; fixed by unplugging and replugging the nunchuck). I'm now using 414 with no issues.

Can a future build have that option 'unchecked' by default? It seems to break all of the games I tested.