(Created page with "__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 ef...")
 
(fidel_eag68k)
 
(13 intermediate revisions by the same user not shown)
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/alpha68k.cpp alpha68k] ==
 +
''' goldmedl, goldmedla, goldmedlb ''' - Dash events timers relies on MCU irq timings, which can't be accurate til the MCU is decapped and emulated.
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/alpha68k_n.cpp alpha68k_n] ==
 +
''' sstingry ''' - Super Stingray MCU irq controls timer speed. The MCU has been hooked up but the clock is almost certainly wrong.
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/aristmk5.cpp aristmk5] ==
 +
Games are running at double speed.
 +
 +
== [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/fidel_as12.cpp fidel_as12] ==
 +
Seems 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?
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/fidel_eag68k.cpp fidel_eag68k] ==
 +
''' feagv10 ''' - V10 CPU emulation is too slow, MAME 68040 opcode timing is same as 68030 but in reality it is much faster, same goes for V11 of course (see below).
 +
 +
''' feagv11 ''' - V11 CPU should be M68EC060, not yet emulated. Now using M68EC040 in its place  at twice the frequency due to lack of superscalar.
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/fidel_elite.cpp fidel_elite] ==
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/fidel_sc12.cpp fidel_sc12] ==
 +
Seems 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?
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/konamigs.cpp konamigs] ==
 +
''' ddrkids ''' - Songs desync.
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/konamim2.cpp konamim2] ==
 +
Games are running slower than they should.
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/mephisto_mm2.cpp mephisto_mm2] ==
 +
''' mm4tk, mm5p ''' - They need proper emulation of the TurboKit (it's not as simple as a CPU overclock plus ROM patch).
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/mmodular.cpp mmodular] ==
 +
I/S= diag speed test doesn't match real hardware.
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/psikyo.cpp psikyo] ==
 +
Excessive input lag.
 +
 +
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/taitojc.cpp 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.

Latest revision as of 05:42, 14 May 2020

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.

alpha68k

goldmedl, goldmedla, goldmedlb - Dash events timers relies on MCU irq timings, which can't be accurate til the MCU is decapped and emulated.

alpha68k_n

sstingry - Super Stingray MCU irq controls timer speed. The MCU has been hooked up but the clock is almost certainly wrong.

aristmk5

Games are running at double speed.

cv1k

Games are running faster than on real hardware.

fidel_as12

Seems 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?

fidel_eag68k

feagv10 - V10 CPU emulation is too slow, MAME 68040 opcode timing is same as 68030 but in reality it is much faster, same goes for V11 of course (see below).

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

fidel_elite

fidel_sc12

Seems 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?

konamigs

ddrkids - Songs desync.

konamim2

Games are running slower than they should.

mephisto_mm2

mm4tk, mm5p - They need proper emulation of the TurboKit (it's not as simple as a CPU overclock plus ROM patch).

mmodular

I/S= diag speed test doesn't match real hardware.

psikyo

Excessive input lag.

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.