Build Your Own Arcade Controls Forum
Main => Main Forum => Topic started by: Xynie on September 06, 2010, 08:47:37 am
-
Silly question, but I can't seem to figure this out. I want to permanently change a button assignment in Mame, but when I Tab and change the general key assignment it doesn't seem to work. It works for that game, but as soon as I go back to my frontend and start another game, it reverts back to the default controls.
Is there a text file I can edit instead of using the tab screen? I am running .138.
Thanks!
-
When in the Mame menu, are you changing the inputs for just that game or for all? If you exit the game and then restart the same one, does the button keep it's configuration?
-
I've tried it both ways, and when I exit and re-enter the same game, it does not save the changes. It works while I play the game, but as soon as I reload it reverts back.
-
If you go into your mame directory, do you have a config folder? If so, do you have files in there? Deleting anything in there may help. I don't have Mame installed on this pc, so I can't easily check that right now.
The other guess is to make sure that the Mame folder or sub-directories and files are write protected. I don't know if that would affect things like this but it's something to check. If you're running XP, that could be the issue. :dunno
-
Not sure if there should be one... but there is no default.cfg file in the ctrl directory, so i can't find anything to manually change settings. Also, I just tested again, changes settings within a game... it worked in game... exited and restarted same game, controls revert. Do I need to create a default.cfg? Does frontend matter? (Hyperspin) Just making sure....
-
If you go into your mame directory, do you have a config folder? If so, do you have files in there? Deleting anything in there may help. I don't have Mame installed on this pc, so I can't easily check that right now.
The other guess is to make sure that the Mame folder or sub-directories and files are write protected. I don't know if that would affect things like this but it's something to check. If you're running XP, that could be the issue. :dunno
No CFG folder... although mame.ini does point to it <shrug>
-
Mame.ini.... if this helps. Is there a setting I need to turn on to enable saving controls, like I had to enable the mouse? :)
<UNADORNED0>
#
# 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 48000
samples 1
volume 0
#
# CORE INPUT OPTIONS
#
coin_lockout 1
ctrlr
mouse 1
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 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 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 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 0
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
-
More details please including:
Command line mame, Mame32 (or 64) and what Front End?
Computer OS?
Try a fresh install of Mame. Don't delete anything, just install Mame again and point the directory to the proper Rom folder.
-
And when you hit tab to enter the Menu, you aren't pausing the game first are you? That causes problems.
-
Mame.ini above...
Mame64 .138 on XP 64-bit
Hyperspin
No pause... just straight to pressing tab. This is a weird one... I have been using Mame for a long time, this is a first for me :)
-
Mame.ini above...
Mame64 .138 on XP 64-bit
Hyperspin
No pause... just straight to pressing tab. This is a weird one... I have been using Mame for a long time, this is a first for me :)
Well at least it isn't an easy one so far. :)
-
Do you have a cntrl file in the cntrl folder?
I wish u_rebelscum was here, he's aces at this stuff. He was on today, but hasn't posted in about 6 months. :'(
-
The contents of the cntrl folder are all named controllers, like slikstick and hotrod. There is no default.cfg or cntrl.cfg
Thanks for your help :)
-
The contents of the cntrl folder are all named controllers, like slikstick and hotrod. There is no default.cfg or cntrl.cfg
Thanks for your help :)
I'm just jacking up my post count. We get double counts on holidays. ;D
Try reinstalling Mame though. It shouldnt take too long and may help.
-
Also, try launching a game outside of your FE. I don't know anything about Hyperspin, but it could have a setting that doesn't accept your change. Not blaming the FE, but it's one thing to try to rule it out.
So use the command line to run a game, change the input, exit it, and try again.
-
OK... downloaded .139, ran it completed seperate in a new, unconfigured install/directory through Hyperspin. Same thing... let me try without hyperspin... To be continued!
-
Is getting a dedicated for the game in question an option? :laugh2:
-
Is getting a dedicated for the game in question an option? :laugh2:
Haha... well, it happens on all the games. Long story short, I have a bad IPAC4 with mismapped ports. Andy sent me a new one, but I am trying to get it to work for the holiday party as a two player. It works, but it won't save the settings.
OK, so the plot thickens... I launched a game outside of hyperspin, changed the settings, relaunched...it worked. Sounds like a hyperspin thing to me... Off to their forums :) Thanks for all your help :)
-
Oh, the Hyperspin haters are going to love this. j/k Hopefully, you can make a simple change and have it work. :cheers:
Do try and post the findings here in case someone else searches for the same problem please.
-
I figured out a workaround... I turned off the "Hyperlaunch" feature in HyperHQ and launched Mame as a normal executable... that resolves the issue.
Thanks for helping me track it down. I will head over to the Hyperlaunch forums to see if it is something I did, or something that doesn't work.
Thanks gain!