Dolphin doesn't detect my wiimote on OSX

[leodelan]

Hi, I'm new here! I have just installed DarwinRemote 0.6, opened it and connected my wiimote without any problem (when I press a button, it's detected). Then I opened Dolphin 3.5-367, clicked on Wiimote, selected 'Real Wiimote' in the Wiimote 1 and pressed 'refresh' below, but I still get '0 connected'. Nothing is crashing nor an error. Any idea? Thanks a lot!
(running OSX 10.8.2)

[Shonumi]

First, see if using the latest revision makes any difference. You're likely using an outdated build from the old site. The newest revisions can be found here: http://dolphin-emu.org/download/ With any luck, that might be all you need to do.

[pauldacheez]

DarwiinRemote won't let Dolphin have any access to the Wii Remote while the remote's connected via DarwiinRemote. Quit that, disconnect the remote (turn Bluetooth off and on if necessary), then connect it by pressing the red Sync button underneath the remote's battery cover and clicking "Refresh" in Dolphin.

Also, yeah, use a newer build as Shonumi suggests. In newer builds you don't even need to click "Refresh" in Dolphin, you just need to either open the Wii Remote settings or boot up a Wii game. (But the same branch that added that functionality also broke real Wii Remote input for me (on both my Macs), so be aware of that and use 3.5-432 or earlier if in the newest development revisions you find that buttons don't work.)

[leodelan]

DarwiinRemote won't let Dolphin have any access to the Wii Remote while the remote's connected via DarwiinRemote. Quit that, disconnect the remote (turn Bluetooth off and on if necessary), then connect it by pressing the red Sync button underneath the remote's battery cover and clicking "Refresh" in Dolphin.

Also, yeah, use a newer build as Shonumi suggests. In newer builds you don't even need to click "Refresh" in Dolphin, you just need to either open the Wii Remote settings or boot up a Wii game. (But the same branch that added that functionality also broke real Wii Remote input for me (on both my Macs), so be aware of that and use 3.5-432 or earlier if in the newest development revisions you find that buttons don't work.)

thank you! I installed the version you mentioned, when I click 'refresh' I get '1 connected' but the wiimote keep blinking. Looks like it's stuck somewhere. Should I try newer version?

[leodelan]

ok, using the latest version worked straight away
but it looks the specs of my Macbook Pro are a bit too low to support wii games!

[pauldacheez]

Eh, yeah... The poor old GeForce 320M isn't even as good as an Intel HD 3000 in most cases, and the HD 3000's what I consider to be the bare minimum requirement for Dolphin these days. (But, before you immediately scramble for your other MacBook with an HD 3000, be aware that there's a driver bug that makes it run at 0-5 fps in-game. Fixed in 10.8.4 beta, but it's currently replaced with another issue where stuff looks broken.)

Also, do buttons work in-game? My remotes connect fine, but the input doesn't work, which I have to yell at Billiard about. :\

[admin89]

The poor old GeForce 320M isn't even as good as an Intel HD 3000 in most cases

Uhm , no
Intel graphic drivers are the worst ever and Intel HD 3000 is not even on par with 320M (For Example : Starcraft 2 low setings : 68 vs 110 ; Black OP 1 - low : 26 vs 41 ) . Thus , Nvidia GT 320M is noticeably faster
320M has 25.3 GB/s memory bandwidth , it can handle 2xIR (1280x1056)

[pauldacheez]

Eh, yeah, whatever. I was going by the first post in this MacRumors thread, but I didn't read the rest of the thing until after I posted. :P http://forums.macrumors.com/showthread.php?t=1102927

Seems that later on they mention that while Intel drivers may be worse than Nvidia's on Windows, Nvidia drivers are comparatively *much* worse on OS X - I mean, remember the whole OS X lighting bug thing? All the OS X drivers are mainly developed by Apple with some indeterminate amount of input/assistance from AMD/Nvidia/Intel, so the Windows driver rules don't really apply.

I was going by results, though, where my mom's MacBook Pro (2.4 GHz Nehalem i5, 320M) kept wavering between 45-60 fps on the title screen of Animal Crossing while my MacBook Air (1.7 GHz Sandy Bridge i5-2557M (that can apparently turbo up to 2.6?), HD 3000) gets a solid 60 fps on the title screen and at almost all points in-game (even with LLE, somehow). Obviously an unfair comparison, considering the CPU difference and the OS difference (MBP's still running 10.7, MBA's on 10.8.4). Even more unfair considering I was testing a clean post-GLSL-master build on the MBP and a pre-GLSL-master build with a pile of compiler tweaks enabled on the MBA. :P

Therefore, yeah, measuring performance is fucking ridiculous and shouldn't be done, especially with *my* measuring sticks. v_v;

[admin89]

2.4 GHz Nehalem

It's i5 520M @ 2.4GHz -> 2.67GHz with Turbo Boost

i5-2557M (that can apparently turbo up to 2.6?)

2.7GHz is single core turbo
It should run at 2.4GHz (2 cores active)
http://www.cpu-world.com/CPUs/Core_i5/In...2557M.html
i5 2557M may be faster (or slower) than i5 520M (Turbo Boost frequency of Ultra Low voltage CPU is pretty beefy to calculate because it does depend on the cooling and power consumption of the laptop )
In single threaded performance , i5 2557M (2.7GHz) can chop off my i5 480M @ 2.9GHz (3419 vs 3192.3)
In multithreaded performance , i5 2557 (2.4GHz) is abit slower than i5 520M @ 2.67GHz (6533.5 vs 6660.8)
In the end , i couldn't figure out this

where my mom's MacBook Pro kept wavering between 45-60 fps on the title screen of Animal Crossing while my MacBook Air (1.7 GHz Sandy Bridge i5-2557M gets a solid 60 fps on the title screen and at almost all points in-game

Ok , I will shut up now xD