MIT: Difference between revisions
No edit summary |
No edit summary |
||
| Line 35: | Line 35: | ||
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/mephisto_mm2.cpp mephisto_mm2] == | == [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). | ''' 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/psikyo.cpp psikyo] == | == [http://github.com/mamedev/mame/blob/master/src/mame/drivers/psikyo.cpp psikyo] == | ||
Excessive input lag. | Excessive input lag. | ||
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/saitek_risc2500.cpp saitek_risc2500] == | |||
More accurate dynamic cpu clock divider is needed. | |||
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/spg2xx_shredmjr.cpp spg2xx_shredmjr] == | == [http://github.com/mamedev/mame/blob/master/src/mame/drivers/spg2xx_shredmjr.cpp spg2xx_shredmjr] == | ||
| Line 47: | Line 47: | ||
== [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. | ||
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/tasc.cpp tasc] == | |||
More accurate dynamic cpu clock divider is needed. | |||
Revision as of 06:34, 10 May 2021
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).
psikyo
Excessive input lag.
saitek_risc2500
More accurate dynamic cpu clock divider is needed.
spg2xx_shredmjr
Bad music timings (too slow).
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.
tasc
More accurate dynamic cpu clock divider is needed.
