LEDBlinky and U360 4 to 8 way switching problem

[BluepointVance]

I'm running hyperspin 1.2 on windows XP with a trial of the latest version of LEDBlinky (just to see if it will work for mapping the u360, then I'll buy!) and two u360 sticks... Everything works great until I attempt to play an 8 way game (i.e. Street Fighter) after just playing a 4 way game (i.e. Ms PacMan)...

For some reason whenever I try to do this, the joysticks remain stuck in 4way mode.

I've got the mame.ini joystick_map set to 7778...4445 as per a recommendation on the board here.

I have a debug.zip from ledblinky of this exact problem occurring, here:http://www.megaupload.com/?d=4144A5SK

Kinda lost as to what to do next. Any help or suggestions greatly appreciated.

Thanks!

[arzoo]

I see a couple of issues here. First, for the MAME.xml setting you are using LEDBlinkyControls.xml. You need to download or create a mame.xml file and point the setting to that file. And second, it seems that HS is not passing the correct emulator value to blinky. For example, when loading the mame wheel, HS should pass the "mame.exe" (or whatever version of mame you are using) - but the log shows the emulator loading as "Street Fighter" or "Neo Geo" or "Favorites". I'm not sure why this is, but it doesn't seem right. This may be an HS configuration problem.

With both those issues, LEDBlinky will use default mappings for the u360s; 4-way when HS is active and 8-way when any emulator or game is active. So the question is, if blinky is loading the 8-way map (as the log indicates), why don't you see any change to the joysticks? One thing you could try is load the windows game controllers dialog and then when an emulator game is running, alt-tab over to the joystick dialog and confirm if the 8-way map is loaded. You could also try using the ultramap app check if the joystick mapping can be changed.

[8BitMonk]

I had this issue with version 5.0.0.1 of LEDBlinky. It does not seem to set maps correctly for HS whereas 5.0.0.0 does. Try using the older version and make sure you have the restrictor set to 4/8/circular from within LEDBlinky as well.

[BluepointVance]

I see a couple of issues here. First, for the MAME.xml setting you are using LEDBlinkyControls.xml. You need to download or create a mame.xml file and point the setting to that file.

Thanks. Somehow I missed that... Didn't really effect the problem. Debug output looks the same. Still logging emulators as "Street Fighter" or "Favorites" (these, of course, being the sub wheels) instead of outputting them as MAME.EXE


One thing you could try is load the windows game controllers dialog and then when an emulator game is running, alt-tab over to the joystick dialog and confirm if the 8-way map is loaded. You could also try using the ultramap app check if the joystick mapping can be changed.

Will try this, thanks!



I had this issue with version 5.0.0.1 of LEDBlinky. It does not seem to set maps correctly for HS whereas 5.0.0.0 does. Try using the older version and make sure you have the restrictor set to 4/8/circular from within LEDBlinky as well.

Thanks! Any idea where I could get LEDBlinky 5.0.0.0 -- I'm running 5.0.0.4 now, and that appears to be the only version available on the LEDBlinky site...

I'll try to mess with it some more, then I might just try to switch to the Analog/Let-MAME-handle-it solution until we get Hyperspin 2.0.

[8BitMonk]

Thanks! Any idea where I could get LEDBlinky 5.0.0.0 -- I'm running 5.0.0.4 now, and that appears to be the only version available on the LEDBlinky site...

I'll try to mess with it some more, then I might just try to switch to the Analog/Let-MAME-handle-it solution until we get Hyperspin 2.0.

I doubt Hyperspin 2.0 will fix the issue. You'd need to get the older version from Arzoo. Mame won't handle it, without LEDBlinky or some other script it the U360's will stay set to what whatever you set them to (using the UltraMap utility) for every game.

My problem was from HS sending the syntax ledblinky.exe 3 plus the romname instead of ledblinky.exe 1 plus the romname which for some reason worked (for me anyway) using version 5.0.0.0 and not in 5.0.0.1. Not sure of versions after that. Arzoo and I did a bunch of testing and sending log files back and forth etc. last April and could never really pinpoint why it didn't work in the newer LEDBlinky version. I'm not sure this is your issue since you are having other configuration questions but it's something to try.

[BluepointVance]

I doubt Hyperspin 2.0 will fix the issue. You'd need to get the older version from Arzoo. Mame won't handle it, without LEDBlinky or some other script it the U360's will stay set to what whatever you set them to (using the UltraMap utility) for every game.

My problem was from HS sending the syntax ledblinky.exe 3 plus the romname instead of ledblinky.exe 1 plus the romname which for some reason worked (for me anyway) using version 5.0.0.0 and not in 5.0.0.1. Not sure of versions after that. Arzoo and I did a bunch of testing and sending log files back and forth etc. last April and could never really pinpoint why it didn't work in the newer LEDBlinky version. I'm not sure this is your issue since you are having other configuration questions but it's something to try.

Thanks for this, I think I might try to reinstall everything from scratch and see if I can get LEDBlinky to send the right commands... It's probably something that I screwed up with the Hyperspin install.