Problem mapping u360 with LEDBlinky in Hyperspin...

[gaijinking]

Hello everyone,
After years of lurking, I'm finally making progress two Mame projects. I'm gutting my old X-arcade tankstick for my home gaming rig, and I'm adding Mame & Daphne to the Space Ace/Dragon's Lair cabinet at our studio. Hopefully I'll be able to post some pics up here shortly, but I digress. For the past few nights I've been pulling my hair out trying to get LEDBlinky to correctly send maps to my u360s for Hyperspin. I've set the paths to mame.xml and controls.ini (on the mame tab), and checked the 'UtltraStik 360' and 'No LEDs Mode' options (on the Misc Options tab).
I'm using the current controls.ini version 0.111.5 and I've set my Ultramap to analog and I've adjusted my mame.ini joystick_map to 7778...4445
It seems like everything is setup and working just fine in Hyperspin, but if I try to launch digdug, pacman, or qbert, the controls are just terrible. Upon further inspection of my debug log I'm getting  

Set UltraStik JDR Map [joy8way.um] for QBERTTST.
Event: FEGameQuit
Set UltraStik JDR Map [joy4way.um] for FE.
Set UltraStik JDR Map [joy8way.um] for PACMANBLA.

But when if I try to reload LEDBlinkyConfig.exe I keep getting "Access violation at address 004c29cf in module "LEDBlinkyConfig.exe" Read of address FFFFFFC4."  which prevents me from loading and saving changes in the config, so I'm forced to reinstall Ledblinky again, and again.
Does anybody know what I might be doing wrong?

[arzoo]

You've got two options when it comes to the u360 - you can use LEDBlinky to set the maps OR set the stick(s) to analog mode and let mame use its own maps. But I think you're using both. With LEDBlinky, you don't need to set the mame.ini joystick_map or set the stick to analog mode (blinky is overriding that mode anyway). As for the config app crashing - that will require more info for me to help. My suggestion is this, if you only need to change the u360 maps for mame (and remain analog for other emulators), then take blinky out of the picture - don't use it. But if you want to set unique maps for each emulator (or game) then you can continue using blinky and you'll need to do some tweaking to get the right maps to load for those games you mentioned.

[gaijinking]

Hey arzoo,
Thanks for responding so quickly! I would really like to use LEDBlinky, specifically because I do play a lot of Qbert and 4 way games, as well as other emulators. So for the mame.ini, I guess I misunderstood what was said here:http://forum.arcadecontrols.com/index.php?topic=98058.msg1037393#msg1037393
"Quote from: Ginsu Victim on November 20, 2009, 11:30:54 AM
Ok, I'm not sure I understand. What do I need to do to make sure MAME doesn't interfere with my U360's mapping?

in the mame.ini change:
-joystick_map auto
to:
-joystick_map 7778...4445"

So to prevent me from using both, what should I set my joystick_map to? And what should I set my u360 to using Ultramap, if at all? so that it doesn't interfere with LEDBlinky.
As for the weirdness with the config app crashing, what type of info would you need?
I'm running xp pro sp3 from the tinyxp rev 10 setup.

[arzoo]

Oh yeah - I forgot about that thread So yes, set the mame joystick_map to 7778...4445. Don't worry about setting the u360 mode with the Ultramap application - blinky will override any map you set.

Using blinky to map the u360, most games should work fine - but from your 1st post it seems like blinky is setting the 8-way map for the games that should be 4-way (PACMANBLA) or diagonal (QBERTTST). So something is not configured correctly. Email me your debug.zip file and I'll take a look.

As for the config app crashing - I wonder if it has something to do with tinyxp - maybe a required windows component is missing (like the sapi speech stuff). When does it crash - at startup before any window is displayed or when you click a button or select an option?