Hallo Franz,


mal wieder ein dickes Dankeschön für deine unermüdliche Arbeit.
Und du hast noch ein Update nachgeschoben - mit neuen Änderungen?


Gruß Volker

Hallo Volker,
nur eine kleine Korrektur, und zwar lief der Mephisto Junior mit etwas zu niedriger Frequenz - hier die Details dazu:
https://www.schachcomputer.info/foru...97&postcount=9

Und im Plugin für Chess Champion Super System III/IV war der Code für die Taste '9' falsch, sodaß man keine Levels mit dieser Ziffer eingeben konnte - auch dieses neue Plugin ist jetzt im Update dabei.

Grüße,
Franz

Neuer romdump von Berger - Chesster Phantom (6126)
(it's Fidelity Phantom hardware, with the Chesster voice added)

Moin...

Was es nicht alles gab.
Hier in Aktion..



Gruß
Mark 1

Hi hap,

I have a problem with making a plugin for the Chesster Phantom:
when the Phantom makes a move, its move is displayed only a fraction of a second in the LCD (and sometimes even not at all), and then immediately switches to the clock display. In this short time it's impossible for the plugin to recognize the move.
The 'normal' (previous) Phantom doesn't have this problem, so could there something be wrong in the emulation of this new Chesster Phantom?

If not, then do you have any idea to detect Phantom's moves with any other method?
I've already made some trials (e.g. getting these moves directly from the sensorboard or phantom driver), but I've not found a reliable solution yet.

Regards,
Franz

Hi @hap,

I noticed one more thing with Chesster Phantom: When you increase the speed or disable throttling, after a while the shift key is enabled by itself and can't be disabled after that. After that, playing is of course no longer possible.

Greets
Dieter

The game not showing the move in the display (even though the manual says it does), it doesn't look like it's an emulation bug. You can see the same thing happening here:


It works fine when setting it to auto mode(computer plays against itself), also shown in the video linked by Mark 1.
I don't know where to obtain last move info, maybe somewhere in the RAM.

Plextor: did you have sound on? It's probably asking a question and waiting for your yes/no answer.

I actually had the sound turned off. If no action is taken after the start, Chesster will begin explaining and wait for a response (yes/no/repeat). If you start the game before this point, everything is ok.

Thank you for the hint.

Hi hap,

your last changes for the Phantom (animating the motor movements) are interesting - much better than the previous version.
They work in MAME 0.230 and 0.238, but when I tried to port them back to 0.220, I got a few error messages about the new layout files (compiling the driver is ok):

1) one type of errors was about the duplicate definitions of bounds for different states:
bounds state="0" ...
bounds state="240" ...
I've tried to solve this by putting it into 2 separate definitions for "disk"
"disk state="0"
"disk state="240"
and with this change the error messages disappeared.
I made similar changes within the "repeat" loop at the end, but I'm not sure if my changes with separate parts
element name="motorx~i~" ref="mpos~i~ state="4"
element name="motorx~i~" ref="mpos~i~ state="136"
are correct there within a "repeat" or if something like this is possible at all!?

2) the other error message was about the token "collection" - it seems that MAME 0.220 doesn't know this feature.
So I've just removed those 2 lines with "collection".

With these changes the compilation worked without any errors, but unfortunately this new red disk doesn't appear on the board, so the motor movements are not visible.

Thus my question: can the layout file be changed, so that this will also work with the older MAME 0.220 which I use in CB-Emu?

Regards,
Franz

The .lay functions I use for animation did not exist yet in MAME 0.220.

It used to be possible to animate on a single axis, if you copy-paste the same line over and over with the X parameter increasing. But a dot moving in X and Y directions, no, not possible in older MAME.