MIT: Difference between revisions
No edit summary |
|||
| Line 12: | Line 12: | ||
== [http://github.com/mamedev/mame/blob/master/src/mame/drivers/fidel_eag68k.cpp fidel_eag68k] == | == [http://github.com/mamedev/mame/blob/master/src/mame/drivers/fidel_eag68k.cpp 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. | ''' feagv11 ''' - V11 CPU should be M68EC060, not yet emulated. Now using M68EC040 in its place at twice the frequency due to lack of superscalar. | ||
Revision as of 07:12, 19 March 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.
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.
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.
