Emulator

In v6304 the problem still present. FSP drop to <30 then immediately to >60, simply if the ball was hit by AI or player.

I don't known if it's a FIFO bug or something related to GPU, but it's so obvious and in an enviroment (Wii sport Tennis Table) where there isn't anything special, no particular change of graphics, rendering etc.. Maybe this situation can help the devs.

DX9, OGL or DX11 same problem.

32bit or 64bit nothing change.

Maybe you don't see this because your system isn't very powerful...so you cannot see a huge drop in framerate because maybe you're playing costantly at low fps...

I usually set EFB copy to Texture. If I use EFB to RAM I got much lower fps, still suddenly changing up and down in the same conditions esplained above. So my guess is something related to FIFO, not the GPU.

My fps Constantly at 50-60 fps with anti-aliasing = none and anisotropic 1x ; only drop when i play with multi-player but still 30-40 fps

Nex, do you have costant FPS in Table Tennis? (EFB to Texture)

@d.sangio.. yes no stutter in table tennis with efb to texture and DSP HLE emulation, did you try fresh copy of dolphin?

@Nexta.. I'm usually use a fresh install of Dolphin. BTW I'm with Nvidia GT9600 with latest driver, do you use ATI?

yes, my vga is ATI HD4650.

I have a Coreduo E8400 with Ati hd4850 on WinXP 32 bit and this particular game still has the usual lot of wierd slowdowns (from 60 to 45 fps and back)...

latest revision didn't fix this issue. I think it would be good to fix it before 3.0 release.

No change also with latest Cache-rewrite. Same problem with DX9 DX11 or OGL.
Sound like a bottleneck in CPU emulation, but it's just a humble guess.

Further testing with recent version.
If you disable frame limiter, you can see the fps drom from 130% to around 70% speed as soon the player hit the ball. The fps again pop up top 130% speed, as soon the CPU hit the ball.
It happens with any video back end, so it evidence some kind of bottle neck somewhere in the CPU emulation. Hope to help.

No difference using x86 or x64. This issue is present also in version r6553 (before FIFO rewrite).

Issue 3775 has been merged into this issue.

Yes it is. Less evident due to general performance improvement,but the sudden drop in FPS still

I tested this pretty thoroughly, and it appears to be something to do with the Wiimote rumbling. Alternate Wiimote timings doesn't help it, and playing on multiplayer causes it to happen on both players shots, and the slowdown ends at the same time as the rumbling.

When the AI hits the ball, it doesn't slowdown, only when a player, and only for as long as the Wiimote is rumbling.

Okay, I jumped the gun a bit on my previous conclusion, it's not rumbling, I turned off that in game option, and the frame rate is a LITTLE sporadic in multiplayer, although not as bad as single player. I'm going to guess it's a mixture of the splitscreen, calculating where to move the players, and in single player, the AI itself. But it's not abnormally slow, considering how the game runs. I don't see the issue.