Emulator

r5249 is the problem. Also affects trauma center second opinion.

r5272 causes the "bobbing", see my comment there:
http://code.google.com/p/dolphin-emu/source/detail?r=5272#cg_1270472416577782

Not sure about r5249 tho?

indeed this started to happen in r5272 and affects all games here, i.e. wii sports
and new smb wii.

using x64 build on win 7 pro, phenom ii x4 920, radeon 4550.

switching off xfb instantly fixes the bobbing.

well, 5249 caused no bobbing on most games, just trauma center second opinion. 5272
made all games bob.

zelda wind waker also has this bobbing problem

I'm still seeing this behavior in every single new build. Is this really fixed?

Issue 2624 has been merged into this issue.

to let this issue clear,the bobing effect is caused by interlacing, we compensate
interlacing by decresing the efb one line in the botton field this aligns the fields
and remove interlacing effect, but some games makes the same compensation in their
code, this cause this games to bop up and down 2 pixels.

So I guess properly implementing interlacing would fix this issue?

Properly implementing interlacing should be easy enough (even without XFB emulation) by using a different shader for the "EFB texture"->"screen" copy (i.e. a shader which would drop every second framebuffer line, albeit it'll be a bit harder to make this work for arbitrary output resolution).

You don't need to emulate all of it, just enough so you actually know which field VI is actually going to render so you can compensate correctly.

...by using a different shader for the "EFB texture"->"screen" copy...

Interlacing is actually done at a later step, when VI scans the XFB out to screen. At the time of the copy, it's unknown which field is going to be rendered to screen (and it's often both fields)

I know. My point was that we would do that when XFB emulation is disabled.

That's why I was talking about the "EFB texture"->"screen" copy, not what's referred to as an EFB copy in the GX API.