---
Goldart (Spain) [Morten Kirkegaard, Ryan Holtz, Clawgrip, David Haywood, Roberto Fresca, Peter Wilhelmsen]
video hardware is bitmap based, but seems to have some control registers so palette etc. is set outside of the actual writes, might also disagree with how the ds5002fp core does memory addressing slightly as some bits seem to be fetched from the wrong places. ds5002fp dump we have is good enough to run the attract mode on PCB, only 2 suspicious bytes.
The Indy/Indigo² issue appears to be related wait states or other unemulated delays on the driver side, and not a problem with this device or at_keybc.
* New WORKING machines
---------------------------------------------------------
Pink Jelly [ClawGrip]
VT03 Sound Test [ClawGrip]
New NOT_WORKING machines
---------------------------------------------------------
Pinball [ClawGrip]
Boxing [ClawGrip]
(nw) All those programs came from the official VT SDK from V.R. Technology. I'm not sure about the flags, as being demo programs I'm not sure what they should really do or look like. At least "Pink Jelly" looks better on the emulator bundled with the VRT VT SDK than on MAME.
* Add 'pinkjelly', 'vtpinball', 'vtboxing' and 'vtsndtest' (nw)
* Change game names (nw)
* note updates (nw)
* no (nw)
* refactors (nw)
* more refactor (nw)
* fix log (nw)
* bit use note (nw)
* note about use (nw)
* register use notes (nw)
* notes, possible timer irq (nw)
* Revert "Used set_folder to avoid hardcoding plugin name in settings path"
This reverts commit 76884986fd8630f81cfc838aa42f264fdcec2ea9.
* Changed autofire config directory to homepath
* Bumped autofire plugin version
There are some bugs, probably linked to the sample counter (I thought
it was a frame counter for a start...). But at least the code is not
aneurysm-provoking anymore.
One thing to do would be to turn the k573dio into a
device_mixer_interface to have the connection to the speakers done at
the driver device level. Volunteers?
