GameEx and Mame Res. INI's

[Blades]

Howdy,

Love GameEx. Well worth the reg. fee. And I've been enjoying it for a while. Recently I've upgraded my AVGA(arcade vga) card to the newer 3000 from the 9200agp version. New CPU/MOBO etc.. Also I upgraded to WIN 7. So I did a wipe, downloaded the latest version of GameEx. Ran the AVres tool and also tried the Mamewah resolution tool so it would set up the correct INI's for best resolution viewing on an Arcade monitor.

My question is, that Mame seems to have no problem picking the correct RES(for an Arcade monitor) for games like Moon patrol etc...

But when I try to play Mortal Kombat or Virtua Racing(those with a weird HZ setting 57 or 59). Instead of running at the INI's recoomended setting, instead it will default to a really skinny res(unusable). Now I've when I had it on my Windows XP machine with GameEX ver 10. I never had this problem. And have matched the old config to the "T" and I still have this problem.

Now I'm not blaming GameEx per say, I just don't know where to look and why it's not switching to the correct resolution. I've followed Ultimarc's directions to a T. And like I said, never had problems withe GameEx ver 10 going to the right resolutions. Especially in MK and such.

And the correct resolution for those games are in the INI's themselves. But for some reason, It will not change/force it into those specified resolutions. Instead it puts it into a resolution that is out of range. But it only effects games like MK or VR, ones that have a 59 or 57HZ refresh rate. But other games like Moon Patrol or 1943 work and switch to the proper resolution just fine.

Any suggestions as I must be missing somthing simple. Or maybe Win7 is to blame somewhat. I've tried multiple versions of Mame. Mame32,64 command line only etc.... Running out of idea's....

Thanks in advance...

;

[Brian Hoffman]

Gameex simply launches the game. Mame by defualt will READ the MAME.INI (if you have it) located in the directory where mame is at. In the MAME.INI you can adjust video settings etc.. If you do not have a MAME.INI in your mame directory; at a command prompt (in your mame directory) type "mame.exe -cc" without quotes.

Otherwise Gameex will run mame (any version) via command line. The command it uses can be adjusted in the mame configuration portion of gammex. Otherwise you can re-produce the exact command Gameex uses outside gameex via the RUN LAST GAME.BAT found in the Gameex programs group.

So, my immediate question is, what happens when you run MK outside Gameex?

[Blades]

Gameex simply launches the game. Mame by defualt will READ the MAME.INI (if you have it) located in the directory where mame is at. In the MAME.INI you can adjust video settings etc.. If you do not have a MAME.INI in your mame directory; at a command prompt (in your mame directory) type "mame.exe -cc" without quotes.

Otherwise Gameex will run mame (any version) via command line. The command it uses can be adjusted in the mame configuration portion of gammex. Otherwise you can re-produce the exact command Gameex uses outside gameex via the RUN LAST GAME.BAT found in the Gameex programs group.

So, my immediate question is, what happens when you run MK outside Gameex?

Ok, i've been able to mess around more.

If I launch it outside of GameEx, it states "Unable to initialize direct draw" and "Unable to setup windows creation". Then goes back to desktop. Now if I change the mame.ini to D3D mode, then it has no trouble launching at all. However, when I have it in DDRAW mode. It won't launch via commandline but it will launch within GameEx. Which really doesn't seem to make sense. And as I stated before, most games such as Moon patrol etc... will launch in there proper Res(for an AVGA card) as per setup via the MAme/ini files in the directory. But it will not use the proper resolution for MK(which the tool sets as 401x256, Virtua Racing which the tool sets as 512x448.

Now I had NO trouble running MK and such at there proper res via Windows XP. However, I wouldn't think that Win7 is the problem? I used the Ultimar Drivers that they gave me, even used the updated ones here: http://www.ultimarc.com/avgadrivers.html

I have GameEx set up exactly as my older WinXP config. I went from the ATI9200 to the ATI3000 AVGA and winxp to win7. (well and cpu/mobo) changes, but other than that, it's set up the same. Maybe Win7 is having a fit. I guess I can wipe and try XP. It's just a big pain in the ass....lol...

Also the other difference was the old setup had GameEx 10 and this has the latest 11.

Here is the INI File config...if this helps. Please keep in mind I have tried Mame and Mame64 with same results... Thanks for helping BTW!!

#

# CORE CONFIGURATION OPTIONS

#

readconfig 1

#

# CORE SEARCH PATH OPTIONS

#

rompath 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

#

# CORE STATE/PLAYBACK OPTIONS

#

state

autosave 0

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 22000

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

#

# 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

#

# CORE MISC OPTIONS

#

bios

cheat 0

skip_gameinfo 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 ddraw

numscreens 1

window 0

maximize 1

keepaspect 1

prescale 1

effect none

waitvsync 0

syncrefresh 0

#

# DIRECTDRAW-SPECIFIC OPTIONS

#

hwstretch 0

#

# 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 1

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

[Blades]

Nothing huh??

I did find out that the Conversion tools make games such as MK 401x256. However, the AVGA 3000 only supports 400x256. But even after changing the MK.ini, it still won't go into the right res. And it still doesn't explain(if GameEx is only a shell to mame) why Mame runs in GameEx, but not by itself, out of GameEx....hmmm....

;

[Brian Hoffman]

I think the next step is to post your gameex config.