Performance on OS X has always been pretty weird. In your case, it might be that it's dropping down to Apple's software renderer instead of actually using your GPU since Dolphin may, for example, be using some GL function that was recently broken in your GPU's drivers. Open up Activity Monitor or another app that monitors CPU usage – if you see a process named "cvmcompiler" taking up a ton of CPU, that's Apple's software renderer.
Short story: I was using beta builds of OS X 10.8.3/4 while testing GLSL-master on OS X with my shitty Intel HD 3000, and at first it would use broken hardware rendering in the betas, then later it started dropping down to software rendering. Eventually it started working decently with hardware rendering, but it still had major issues (e.g. hardlocking the OS) that made Dolphin unusable until someone finally figured out that the NV_primitive_restart GL extension was causing my HD 3000-specific issues.
Short story: I was using beta builds of OS X 10.8.3/4 while testing GLSL-master on OS X with my shitty Intel HD 3000, and at first it would use broken hardware rendering in the betas, then later it started dropping down to software rendering. Eventually it started working decently with hardware rendering, but it still had major issues (e.g. hardlocking the OS) that made Dolphin unusable until someone finally figured out that the NV_primitive_restart GL extension was causing my HD 3000-specific issues.
<@skid_au> fishing resort is still broken: http://i.imgur.com/dvPiQKg.png
<@neobrain> dafuq
<+JMC47> no dude, you're just holding the postcard upside down
----------------------------------------
<@Lioncash> pauldachz in charge of shitposting :^)
<@neobrain> dafuq
<+JMC47> no dude, you're just holding the postcard upside down
----------------------------------------
<@Lioncash> pauldachz in charge of shitposting :^)