Strange new error

[cquealy]

I recently encountered an error that I can't figure out. I run two version of MAME on my cab in Gameex. Mame64 so that some of the more demanding games run better and a hackedmame32 version for my light gun games and for Birdie King that doesn't work in MAME64(The tracking is off in mame64 for some reason). Just recently, the trackball device doesn't work anymore in Gameex for the hackedmame version. It works fine outside of gameex.

Any thoughts? I have attached my log.

Thanks.

dhlog.txt

[fRequEnCy]

Are you using a mame.ini file to call your arguments as I don't see any being called from the command-line shown in the log? Perhaps that's why it's not working if you don't use a mame.ini file.

[cquealy]

Are you using a mame.ini file to call your arguments as I don't see any being called from the command-line shown in the log? Perhaps that's why it's not working if you don't use a mame.ini file.

Not sure what you mean. I beem using the mame with gameex for about three years. It's been working fine but just recently did I encounter the trackball not working in gameex for those games.

[fRequEnCy]

This is one of the commands you're calling:

 Running: cmd.exe /c C: mamep.exe  centiped.zip

That being said, where are the settings being called? There are no other arguments being passed to the command-line. So that means things are not being called but have to assume you're using a mame.ini file in your mame directory to call those settings or then it wouldn't even run the rom since the rom directory isn't being passed. To make it simple, do you have a mame.ini file in that mame directory?

[cquealy]

I do have a mame.ini but it must be autogenerated. It's been working fine in and out of gameex for over a year or so but just recently stopped recognizing the trackball in gameex. I have a slikstik quad which might be one of the last produced & delivered! What's even stranger is that the reason for using the two different version of mames (32bit & 64bit) was due to light gun games not working in mame64 (couldn't run the configurations) and now i can. The axises used to show two coordinates (gun1x gun2x) for horizontal & (gun1y gun2y) for vertical but now theu just show one cooridnate (gun1x) so maybe I was just configuring wrong. Only problem I have now is in MAME64 the bking game not being accurate (not distinguishing between fairway and bunker). If someone else is a birdie king fan and is running maem64, I would love to know if you are experiencing the same glitch.

So if my issue is not calling the mame.ini, how would i put that in the command line?

[Adultery]

You should be able to just add a 1 in the INI for load MAME.INI, or at least that's what works for vanilla mame.

[fRequEnCy]

I would assume it's already being used because of what I mentioned above about the paths. Please post your mame.ini file and we'll take a look at your settings.

[cquealy]

#

# CORE CONFIGURATION OPTIONS

#

driver_config mame,plus

#

# CORE CONFIGURATION OPTIONS

#

readconfig 1

#

# CORE SEARCH PATH OPTIONS

#

rompath C:\Emulators\HackedMAMEPlus118\roms

samplepath C:\Emulators\HackedMAMEPlus118\samples

artpath artwork

ctrlrpath C:\Emulators\HackedMAMEPlus118\ctrlr

inipath C:\Emulators\HackedMAMEPlus118\ini

fontpath .;lang

translation_directory lang

localized_directory lang

ips_directory ips

#

# 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 FILENAME OPTIONS

#

cheat_file cheat.dat

history_file history.dat

story_file story.dat

mameinfo_file mameinfo.dat

command_file command.dat

hiscore_file hiscore.dat

#

# CORE STATE/PLAYBACK OPTIONS

#

state

autosave 0

playback

record

mngwrite

wavwrite

#

# CORE PERFORMANCE OPTIONS

#

autoframeskip 0

frameskip 0

seconds_to_run 0

throttle 1

sleep 1

#

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

use_overlays 0

use_bezels 0

#

# CORE SCREEN OPTIONS

#

brightness 1.000000

contrast 1.000000

gamma 1.000000

pause_brightness 0.650000

scale_effect none

#

# CORE VECTOR OPTIONS

#

antialias 1

beam 1.000000

flicker 0.000000

#

# CORE SOUND OPTIONS

#

sound 1

samplerate 48000

samples 1

volume 0

volume_adjust 1

#

# CORE INPUT OPTIONS

#

ctrlr SlikStik_Quad

mouse 1

joystick 0

lightgun 0

multikeyboard 0

multimouse 0

steadykey 0

offscreen_reload 1

joystick_map auto

joystick_deadzone 0.300000

joystick_saturation 0.850000

#

# 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

#

# CORE MISC OPTIONS

#

bios default

cheat 1

skip_gameinfo 1

ips

confirm_quit 0

auto_pause_playback 0

m68k_core c

use_trans_ui 1

ui_transparency 224

#

# CORE PALETTE OPTIONS

#

font_blank 0,0,0

font_normal 255,255,255

font_special 247,203,0

system_background 16,16,48

button_red 255,64,64

button_yellow 255,238,0

button_green 0,255,64

button_blue 0,170,255

button_purple 170,0,255

button_pink 255,0,170

button_aqua 0,255,204

button_silver 255,0,255

button_navy 255,160,0

button_lime 190,190,190

cursor 60,120,240

#

# CORE LANGUAGE OPTIONS

#

language en_US

use_lang_list 1

#

# WINDOWS DEBUGGING OPTIONS

#

oslog 0

#

# WINDOWS PERFORMANCE OPTIONS

#

priority 0

multithreading 0

#

# WINDOWS VIDEO OPTIONS

#

video d3d

numscreens 1

window 0

maximize 1

keepaspect 1

prescale 1

effect none

waitvsync 0

syncrefresh 0

#

# 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 \\.\DISPLAY1

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 0

switchres 0

full_screen_brightness 1.000000

full_screen_contrast 1.000000

full_screen_gamma 1.000000

#

# WINDOWS SOUND OPTIONS

#

audio_latency 1

#

# INPUT DEVICE OPTIONS

#

dual_lightgun 0

joyid1 0

joyid2 1

joyid3 2

joyid4 3

joyid5 4

joyid6 5

joyid7 6

joyid8 7

[Adultery]

I thought this was unusual, but maybe it's not?

fontpath .;lang

Shouldn't it be:

fontpath lang

[cquealy]

Attached is screenshot of Birdie King error (ball is clearly not in bunker but the game thinks it is). Works great in mame32, not so great in mame64.

bking screen error.bmp

[Adultery]

Do you have it set up to stretch like that or is that the original game aspect ratio?

It almost looks to me like it's stretching the game images but not tracking properly since the bunker would be there if it was a 4:3 ratio. Plus the ball almost looks more like a rectangle to me.

Just taking a stab, I really don't know what else to tell you to try.

.:EDIT:. Wait, I bet you use your wide screen monitor turned sideways huh? The MAWS image looks like it's a vertical game. If so, I'm leaning more and more towards that image being stretched and things not tracking as they should. Maybe it's a MAME64 bug? I don't use that build, so I can't say for sure. I would try turning the stretching off and see if you still get an error.

[cquealy]

I actually grabbed that screenshot off this youtube clip http://www.youtube.com/watch?v=coA1_IY0PkE so I'm thinking it's more global thatn my system and is an issue with MAME64. I have the asepct ratio right on mine and still the inaccuracy problem. If you run mame64 and I would love to know if it happens to you.

Oh well, looks like I'll just have to setup up mame32 as an emualator & figure out how to get my trackball working in gameex again. The trackball works in mame configure in gameex. Just not working when ame is configured as an emulator.

[cquealy]

Did some more research and found out my birdie king problem is a mame issue:

http://www.mametesters.org/view.php?id=3863

Still would like to know why I can't get the the older version of MAMEUI to have trackball functionality when set up as an emulator. It works outside of gameex but not inside.

[Adultery]

Are you using an advanced config?