|Viewing Issue Advanced Details||msx.cpp|
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06608||Graphics||Minor||Always||Jun 6, 2017, 14:59||Jun 16, 2017, 02:10|
|Tester||daneman||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||Resolution||Open||OS||Windows 10 (64-bit)|
|Version||0.185||Fixed in Version||Build||64-bit|
|Summary||06608: nms8255, nms8250, expert20: MSX2/2+ Screen issue|
MSX 2/2+ screen is not covering entire display as it can. The upper and lower borders of the screen are wrong and consuming too much display area. I'm comparing with other emulators which can fully emulate MSX2/MSX2+ screen accordingly. Sretching options on Mame only stretchs left and right borders.
Tried with MSX 2 nms8250, nms8255 and expert20.
If you compare MSX 1 emulation (any system) on MAME you can see a proper use of display and borders.
Attached zip file with MSX1 print running on mame accordingly and MSX2 print with excessive border usage, for comparison.
|Steps To Reproduce||Run MSX2/MSX2+ emulation|
|Affected Sets / Systems||nms8255, nms8250, expert20|
| msx_screens.zip (3,794 bytes) Jun 6, 2017, 14:59 by daneman|
msx 1 and 2 screens
Jun 8, 2017, 12:41
since MESS is no more, is there any point in having the 'mess_specific' flag here?
I notice MASH keeps bumping posts to set it, when really these days it's all just MAME and doesn't need setting.
Jun 8, 2017, 14:33
I'm keeping it until it is no longer a valid SUBTARGET=mess. The system is set up for it and there are still users of it separately, as well. Yes, eventually all bugs will need to be changed to MAME but you have to remember that there are Devs who are not interested in arcade hardware and other Dev not at all interested in what MESS brought to the table. The bumping is an unfortunate side effect of making any change to a bug, but as a moderator/admin this can be done without bumping which I do to a LOT of bugs.
MESS stays for now.
Jun 8, 2017, 14:44
I'm confirming this based on a video here:
Where Vampire Hunter appears to hit near top/bottom of the screen on real hardware
The emulation, using example from softlist, has sizable empty areas on top and bottom: mame nms8250 vampkill
Jun 16, 2017, 02:10
edited on: Jun 16, 2017, 09:26
If you see 05623 seems like this bug was saw and fixed on MESS 0.166.