Emulator

The only other game I have is Bomberman Blast and it works fine with the tev_fixes_new.

I guess integer division in light shader which will fall back to software emulation.

We had lots of integer division in the first versions after the tev merge, so what is the performance of Bomberman Blast with the first tev-fixes build?

for Bomberman Blast I get ~55fps. It is the same frame rate as I got with pre-tev-fixes build.

On this build? http://dl.dolphin-emu.org/builds/dolphin-master-4.0-1192.dmg

If the issue is really the integer division, https://github.com/dolphin-emu/dolphin/pull/360 will fix that. (I have no idea if that's actually the issue, though...)

Wickmark yes, this build 4.0-1192 creates the problem.
Maguma Is there a build with your patch?

and yes there is no problem with Bomberman on the build 4.0-1192

What happens when you use 4.0-1288 and newer?

4.0-1288 and newer don't improve things for me

I have compiled dolphin with the patch https://github.com/dolphin-emu/dolphin/pull/360 and it didn't help.

small update: new version of the intel driver from OS X 10.9.3 doesn't change anything for this problem.

new observation: The new OS X 10.10 beta 2 improves fps by a factor of 2 with respect to OS X 10.9. Now it is 4 fps

When it's doing this run-everything-at-4-fps thing, is there a CVMCompiler process using 100% CPU? If so, that's the same issue I'm running into where rendering certain things (e.g. Metroid Prime's water) makes it drop down to software rendering.

Whoever's maintaining the Intel HD 3000 drivers at Apple needs a kick in the pants.

Hmm, the CVMCompiler process is there indeed. But it is a bit more complicated. First, when I start NSMB and the game asks to hold wiimote properly everything works smoothly. Then I see the black screen and the game starts to appear in the growing hole in centre of the screen at this moment the CVMCompiler kicks in. It is using 100% CPU and the frame rate is actually 1 fps at this moment. After some time CVMCompiler disappears and the game runs steadily at 4 fps.

pauldacheez and I have debugged which feature did fall back to software, but it was something in the shader itself :/

Do we still use integer divisation in some places?

Ok, so I have an extra reason to update my macbook :)