Build Your Own Arcade Controls Forum
Software Support => GroovyMAME => Topic started by: big10p on March 17, 2015, 10:07:56 am
-
Hi
Sorry, this is my second question of the day, but I'm a bit of a noob when it comes to using groovyMAME with an arcade monitor.
I have installed CRT emudriver and had everything working OK with groovyMAME 153, but wanted to try out the super resolutions. So, I downloaded the latest groovyMAME (159) and followed the following instructions:
# Instructions to enable "super resolutions"
# ------------------------------------------
# - Delete or rename the original "ReslList.txt" file
# - Rename this file as "ReslList.txt"
# - Set up VMMaker, in vmmaker.ini edit:
# ListFromXML = 0
# GenerateXML = 0
# ModeTableMethod_Custom = 0
# - Run VMMaker (run as admin in Windows 7!), restart.
# - Then set up GroovyMAME, edit mame.ini with these settings:
# resolution 2560x0
# cleanstretch 2
Now, when I run groovyMAME, a dialog says Switchres is unable to find a mode that meets my specs. I did a search and apparently this means I've done something pretty basic, wrong, but I can't figure out what.
When I ran VMMaker, it only found 31 modes and generated 16. Also, arcadeOSD doesn't list any custom modes.
I have my VMMaker.ini and mame.ini here if someone would be kind enough to take a look:
https://www.dropbox.com/s/wf2pl7612twokof/gm_error.zip?dl=0 (https://www.dropbox.com/s/wf2pl7612twokof/gm_error.zip?dl=0)
Thanks!
-
It's probably a monitor detection issue, check this: http://forum.arcadecontrols.com/index.php/topic,143136.msg1484489.html#msg1484489 (http://forum.arcadecontrols.com/index.php/topic,143136.msg1484489.html#msg1484489)
-
Indeed, that was the problem. I might have a go at making that VGA cable, sometime. Thanks. :)
Erm, another slight problem here :-[ Like someone else in the thread you linked to, some vertical games (on my horizontal monitor) are running at 97%. I changed the 'monitor' setting in mame.ini to 'arcade_15', and now Gyruss (for example) runs at 94%. I previously had it set to H9110 as I read this preset can be used for my MTC 9000 monitor, too?
I've attached the log file when running Gyruss. Thank you for your help! :applaud:
-
OK, I have re-run VMMaker ensuring there is a 1600 x 224 @ 60hz super resolution for Gyruss, Pac-Man etc. I have verified the mode works in ArcadeOSD but groovyMAME is still not picking this mode. I've deleted all mame game-specific config files and tried 'monitor arcade_15' and 'monitor h9110' in mame.ini, but still no luck.
Anyone got any ideas what's wrong, here, please?
[edit] Forget the above - seems I need a 1600x288@60 mode to run the mentioned games. I have one specified in reslList.txt but VMMaker only seems able to create that res @ 53Hz. Seems odd as I have my desktop res set to 384x288, and that works at 60Hz.
-
Are you sure your desktop is 60hz? Windows is probably lying.
-
It's a genuine bug. I'm uploading fixed binaries in a minute :-[
EDIT: Ok I've uploaded new diff and Windows binaries. Please check again.
-
[edit] Forget the above - seems I need a 1600x288@60 mode to run the mentioned games. I have one specified in reslList.txt but VMMaker only seems able to create that res @ 53Hz. Seems odd as I have my desktop res set to 384x288, and that works at 60Hz.
Obviously 288p is not 60 Hz. VMMaker does it right. It's simple maths.
Anyway there was a bug that now should be fixed. Now you should be able to run gyruss at 60 Hz when using the H9110 preset. You need a 16.7 kHz capable monitor to do that. Above 256p you can't achieve 60 Hz, you'd need 17-18 kHz and no standard arcade monitor can do that.
You can enable the -multithreading option if you want those games to reach 100% (scroll won't be smooth).
-
Maths never was my strong point. I just thought I'd seen it running at that res, before trying super resolutions.
Where do I download the new version? I re-downloaded VMMaker etc. but all the files in the zips have older dates. Thanks.
-
New version of GroovyMAME (https://drive.google.com/drive/#folders/0B0NB2HYUHHktSUJiRDRKWWFCV1k/0B5iMjDor3P__aEFpcVNkVW5jbEE/0B5iMjDor3P__fjNkU2MwMUNaSEY4V2NGLWQwN2dYVHh2Zy03am5GSTlsVGJMWkNIbWZMQXM), not VMMaker.
-
That's done the trick. Thank you for this, and all your hard work, Calamity. Much appreciated!