Another Bezel Question

[GoTheBunnies]

Running GameEx on a 3-sided cocktail, and have it set up so that Mame Auto-Rotates when it's a horizontal game. I'm using the GameEx bezel because some of the Mame ones are pretty 'noisy', but my question is can I remove Bezels completely and effectively spread the game out across the screen? Some of the horizontal games get pretty skinny-looking.

Thanks

[Adultery]

You can use the -noka switch to lose the aspect ratio.

[GoTheBunnies]

You can use the -noka switch to lose the aspect ratio.

Thanks - I just put it in the Mame command line?

[Adultery]

Yeah. I use it on my cabinet to fill up the whole screen.

It goes under advanced mame options.

[GoTheBunnies]

Yeah. I use it on my cabinet to fill up the whole screen.

It goes under advanced mame options.

Ok, finally got some time to try to set this up - it didn't work.

I don't use AdvanceMAME (actually I don't even know what it does), so the switch is set to False. I tried putting the -noka switch in the Mame Options line, but nothing changed.

What should I try next?

[fRequEnCy]

Ok, finally got some time to try to set this up - it didn't work.

I don't use AdvanceMAME (actually I don't even know what it does), so the switch is set to False. I tried putting the -noka switch in the Mame Options line, but nothing changed.

What should I try next?

Quote from Setup Wizard:

AdvanceMAME is an excellent MAME build that is designed to support Arcade Monitors and TV's.

So AdvanceMAME and Advanced MAME settings are different options. I think that confuses users IMO. As far as the switch that Adultery suggested, that's the one that tells MAME not to keep aspect ratio. If for some reason that isn't working for you then perhaps another setting is conflicting with it. Please post your MAME options line or mame.ini file if you use one so that we can see how your MAME settings are set.

[GoTheBunnies]

Quote from Setup Wizard:

So AdvanceMAME and Advanced MAME settings are different options. I think that confuses users IMO. As far as the switch that Adultery suggested, that's the one that tells MAME not to keep aspect ratio. If for some reason that isn't working for you then perhaps another setting is conflicting with it. Please post your MAME options line or mame.ini file if you use one so that we can see how your MAME settings are set.

Ok, my Mame options line says -nowindow -hwstretch -joy -skip_gameinfo

Mame ini file is

<UNADORNED0>

#

# CORE CONFIGURATION OPTIONS

#

readconfig 1

#

# CORE SEARCH PATH OPTIONS

#

rompath "c:\Emulators\Mame32\Mame_133\roms\"

samplepath samples

artpath artwork

ctrlrpath ctrlr

inipath .;ini

fontpath .

cheatpath cheat

crosshairpath crosshair

#

# CORE OUTPUT DIRECTORY OPTIONS

#

cfg_directory cfg

nvram_directory nvram

memcard_directory memcard

input_directory inp

state_directory sta

snapshot_directory snap

diff_directory diff

comment_directory comments

hiscore_directory hi

#

# CORE STATE/PLAYBACK OPTIONS

#

state

autosave 1

playback

record

mngwrite

aviwrite

wavwrite

snapname %g/%i

snapsize auto

snapview internal

burnin 0

#

# CORE PERFORMANCE OPTIONS

#

autoframeskip 0

frameskip 0

seconds_to_run 0

throttle 1

sleep 1

speed 1.0

refreshspeed 0

#

# CORE ROTATION OPTIONS

#

rotate 1

ror 0

rol 0

autoror 0

autorol 0

flipx 0

flipy 0

#

# CORE ARTWORK OPTIONS

#

artwork_crop 0

use_backdrops 1

use_overlays 1

use_bezels 1

#

# CORE SCREEN OPTIONS

#

brightness 1.0

contrast 1.0

gamma 1.0

pause_brightness 0.65

#

# CORE VECTOR OPTIONS

#

antialias 1

beam 1.0

flicker 0

#

# CORE SOUND OPTIONS

#

sound 1

samplerate 48000

samples 1

volume 0

#

# CORE INPUT OPTIONS

#

coin_lockout 1

ctrlr

mouse 0

joystick 1

lightgun 0

multikeyboard 0

multimouse 0

steadykey 0

offscreen_reload 0

joystick_map auto

joystick_deadzone 0.3

joystick_saturation 0.85

natural 0

uimodekey auto

#

# CORE INPUT AUTOMATIC ENABLE OPTIONS

#

paddle_device keyboard

adstick_device keyboard

pedal_device keyboard

dial_device keyboard

trackball_device keyboard

lightgun_device keyboard

positional_device keyboard

mouse_device mouse

#

# CORE DEBUGGING OPTIONS

#

log 0

verbose 0

update_in_pause 0

debug 0

debugscript

debug_internal 0

#

# CORE MISC OPTIONS

#

bios

cheat 0

skip_gameinfo 1

#

# CORE MKChamp OPTIONS

#

disable_hiscore_patch 0

disable_nagscreen_patch 0

disable_loading_patch 0

#

# WINDOWS DEBUGGING OPTIONS

#

oslog 0

watchdog 0

debugger_font "Lucida Console"

debugger_font_size 9

#

# WINDOWS PERFORMANCE OPTIONS

#

priority 0

multithreading 0

numprocessors auto

#

# WINDOWS VIDEO OPTIONS

#

video d3d

numscreens 1

window 0

maximize 1

keepaspect 0

prescale 1

effect none

waitvsync 1

syncrefresh 1

#

# DIRECTDRAW-SPECIFIC OPTIONS

#

hwstretch 1

#

# DIRECT3D-SPECIFIC OPTIONS

#

d3dversion 9

filter 1

#

# PER-WINDOW VIDEO OPTIONS

#

screen auto

aspect auto

resolution auto

view auto

screen0 auto

aspect0 auto

resolution0 auto

view0 auto

screen1 auto

aspect1 auto

resolution1 auto

view1 auto

screen2 auto

aspect2 auto

resolution2 auto

view2 auto

screen3 auto

aspect3 auto

resolution3 auto

view3 auto

#

# FULL SCREEN OPTIONS

#

triplebuffer 1

switchres 0

full_screen_brightness 1.0

full_screen_contrast 1.0

full_screen_gamma 1.0

#

# WINDOWS SOUND OPTIONS

#

audio_latency 2

#

# INPUT DEVICE OPTIONS

#

dual_lightgun 0

[fRequEnCy]

Well since you're using a mame.ini config file then there is no need to have those options as well in the command-line options since they are already being called. So you can get rid of those settings to clean things up a bit. However, that shouldn't cause conflict. Your settings appear to be fine and should work. The only thing I could think of is if you have 2 mame.ini files and they are conflicting. I've seen this happen while troubleshooting when using mame32/mameui. Not sure if your using that version. But according to your rom path I would think so. Check to see if you have another mame.ini file in your cfg directory (this is by memory so could be another directory) of your mame setup. Please report back!

[GoTheBunnies]

Well since you're using a mame.ini config file then there is no need to have those options as well in the command-line options since they are already being called. So you can get rid of those settings to clean things up a bit. However, that shouldn't cause conflict. Your settings appear to be fine and should work. The only thing I could think of is if you have 2 mame.ini files and they are conflicting. I've seen this happen while troubleshooting when using mame32/mameui. Not sure if your using that version. But according to your rom path I would think so. Check to see if you have another mame.ini file in your cfg directory (this is by memory so could be another directory) of your mame setup. Please report back!

Ahhh well that's good to know! What happens when there's a command in the GameEx commnad line that conflicts with the Mame config file - which one takes precedence?

No luck with a duplicate .ini file unfortunately, and yeah I am using Mame32/mameui. I played around a bit with the Mame settings, without success.

[fRequEnCy]

Ahhh well that's good to know! What happens when there's a command in the GameEx commnad line that conflicts with the Mame config file - which one takes precedence?

No luck with a duplicate .ini file unfortunately, and yeah I am using Mame32/mameui. I played around a bit with the Mame settings, without success.

Taken from the mame source docs:

263 Configuration options

264 ---------------------

265

266 -[no]readconfig / -[no]rc

267

268 Enables or disables the reading of the config files. When enabled

269 (which is the default), MAME reads the following config files in order:

270

271 - mame.ini

272 - <mymame>.ini (i.e. if MAME was renamed mame060.exe, MAME

273 parses mame060.ini here)

274 - debug.ini (if the debugger is enabled)

275 - vector.ini (for vector games only)

276 - <driver>.ini (based on the source filename of the driver)

277 - <parent>.ini (for clones only, may be called recursively)

278 - <gamename>.ini

279

280 The settings in the later ini's override those in the earlier ini's.

281 So, for example, if you wanted to disable overlay effects in the

282 vector games, you can create a vector.ini with the "effect none" line

283 in it, and it will override whatever effect value you have in your

284 mame.ini. The default is ON (-readconfig).

So if that's not the case then I don't have another clue as to why it's not working. We could try troubleshooting together if you want. Meet me in the chat room for real-time support.

[GoTheBunnies]

Taken from the mame source docs:

So if that's not the case then I don't have another clue as to why it's not working. We could try troubleshooting together if you want. Meet me in the chat room for real-time support.

Thanks for that, and might take you up on the troubleshooting offer at some stage. I've posted to problem in one of the Mame forums, so I'll see if I have any joy over there.

Cheers

[GoTheBunnies]

I found the solution to this problem - simply change the option labelled artwork_crop from 0 to 1 and no more bezels. Games go to fullscreen (and look a lot better albeit not authentic IMO).

Thanks