The NEW Build Your Own Arcade Controls
Software Support => GroovyMAME => Topic started by: Cowslanlr on July 17, 2019, 04:50:38 pm
-
I am having issues getting GroovyMAME to use my 2560x240 super resolution for games with a native resolution of 320x240. This became an issue after I added "320 x 240 @ 60.000000 desktop" to user_modes - super.ini. I added this as a desktop mode so that I could play other PC games in 240p. The problem is, now that I have done this switchres wants to select 320x240 rather than my super resolution.
How can I get GroovyMAME to use my super resolution again without removing the 240p desktop mode?
Any help would be greatly appreciated, I have been struggling with this for a while.
-
In mame.ini, change " resolution auto" to "resolution 2560x0" This will force groovymame to use the appropriate super resolution for whatever game you're playing. It works for me at least!
-
In mame.ini, change " resolution auto" to "resolution 2560x0" This will force groovymame to use the appropriate super resolution for whatever game you're playing. It works for me at least!
Thank you so much, that worked like a charm! I feel so dumb for not trying that sooner. I knew there must have been something really obvious that I was missing. :P
-
Are you using an old version of GroovyMAME?
-
Are you using an old version of GroovyMAME?
No, I am using the newest version of GroovyMAME 0.211, why do you ask?
-
I seem to recall that we used to have to set "resolution 2560x0" or something similar in the mame.ini in older versions but I thought that was no longer a requirement.
-
I seem to recall that we used to have to set "resolution 2560x0" or something similar in the mame.ini in older versions but I thought that was no longer a requirement.
I think for most people it probably isn't necessary, but in my situation it was required because I added the 320x240 desktop resolution to user_modes - super.ini.
-
I seem to recall that we used to have to set "resolution 2560x0" or something similar in the mame.ini in older versions but I thought that was no longer a requirement.
I believe the setting "cleanstretch 2" was the thing that is no longer needed/used