Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07504 Graphics Trivial Always Nov 27, 2019, 10:27 Dec 31, 2019, 02:22
Tester Robbbert View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Reopened OS Windows Vista/7/8 (64-bit)
Status [?] Confirmed Driver
Version 0.216 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 07504: pong, pongf: score on right-hand side is mis-shapen
Description The right-hand digit has extraneous lines and blobs. Some other playfield parts show imperfections as well.

Compare with real machine:
or


It's possible it's simply a split-second timing issue, but I'll leave that determination to the experts.
Steps To Reproduce >mame64 pong

>mame64 pongf

Start a game and watch the score.
Additional Information See attached F12 snaps. For some reason they are very much stretched out.
You need to click on each one to see the issues.
Github Commit
Flags
Regression Version 0.216
Affected Sets / Systems pong, pongf
Attached Files
png file icon 0001.png (2,616 bytes) Nov 27, 2019, 10:27 Uploaded by Robbbert
Robbbert
png file icon 0002.png (2,606 bytes) Nov 27, 2019, 10:27 Uploaded by Robbbert
Robbbert
png file icon 0003.png (2,612 bytes) Nov 27, 2019, 10:28 Uploaded by Robbbert
Robbbert
png file icon 0004.png (2,662 bytes) Nov 27, 2019, 10:28 Uploaded by Robbbert
Robbbert
png file icon 0005.png (2,765 bytes) Nov 27, 2019, 10:29 Uploaded by Robbbert
Robbbert
Relationships
There are no relationship linked to this issue.
Notes
2
User avatar
No.17307
couriersud
Developer
Dec 29, 2019, 13:28
This has been discussed over and over in the past. This is a result of the screen representation of X horizontal pixels in MAME. The real pong monitor was a B&W monitor and had no aperture mask.
If the OP would use a high speed AD sampler to sample the video output at sub-pixel accuracy (around 30 MHz) he would observe the same artifacts.
You may increase hsl defocus values to 1.0 for a more realistic display

I am too lazy to dig out all the references. Here is one:

https://mametesters.org/view.php?id=6085

This is not a driver bug. It should either be closed or attributed to the mame display subsystem
User avatar
No.17309
couriersud
Developer
Dec 31, 2019, 02:22
I am changing the status to confirmed. Leaving comments tired late at night is not the best idea.
The topics highlighted in this report are valid. I have addressed them with changes to the fixedfreq monitor code. The code supports vector output now (switch in machine configuration).
With a rendering chain supporting sub-pixel rendering this should work now. But I am currently not aware of any renderer with adequate sub-pixel rendering.