Emulator

Yeah uh, don't enable it then.

What's your framelimit settings? Try different values, i.e. auto-limit by VPS, auto-limit by FPS and limit by audio.

... btw are you sure the game runs half speed with accurate vbeam? I.e. sure that it's not just the game running at twice speed without accurate vbeam? :p

Yes I'm sure; Tested It against the Wii itself. Will test different limit
settings hand report back.
Op 30 dec. 2012 14:14 schreef dolphin-emu@googlecode.com het volgende:

Ticking "Limit by FPS" makes he game run at "normal" speed, with 50FPS,
100VPS and emulator reporting speed at 200%. Limiting by any other means
results in 100% speed, but actually running at half-speed.

That said, when enabling the VBeam option the game just runs half speed,
regardless of any limiting settings. Perhaps because the game has a
1FPS/2VPS ratio?
Op 30 dec. 2012 14:28 schreef "Arthur van Dijk" avandijk1982@gmail.com
het volgende:

Where is the random text coming from in your comments?

Dunno, it happens when I reply with GMail

I didn't know you could.. haha

Maybe if I disable "quoted text"...

Anyways, this issue might be specifically for this game. I strongly suspect
it has its own code for handling framerate, as I noticed it skipping frames
on the wii itself in large areas where Dolphin just reduces FPS because my
CPU can't go any faster. That is, when using the dual-core option. Without
it, the VPS remains high (~50) and the FPS drops down to 2-5.

This just might be "one of those games". The game is perfectly playable
though (provided the correct settings are used), but I noticed some users
on the forum talking about accurate VBeam giving a speed up, so I couldn't
resist to try it out.

Either way, the settings for the game to run perfectly are:

EFB to RAM (with or without cache) fixes photo-making with the camera
in-game
DSP-LLE fixes reverb sound effects like the echoing in the mines.

It's not just this game, it happens for a lot of them.

This option is a hack itself, helps some games, causes trouble for even more, this issue is invalid

Accurate VBeam emulation is not a hack. I don't see where you're getting that idea from, anyway :|

Accurate, maybe not, but not accurate is defenetly

I've noticed weird behavior like this when I had vbeam and progressive scan on together

VBeam shouldn't change anything at all when progressive scan is enabled. That's a Dolphin bug.

I talked to skid about the DSP DMA callback @ http://code.google.com/p/dolphin-emu/source/browse/Source/Core/Core/Src/HW/SystemTimers.cpp#163 , and it pretty much should be dropped anyway (i.e. that line should read "int fields = 1"). Unfortunately I have no idea what kind of regressions it might cause on the non-AX side of things, but that'd be worth a try for anyone who wants to look at this issue.

To be more clear here, it sounds like HM:AP is using progressive scan by default and is limiting its framerate by the speed of DSP DMA stuff (I don#t specifically what the hack is about). By doubling the magic value via the hack, HM:AP's framerate gets halved.

Might, anyway. I didn't actually debug anything here :p

Ok, I was just proven wrong on IRC, so nevermind :p

We're not taking bug reports on the VBeam option. It's an option because it does not work with every game yet.