Home Page Forums Archives MAME OS X HID Control Setting not saving

Has anyone else had an issue where they sat controls for an HID device (wireless rumblepad) and it takes as long as you play the game but it won't save once mame stops?

All my video setting save, just not my controller settings. I've tried this on 2 computers (Quad Xeon MacPro and a Macbook Pro), both have the issue with Mame OS X 114.

Anyone else experiencing this?

Just found that if I go back to version 112-1 and make a change to the controller, it saves in the pref. But if I use 114, it then refuses to save any changes.

Seems to happen more with the right analog controller setting. For example Right/Left controller button setting always defaults back to one of my HID buttons rather than an analog control. (112-1 doesn't really notice the right analog control well so it's hard to just set it with that and carry on).

So it seems that it's just a problem with 114 writing(or not writing) bad pref info.

Once again, it happens on 2 machines so it does seem to be a mame os x issue.(though, anything, including my setup, is possible)

Ok, even though I appear to be having a conversation with myself in this thread :-), I wanted to make sure to get this info out there. On my rumblepad it seems as though I can have both controllers connected and most settings do save in my mame preferences. Though, the setting for P1 Righ/Left and P2 Right/Left don't save under any circumstance. I originally found this by trying to setup both analog controls to play robotron and then smash TV.

Dave, is there any ways there is an issue that would affect just this particular HID setting and would prevent it from saving once MAME OS X is quit?

This is all very odd. Are you trying to change the settings in "Input (general)" or "Input (this game)"? I haven't tried to reproduce this, yet. I can't think of any issue that would cause this. The pref reading/writing for inputs is handled by core MAME, so it's possible something changed, there.

-Dave

"""Are you trying to change the settings in "Input (general)" or "Input (this game)"? """

If I set as "general" or "this game" it always defaults "P1 Right/Left" and "P2 Right/Left" back to a setting of "J1 or J1 Button 1". I've now tried it on 3 machines with multiple games. So it's surely seems like a real bug, but I'm not sure if it's in the controller, MAME, or somewhere else.

Here's the dig, I can set it as a key on the keyboard,(the q key, for example) and that will take. I can also set it to another analog setting with either analog stick and it will take. But setting it to "P1 Right/left" to a setting of "J1 Axis 3-" will never take after I quit MAME OSX. But as long as I set it and then play, it's fine for as long as MAME is running.

I've got 2 of these controllers and they both do the same thing. So it may be with the controller, but it's odd that MAME sees the input and registers it and plays with it, yet won't save it after it quits.

I've posted a pic of it here just in case I"m not describing it well. It's obvious which one is not saving as I have the rest of them highlighted.

http://homepage.mac.com/kbebee/PhotoAlbum24.html

What do you think? Controller issue or a deeper bug?

I've had the same issue in SDLMAME for far longer (i.e. versions before .114) using a Playstation analogue pad (non-rumbly) using a Lik-Sang n64/psx converter. Sometimes the start button loses mapping as well. The right/left mapping will stick for the one game, but change games and it's gone. I wouldn't chalk it up to code without more testing of different controllers.

You could try moving the "Config" directory out of the way:


Also, maybe the NVRAM. Once or twice, I've had "wierd things happen" with newer versions of MAME opening these files generated by older versions. Just move them to your Desktop, so you can revert back, after the experiment.

-Dave

I got a friend of mine to test the same setup Sean has, with PS controller with converter and the issue happens on his setup too.

I tried the config troubleshooting but it looks like it's happening with multiple controllers on a spread of machines.

If Sean had it happen with SDLMAME, then I'm assuming it's either a Core MAME bug or just the way these right analog controllers interact with the setup. Since I don't have any access to other controllers with dual analog sticks, I'm kinda stuck at this point.

Hopefully someone else has other controllers and can verify this to show if it's a real bug.