MIT: Difference between revisions
No edit summary |
No edit summary |
||
| Line 30: | Line 30: | ||
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/mmodular.cpp mmodular] == | == [http://github.com/mamedev/mame/blob/master/src/mame/drivers/mmodular.cpp mmodular] == | ||
I/S= diag speed test doesn't match real hardware. | 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] == | == [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. | 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. | ||
Revision as of 13:08, 18 November 2019
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_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
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?
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.
