Viewing Issue Advanced Details
[ Jump to Notes ]
midway/midtunit.cpp
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
05650 Graphics Minor Always Jul 31, 2014, 02:11 Aug 2, 2014, 00:39
Tester ScHlAuChi View Status Public Platform MAME (Unofficial Binary)
Assigned To Resolution Duplicate OS Windows Vista/7/8 (64-bit)
Status [?] Closed Driver
midway/midtunit.cpp
Version 0.150 Fixed in Version Build Normal
Fixed in Git Commit Github Pull Request #
Summary 05650: Mortal Kombat 1,2,3 all versions!: Wrong resolution of 399x253 for all Mortal Kombat games instead of the correct 400x254!
Description Machine resolution is 400x254
http://www.mksecrets.net/mk1/eng/mk-arcade.php

While this isnt a big a problem, it becomes one when you use the -aviwrite function - as this will result in a broken 399x253 file!

Simply fixing the incorrect resolution will solve this problem!
Steps To Reproduce Start Mortal Kombat 1, 2 or 3
Resolution will be 399x253
Record an AVI
AVI will be broken!
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems Mortal Kombat 1,2,3 all versions!
Attached Files
  
Relationships
duplicate of 05539Closed all (?) sets in qix.c: Inconsistant refresh rate in games between various sources/mame 
has duplicate 06509Closed  mk: Mismatch between game and machine information resolution 
Notes
8
User avatar
No.10879
haynor666
Tester
Jul 31, 2014, 06:42
 Probably avi write requires resolutions with parity.

BTW. Violent Storm is currently working at 385x224. Probably video will be also broken.
User avatar
No.10881
kamilz
Tester
Jul 31, 2014, 16:55
 Dudes don't get me wrong, of course every report here counts.

I just wanna say something about resolution issue:
My experiences tells me, this is one of the area where Mame is highly accurate, even sometimes official reports are not precisely accurate but Mame is.

Just a guess, I think 399x253 probably the correct one. Even though looks both x and y res. seems off by one.
User avatar
No.10884
Haze
Senior Tester
Jul 31, 2014, 17:54
 I thought the TMS controlled the resolution directly, if it programs in 399 then 399 is correct..
User avatar
No.10885
zaxxon
Tester
Jul 31, 2014, 19:33
edited on: Jul 31, 2014, 19:35
 for the record there are quite a few games (listed below) which initially report having a resolution of 399x253, but when the game is run in mame the actual drawn resolution is something else (ie. if you take a .png snapshot the actual resolution is as below:)

400x254:
openice
jdreddp
mk
mk2
mk3
ngahangt
nbajam
nbajamte
rmpgwt
revx
umk3
wwfmania

396x256:
hiimpact
shimpact
trog

410x256:
smashtv

400x255:
strkforc

404x255:
term2

400x256:
totcarn

and narc is a similar example:
it is reported as 511x399, but runs at 512x400

i dont know if there are others.
User avatar
No.10889
NekoEd
Senior Tester
Jul 31, 2014, 23:08
 I'm sure there are some sets like these where documentation doesn't match reality, or MAME reports the initial resolution which then changes via code. Marking for further direction.
User avatar
No.10890
Haze
Senior Tester
Aug 1, 2014, 00:06
 ok, in that case (for mk2/3 etc.) the initial resolution in the driver is probably non-optimal, but it's just another case of dynamic resolutions, the TMS can configure the display to whatever it wants, so the actual resolution specified in the driver is never going to be 100% accurate anyway.
User avatar
No.10891
haynor666
Tester
Aug 1, 2014, 21:04
 BarnacleEd, there was similiar problem in bug 5539. I think it was explained already.
User avatar
No.10892
NekoEd
Senior Tester
Aug 2, 2014, 00:39
edited on: Aug 2, 2014, 00:40
 You're right, haynor666. Closing as duplicate of closed bug 05539.