this logic (hack?) added in 2010 breaks tempest service mode (boot with service switch turned on, or press fire+zap when prompted in the menu you get when you hit f2 during gameplay)

the original change was this
"Mathis Rosenhauer fixed mametesters bug 03634. Reduced flickering in Tempest/Quantum. "
the diff for that (thanks Tafoid)
http://pastebin.com/NXs4UvzW

the bug report it was used to fix is
http://mametesters.org/view.php?id=3634

I've not backed it out for Quantum, only Tempest, I guess it needs proper review tho.  Maybe the flickering actually happened on real hardware sometimes, or wasn't visible due to the nature of the vector generator?
This commit is contained in:
David Haywood 2015-08-03 01:26:47 +01:00
parent 3575a923a6
commit f341509a74
2 changed files with 3 additions and 3 deletions

View File

@ -670,6 +670,7 @@ int avg_tempest_device::handler_7() // tempest_strobe3
return cycles;
}
#if 0
void avg_tempest_device::vggo() // tempest_vggo
{
m_pc = 0;
@ -682,7 +683,7 @@ void avg_tempest_device::vggo() // tempest_vggo
*/
nvect = 0;
}
#endif
/*************************************
*
@ -912,7 +913,6 @@ void avg_quantum_device::vggo() // tempest_vggo
nvect = 0;
}
int avg_quantum_device::handler_0() // quantum_st2st3
{
/* Quantum doesn't decode latch0 or latch2 but ST2 and ST3 are fed

View File

@ -189,7 +189,7 @@ public:
virtual int handler_6();
virtual int handler_7();
virtual void vggo();
//virtual void vggo();
};
// device type definition