Closed GoogleCodeExporter closed 8 years ago
The options in the default Pi mame.cfg are the only ones supported, you can't
add additional ones from the official MAME program as it's not coded that way,
it's specific to the Raspberry Pi.
To remove antialiasing means rewriting the graphics backend as it currently
uses the low level graphics hardware API for performance. I may try and have a
look at this in future but any sort of software scaling is going to affect the
performance on the Pi badly as it's very CPU limited, unlike a PC.
Original comment by squid...@gmail.com
on 15 May 2013 at 2:48
I had not hoped for software scaling except for maybe scan doubling, but
rather for non-antialiased output. I would then want to chose the display
resolution so that it matches the game resolution and use the scaler inside
of the TFT display. But I don't know anything about how the low-level
graphics output works, so if you say that my naive wish cannot easily be
granted, please feel free to close the issue and please ignore my ignorance.
Thanks for your reply!
-Hans
Original comment by hans.hue...@gmail.com
on 15 May 2013 at 4:14
It's OK. I'll leave it open as I might be able to produce a solution sometime
in the future.
Original comment by squid...@gmail.com
on 15 May 2013 at 4:44
Would be great to have the non-antialised option and disable any kind of
postprocessing.
Original comment by luishern...@gmail.com
on 20 May 2013 at 8:41
[deleted comment]
There's currently no postprocessing going on, the GPU is simply scaling to the
size of the screen. Using "stretch_display=no" switches off any scaling. You
can then change the monitor/TV resolution using /usr/bin/tvservice. The Pi's
scaling quality is more than likely better quality than your Monitor's.
Original comment by squid...@gmail.com
on 22 May 2013 at 3:36
Implemented in the latest version. "display_smooth_stretch" option.
Original comment by squid...@gmail.com
on 8 Jun 2013 at 11:12
You are awesome, thank you so much. The games I'm interested in look
crystal clear now!
Original comment by hans.hue...@gmail.com
on 8 Jun 2013 at 8:01
Original issue reported on code.google.com by
hans.hue...@gmail.com
on 14 May 2013 at 10:10