> You don't need to measure it. On an arcade board the CPU can sit in a loop monitoring
> your button presses. When you run that in MAME the inputs are only updated every
> frame.
Well I thought more in the line of measuring if the lag was perceived/perceivable by gamers.
>
> On seeing you press that button it could change a palette register which will be
> output instantly. In MAME it's not only had to wait up to a frame to get the input
> but the frame can only be output once it's fully generated. Which can add up to
> another frame.
>
> This is before you get into vsync/triple buffer/display driver issues which can add
> more latencies.
Call me naive, but I would have thought that MAM emulation granularity would be (at least partly) in sub-frame slices.
Given your example, what happens to multiple input events in MAME within a single frame, say joystick right, then left? Is only the latest one processed?
|
Index 
Flat 
Re: MAME latencies?
Reply
