Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
This page is designed to allow for a quick look over all the drivers with a MACHINE_IMPERFECT_TIMING flag by giving, as much as possible, an idea on the amount of effort needed to fix them.
 
This page is designed to allow for a quick look over all the drivers with a MACHINE_IMPERFECT_TIMING flag by giving, as much as possible, an idea on the amount of effort needed to fix them.
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/cv1k.cpp cv1k] ==
 +
Games are running faster than on real hardware.
  
 
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/fidel6502.cpp fidel6502] ==
 
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/fidel6502.cpp fidel6502] ==

Revision as of 06:34, 27 October 2017

This page is designed to allow for a quick look over all the drivers with a MACHINE_IMPERFECT_TIMING flag by giving, as much as possible, an idea on the amount of effort needed to fix them.

cv1k

Games are running faster than on real hardware.

fidel6502

fscc12 and clone - They seem a little bit slower than the real machine. Currently, a dummy timer workaround is needed, or it's much worse. Is the problem here is due to timing of CPU addressbus changes?

fidel68k

feagv10 - V9(68030 @ 32MHz) is faster than V10(68040 @ 25MHz) but it should be the other way around, culprit is unemulated cache?

feagv11 - V11 CPU should be M68EC060, not yet emulated. Now using M68EC040 in its place at twice the frequency due to lack of superscalar.

taitojc

Games are running at wrong speed(unthrottled?) compared to pcb recordings, easily noticeable on sidebs/sidebs2, for example the selection screens are too fast, and the driving is almost twice as slow.