Build Your Own Arcade Controls Forum
Software Support => GroovyMAME => Topic started by: crispux3 on April 17, 2015, 06:30:25 pm
-
I can't get the Ultrastik 360 to work in GroovyUME. I've enabled the joystick tab, and I've enabled the ume.ini to use joysticks and set 'joystick' to the adstick option. (I'm also launching groovyUME through Mala, which doesn't recognize the stick either).
I have the ultrastik plugged in via USB, but no buttons connected to it. My buttons are connected to a mini-pac.
The buttons seem to work fine as they are connected to the default wiring on the mini-pac, but the joystick will not work at all. I've downloaded the "analog" map to the joystick through the ultramap software.
Funny thing is, I've started an NES emulator (nestopia) through Mala using my keyboard, and the analog joystick and buttons work fine for it, but I cannot use the joystick to scroll lists in Mala nor control anything in MAME/UME.
Does anyone have any advice? I've attached the ume.ini file and added the .txt extension so I could upload it.
My system is:
Windows XP x64 edition, radeon HD4350. Plugged into my mobo's USB ports are Xbox360 controller, mini-pac, Ultrastik 360, and wireless keyboard. It seems that the ultrastik is receiving full power and the led light on it is blinking.
Thanks.
-
Can you get it working with regular MAME?
-
Hi Calamity. After further reading and just plain trial and error, I think I've got the joystick working. For mala, it seems like had to disable "require ultrastik to be plugged in" and also disable "joystick always as analog" in the ultramap software. I also downloaded the ultrastk mala plugin, but I'm not sure if that made a difference or not.
In GroovyUME (MAME) it has to do with the device ID's windows assigns. The Mini-pac and Ultrastik 360 are both seen as game pads in Windows XP, and no matter what I do, the ultrastik will always be assigned an ID higher (or lower I guess would be the proper way of putting it) than the Mini-pac. So Mini=ID1 and Ultrastik=ID2. If I plug in an Xbox 360 controller, it seems to ALWAYS be assigned ID1 and the other two get pushed down the list. MAME was enabling joystick support, but all the controls were mapped to "Joy 1." Since the Mini-pac was assigned in ID 1 by windows, I basically had to assign all the controls manually in the MAME user interface. MAME recognized the ultrastik as Joy 2. After I did this, MAME games seem to play fine. If, however, I plug in an Xbox 360 controller again, the ultrastik immediately gets assigned ID 3 in windows and MAME stops working again unless I'd manually assign the joystick functions.
So I guess unless a person is going to use the input of the U360 and not use a keyboard encoder, MAME should work right away, but if a U360 and a keyboard encoder are both used, one will have to configure MAME manually as the U360 joystick ID will be something other than ID1. And if one wants to plug in a controller at a later point, especially an Xbox 360 controller, well, it'll just be a real headache. Bottom line, I learned that I'll have to plan all my controls beforehand, and not change them unless I want to reconfigure everything. So it seems like it's a windows problem and not a GroovyUME/MAME problem. Andy said that with the U360's it's a real problem in the way Windows assigns Device ID's.
I hope this had made sense.