06892: pico and clones: Colored borders are cropped

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
06892	Graphics	Minor	Always	Feb 27, 2018, 09:10	Apr 16, 2023, 15:07

Tester	ICEknight	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Open	OS
Status [?]	Acknowledged			Driver	sega/segapico.cpp
Version	0.194	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	06892: pico and clones: Colored borders are cropped
Description	MAME isn't rendering the full output of the Sega Pico and crops the borders that can be seen on real hardware.
Steps To Reproduce	A year at Pooh's Corner (poohcorn) will show a colored border right at the intro screen:
Additional Information	MAME already renders the full display output for systems such as the PC Engine or ZX Spectrum, so it would be consistent to not crop them for the Pico and other related systems (Mega Drive, etc).
Github Commit

Flags	Verified with Original
Regression Version
Affected Sets / Systems	pico and clones

Attached Files

No.14793 Haze Senior Tester Feb 28, 2018, 19:00	I guess it should be an option at least, the problem is most people consider the borders being present to be a bug, so we probably need to cater for both.
No.14826 ICEknight Tester Mar 11, 2018, 20:26 edited on: Apr 16, 2023, 20:42	It's been pointed out at MAMEWorld that VS Excitebike is missing a colored border at the bottom, so this may also extend to NES-based hardware as well: See also: https://mametesters.org/view.php?id=7054
No.14881 Heihachi_73 Tester Mar 28, 2018, 02:09	Mega Drive should at least have the border as a display option (e.g. via the artwork system) similar to the 304-wide Neo-Geo games, if it's there on the real thing e.g. when messing with the horizontal hold on a CRT TV it should at least be possible to show it in MAME. Same goes for NTSC NES games where the top 16 pixels aren't normally seen. The (unrelated) Excitebike border problem (the border around the Nintendo logo on the wall, not the screen itself) is most likely just a video timing bug, Super Mario 3 had similar problems with the HUD on older emulators which used exactly 60Hz instead of 59.94 or thereabouts.