+- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org)
+-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support)
+--- Forum: Controllers (https://forums.dolphin-emu.org/Forum-controllers)
+--- Thread: OSX Mountain Lion Wiimote doesn't do anything after connected (/Thread-osx-mountain-lion-wiimote-doesn-t-do-anything-after-connected)
OSX Mountain Lion Wiimote doesn't do anything after connected - barrington - 01-27-2014
Hello all!
I've successfully run dolphin on my macbook pro (lion) with the remote connecting and was able to play games fine, but for some reason I can't figure out for the life of me why I can't get my wiimote to respond on my mountain lion desktop. The issue I'm running into is this: The wiimote connects fine (1 blue LED on the remote), I can connect/disconnect the wiimote while running a game (testing with xenoblade chronicles), but none of the buttons on the wiimote or nunchuck do anything at all. I'm stuck at the "press any button" screen no matter what I do or what version I run. I've tried the official 4.0, the ML 3.5 patched release, and any dev builds available.
Not gonna lie, I've been feeling like Homer Simpson when he's struggling to find the "any" key. Any help would be appreciated. Thanks!
RE: OSX Mountain Lion Wiimote doesn't do anything after connected - KHg8m3r - 01-27-2014
Did you press 1 and 2 at the same time once the game started?
Is it the Wiimote Plus RVL-CNT-01-TR?
RE: OSX Mountain Lion Wiimote doesn't do anything after connected - barrington - 01-27-2014
(01-27-2014, 04:00 PM)KHg8m3r Wrote: Did you press 1 and 2 at the same time once the game started?
Is it the Wiimote Plus RVL-CNT-01-TR?
I get a solid blue light in the "1" spot on the remote after syncing it in the wiimote settings. Once the game loads, it's still solid in the 1st player area and pressing 1+2 does nothing.
My bluetooth shows it as RVL-CNT-01, so I think I have the right model wiimote for this.
RE: OSX Mountain Lion Wiimote doesn't do anything after connected - KHg8m3r - 01-28-2014
Check the actual wiimote for the model.
Are you 100% up to date?
The only other thing i can think of is to use Bootcamp and use Windows with the Toshiba stack
RE: OSX Mountain Lion Wiimote doesn't do anything after connected - barrington - 01-28-2014
(01-28-2014, 02:35 AM)KHg8m3r Wrote: Check the actual wiimote for the model.
Are you 100% up to date?
The only other thing i can think of is to use Bootcamp and use Windows with the Toshiba stack
The model number inside the wiimote is RVL-003. By 100% up to date, I'm assuming you mean running the latest official 4.0 software, which I am (please correct me if you were talking about something else).
It's just weird...as the wiimote works perfectly on my laptop mbp.
RE: OSX Mountain Lion Wiimote doesn't do anything after connected - KHg8m3r - 01-28-2014
Its possible that the different Macs have different Bluetooth adapters....
By up to date, I meant ant software updates for your Mac
RE: OSX Mountain Lion Wiimote doesn't do anything after connected - barrington - 01-28-2014
(01-28-2014, 07:54 AM)KHg8m3r Wrote: Its possible that the different Macs have different Bluetooth adapters....
By up to date, I meant ant software updates for your Mac
I'm running 10.8.4 on a hackintosh...haven't updated yet because I hate having to go back and redo all my drivers. Do you think 10.8.5 would fix it?
In addition, I downloaded darwinremote to see if it will recognize any movement or button presses there...it will connect fine but doesn't register any activity on the remotes.
RE: OSX Mountain Lion Wiimote doesn't do anything after connected - KHg8m3r - 01-29-2014
Yeah, not sure how well a hackintosh likes other drivers....
Either try bootcamp and windows, or update that hackintosh. There's most likely a driver issue
RE: OSX Mountain Lion Wiimote doesn't do anything after connected - pauldacheez - 01-30-2014
I can't say whether Wii Remotes are broken on 10.9 on real Macs as I haven't tested them recently, but they worked fine on 10.8. I'd blame your dongle or whatever drivers are in use.