Mamewah Controller Problems

[gonzo90017]

I'm having trouble using mamewah with my ps2 to usb adapter. For some reason even though I assigned button 9 as exit when I press it nothing happens. However when I press button 10 which is assigned as Launch game it exits mamewah! When I reverse them, in other words button 10 as exit and button 9 as start game. When I press button 9 nothing happens but when I press button 10 it launches the game! Can someone please take a look at my .cfg and tell me what i'm doing wrong.
I'm using the latest beta version 13.

### INPUT MAPPINGS ###

# main form
UP_1_GAME         "DIK_UP ¦ JOY1_UP ¦ MOUSE_UP"
DOWN_1_GAME         "DIK_DOWN ¦ JOY1_DOWN ¦ MOUSE_DOWN"
UP_1_PAGE         "DIK_R"
DOWN_1_PAGE         "DIK_F"
UP_1_LETTER         "DIK_LEFT ¦ JOY1_LEFT"
DOWN_1_LETTER         "DIK_RIGHT ¦ JOY1_RIGHT"

FIND_GAME         "DIK_TAB"
RANDOM_GAME         "DIK_LSHIFT"
SELECT_GROUP         
NEXT_GROUP         
PREVIOUS_GROUP         
SELECT_PLATFORM         
NEXT_PLATFORM         
PREVIOUS_PLATFORM      
SELECT_GAMELIST         
NEXT_GAMELIST         
PREVIOUS_GAMELIST      
ADD_GAME_TO_LIST      
REMOVE_GAME_FROM_LIST      
MENU_SHOW         "DIK_2"
MENU_LOCK         
TOGGLE_MOVIE_PREVIEW_DISPLAY   "DIK_M"
TOGGLE_HISTORY_DAT_DISPLAY   "DIK_H"
LAUNCH_GAME         "JOY1_BUTTON10 ¦ DIK_1"
LAUNCH_APP         
LAUNCH_APP_1         
LAUNCH_APP_2         
LAUNCH_APP_3         
LAUNCH_APP_4         
LAUNCH_APP_5         
NEXT_THEME         
PREVIOUS_THEME
EXIT_WITH_CHOICE      
EXIT_TO_WINDOWS         "JOY1_BUTTON9 ¦ DIK_ESCAPE"
EXIT_AND_RUN_APP      
EXIT_AND_REBOOT         
EXIT_AND_SHUTDOWN      

# options form
OP_UP_1_OPTION         "DIK_UP ¦ JOY1_UP ¦ MOUSE_UP"
OP_DOWN_1_OPTION      "DIK_DOWN ¦ JOY1_DOWN ¦ MOUSE_DOWN"
OP_UP_1_OPTION_PAGE      "DIK_LEFT ¦ JOY1_LEFT"
OP_DOWN_1_OPTION_PAGE      "DIK_RIGHT ¦ JOY1_RIGHT"
OP_MENU_SELECT         "DIK_1"
OP_MENU_BACK         "DIK_2"
OP_MENU_HIDE         

# screensaver form
SS_SHOW_TRACK_NAME      "DIK_2"
SS_FIND_N_SELECT_GAME      "DIK_1"

# any form
VOLUME_DOWN         
VOLUME_UP         
VOLUME_MUTE         
PLAY_OR_PAUSE         
PREVIOUS_TRACK         
NEXT_TRACK         
REWIND_TRACK         
FF_TRACK         
      

### SETTINGS ###

# 0 or 1 (off / on)
keyboard 1
mouse 0
joystick 1

# 1+ (milli-seconds)
digital_scroll_rate 125

# 0 = off, 1+ (milli-seconds)
simulated_analog_max_rate 20

# 1-100%
mouse_x_sensitivity 100
mouse_y_sensitivity 100

joy1_x_deadzone 10
joy1_x_saturation 95
joy1_x_sensitivity 100
joy1_x_analog 0

joy1_y_deadzone 10
joy1_y_saturation 95
joy1_y_sensitivity 100
joy1_y_analog 0

joy1_z_deadzone 10
joy1_z_saturation 95
joy1_z_sensitivity 100
joy1_z_analog 0

joy1_rx_deadzone 10
joy1_rx_saturation 95
joy1_rx_sensitivity 100
joy1_rx_analog 0

joy1_ry_deadzone 10
joy1_ry_saturation 95
joy1_ry_sensitivity 100
joy1_ry_analog 0

joy1_rz_deadzone 10
joy1_rz_saturation 95
joy1_rz_sensitivity 100
joy1_rz_analog 0

joy1_slider0_deadzone 10
joy1_slider0_saturation 95
joy1_slider0_sensitivity 100
joy1_slider0_analog 0

joy1_slider1_deadzone 10
joy1_slider1_saturation 95
joy1_slider1_sensitivity 100
joy1_slider1_analog 0

[gonzo90017]

Just solved it. Read the ctrl docs but this wasn't in it unless i'm mistaken this should be added. Mamewah starts counting buttons from 0. In other words button 1 = button 0. Button 2 = button 1 etc...

[bfauska]

That's actually fairly standard computer protocol.  The problem is that windows ignores this and bases things on a numbering system beginning with 1.  For example, the primary monitor on a computer system is monitor 0, windows calls it 1.  I think that it is the same with mice, keyboards and joysticks too.  Although, MameWah does refer to my GPwiz as Joy1, and it is the only joystick in the system, which by the other standard would make it joy0.  whaddaygonnado?  Nobody can make up there mind on a good system I guess.