Build Your Own Arcade Controls Forum
Main => Main Forum => Topic started by: Pakled on January 22, 2013, 07:41:36 pm
-
Does anyone no which command line tags get rid of the virtual bezels in MAME and bring the game to full screen? I'm running in 640x480 mode on a Billabs 25 inch CRT at a 4:3 ratio with the Maximus Arcade frontend.
Any help will be appreciated,
Pakled
-
If you haven't already, from the command prompt, type mame -createconfig.
This will create the mame.ini file in your mame folder.
Click on that to open in word. Look for where it says bezels, it will have a 1. Just change that to a 0 and save and close
-
Once I do that how do I get Maximus Arcade to load the .ini file?
-
Once I do that how do I get Maximus Arcade to load the .ini file?
You don't. The .ini file controls what MAME displays and how it is displayed.
If you aren't getting the desired results, either you haven't changed the correct option in the mame.ini file or
there is a .ini file for that particular game in the ini folder (in your MAME folder) that is over-riding mame.ini
Maximus Arcade is irrelevant.
MAME is launched by Maximus Arcade the same way it's always been.
-
I've changed the bezel line to 0 in the ini file. Ive also checked the folder and found no other ini files yet all my games, even ones I haven't tried before, still spear small on my monitor and in a virtual bezel. Any other ideas?
Thanks,
Pakled
-
Just to make sure, are the options for artwork and backdrops also set to 0 in the mame ini. And are you sure you don't have any separate game INIs in the ini folder?
I'm not familiar with the front end, is there possibly a setting in there that puts artwork on?
-
Did you make sure to save the ini file once you edited it?
Sent from my Galaxy Nexus
-
Running mame under linux, you can also turn off bezels by passing the option -nouse_bezels. You might also want to disable backdrops and overlays with -nouse_backdrops and -nouse_overlays.
The method of setting the ini file should work too, but my guess is that the front end is running mame from some other directory than where you created the .ini file, and it isn't finding the ini file that you created.