|Viewing Issue Advanced Details||midtunit.cpp|
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06509||Documentation||Trivial||Always||Feb 21, 2017, 16:13||31 days ago|
|Tester||StHiryu||View Status||Public||Platform||MAME (Unofficial Binary)|
|Assigned To||Resolution||Duplicate||OS||Windows Vista/7/8 (64-bit)|
|Version||0.182||Fixed in Version||Build||64-bit|
|Summary||06509: mk: Mismatch between game and machine information resolution|
Take a look at the machine informationt for MK, and you can see:
Mortal Kombat (rev 5.0 T-Unit 03/19/93) (Midway 1992)
TMS34010 50.000000 MHz
M6809E 8.000000 MHz
Williams ADPCM Sound Board
YM2151 3.579545 MHz
OKI6295 1.000000 MHz
400 x 254 (H) 54.706840 Hz
However, I've recorded a mk video with Virtualdub and in the file info shows 400x252. It's strange because all the others games I've recorded show the correct resolution.
|Steps To Reproduce||
Record a game with "Play and record uncompressed AVI output" option.
On windows, click on avi file, Properties, Details tab, and you'll see the resolutions.
|Affected Sets / Systems||mk|
Feb 22, 2017, 03:49
|MK3 also produces the same result as MK. Seems like some kind of overscan differential rather than a bug.|
Feb 22, 2017, 03:55
|Tempted to close this one out as well based on 05650 - I'll leave it for now to see what responses it gets if any.|
31 days ago
|So the real resolution should be 400x252?|
31 days ago
it's just the usual case of a chip with programmable resolution.
MAME doesn't know the resolution of the game until the game code configures the video chip which obviously requires the emulation to have already been started. The values you see on startup are just default placeholder values or whatever the default mode of the chip is.
You have to force a size with -snapsize when recording them.
it's not a bug.