Build Your Own Arcade Controls Forum
Software Support => GroovyMAME => Topic started by: mikecrj on February 10, 2013, 04:24:30 pm
-
I'm having trouble with Mortal Kombat in GroovyMAME 0.147u3v014. In GroovyMAME, it's reporting an average speed of 114% while my LCD's OSD indicates a refresh rate of 62.1Hz. In comparison, when running GroovyMAME 0.146v013f, I get an average speed of 100% at 54.8Hz. This problem is not isolated to Mortal Kombat. It also happens in tapper, argus, twincobr, loht, rtype2, tdragon2, mpatrol, snowbros, donapachi, etc. The scrolling is fine, but the games are running too fast.
I'm running a clean install of Windows XP (32-bit), with a Sapphire Radeon HD7750 (AMD Catalyst 12.6 display driver), and a Gateway FPD2185W LCD (1680x1050) monitor. I'm guessing the issue is related to PowerStrip. I tried upgrading to AMD Catalyst 13.1, but that did not make a difference. Below is the mame.ini and Mortal Kombat log files for both versions of GroovyMAME. Perhaps something is not configured correctly in my mame.ini.
Thank you for any help or suggestions. I've really enjoyed GroovyMAME and have had no issues with v013. Hopefully I can get v014 running smoothly.
GroovyMAME 0.147u3v014 Mortal Kombat log. Ran with command line -norotate -norol -noror -notriplebuffer -syncrefresh -waitvsync -nohwstretch -nofilter -nocleanstretch -keepaspect -prescale 1:
http://pastebin.com/sEL38dgQ (http://pastebin.com/sEL38dgQ)
GroovyMAME 0.146v013f Mortal Kombat log:
http://pastebin.com/rKPCirV7 (http://pastebin.com/rKPCirV7)
GroovyMAME 0.147u3v014 mame.ini:
http://pastebin.com/ssECjbM8 (http://pastebin.com/ssECjbM8)
GroovyMAME 0.146v013f mame.ini:
http://pastebin.com/5D2Qmr4s (http://pastebin.com/5D2Qmr4s)
-
Hi mikecrj,
Well this is interesting, thanks for posting. The problem is your video card's dotclock is fixed at 146366. My old method worked around this problem by adding lines to the back porch. The new method is based on VESA timings and the idea was to avoid the user having to enter "difficult" porch specs, but it requires a flexible enough card with all the required dotclock values available. However, I will try to integrate both methods somehow, please stay tuned, I will need you to test it.
-
Thank you, Calamity. I will be available for testing.