LEDBlinky and UltraStick mapping

[Petey09]

Hey Guys,

I'm trying to setup LEDBlinky for my UltraStick 360 so that it automatically maps from 4-Way to 8-Way with MAME. Problem is, except for the Analog mapping, nothing works. There is a "UltrastickTest.exe" that seems to emulate the mapping but, as I said, only Analog mapping actually works. All the other maps are saying "Upload Successful" but none of them actually worked. Do you guys know what might cause this? The firmware on the stick is 2.3 by the way.

Also, I don`t know if its linked but, whenever I launch LEDBlinky, it works on the first launch. After that, every launch fails saying that "Invalid LEDBlinky Input Map file [LedBlinkyInputMap.xml]. No valid LED Controller data. The file may not be a LEDBlinky Input Map". The file in question seems to be generated on first launch so when trying to load it afterwards, it fails for some reason. I'm using the "No LED mode" just to map the ultrastick.

Thanks in advance!

[EMDB]

Does mapping with the official software work? You could take a look at Hypermap in the software forum. This is specially designed to map Ultrasticks based on the launched game...

[arzoo]

Hey Guys,

I'm trying to setup LEDBlinky for my UltraStick 360 so that it automatically maps from 4-Way to 8-Way with MAME. Problem is, except for the Analog mapping, nothing works. There is a "UltrastickTest.exe" that seems to emulate the mapping but, as I said, only Analog mapping actually works. All the other maps are saying "Upload Successful" but none of them actually worked. Do you guys know what might cause this? The firmware on the stick is 2.3 by the way.

Also, I don`t know if its linked but, whenever I launch LEDBlinky, it works on the first launch. After that, every launch fails saying that "Invalid LEDBlinky Input Map file [LedBlinkyInputMap.xml]. No valid LED Controller data. The file may not be a LEDBlinky Input Map". The file in question seems to be generated on first launch so when trying to load it afterwards, it fails for some reason. I'm using the "No LED mode" just to map the ultrastick.

Thanks in advance!

Hi,
In regards to the problem with the Input Map error, this will be fixed in the next release but in the interim I've emailed you a patch file.

As for the U360 problem, when using the UltrastickTest, can you switch over to the Windows Game Controllers dialog and confirm if the range of motion has been restricted based on the loaded map? I looked over the log you provided and it seems that LEDBlinky is loading the correct map files. Here's the relevant entries from the log:

[08/02/2014 11:13:29] UltraStik U360(s) detected: 1   Restrictor Type: 4way/8way/Circular

[08/02/2014 11:13:29] Set UltraStik JDR Map [joy4way.um] for FE.

[08/02/2014 11:13:39] Set UltraStik JDR Map [8-way.um] for OPENICE.

[Petey09]

Thanks for the answers!

EMDB : The official software works and is able to switch to any mapping I select without problems. As for the Hypermap, I'm using Hyperlaunch sand I saw that you need to disable it which is a problem. If I'm not able to fix the problem with LEDBlinky, I'll probably try it out.

arzoo : Thanks for the patch. It fixed the second problem. As for the U360, If I use the official software or Game Controller dialog, I can see that no matter what map I select in the UltrastickTest, it sets the restiction to 360 Analog (Ex. The stick is set to 2-Way through UltraMap and then I set it 8-Way with the test program. It is now set to Analog with no restriction) I've tested with both um files from UltraMap software and LEDBlinky. I also have two sticks so I tried with both and I still have the same problem.

[DietCoke]

Hi,
In regards to the problem with the Input Map error, this will be fixed in the next release but in the interim I've emailed you a patch file.

Any chance you could send it my way as well?

[arzoo]

Hi,
In regards to the problem with the Input Map error, this will be fixed in the next release but in the interim I've emailed you a patch file.

Any chance you could send it my way as well?

I've pm'd you with the download link.

[arzoo]

arzoo : Thanks for the patch. It fixed the second problem. As for the U360, If I use the official software or Game Controller dialog, I can see that no matter what map I select in the UltrastickTest, it sets the restiction to 360 Analog (Ex. The stick is set to 2-Way through UltraMap and then I set it 8-Way with the test program. It is now set to Analog with no restriction) I've tested with both um files from UltraMap software and LEDBlinky. I also have two sticks so I tried with both and I still have the same problem.

LEDBlinky uses the ultrastik.dll function library to communicate with the U360. The log indicates that the commands are going out (as does the "upload successful" message from the test app) - so I'm not sure why the DLL is not actually loading the map. Which version of Windows are you running?

[Petey09]

I'm running Windows 7 64bit.

[arzoo]

I'm running Windows 7 64bit.

When you run the LEDBlinky UltrastikTest app, does it show 1 (or more) joystick detected? I just ran a test on my Win8-64 pc and it worked as expected - loading the selected map file.

[Petey09]

Ok... I finally managed to make it worked has I was testing and it was a really stupid step missing. I had to run LedBlinky or Hyperspin as Administrator. Gotta love Windows. Now I feel stupid for not figuring this out earlier.

Thanks alot arzoo for all your support.

[arzoo]

Ok... I finally managed to make it worked has I was testing and it was a really stupid step missing. I had to run LedBlinky or Hyperspin as Administrator. Gotta love Windows. Now I feel stupid for not figuring this out earlier.

Thanks alot arzoo for all your support.

No worries, glad you got it working. I'm going to add this info to the U360 section on the LEDBlinky support page.

[IAmDotorg]

Ok... I finally managed to make it worked has I was testing and it was a really stupid step missing. I had to run LedBlinky or Hyperspin as Administrator. Gotta love Windows. Now I feel stupid for not figuring this out earlier.

Thanks alot arzoo for all your support.

That's worth reporting to one, or both (I suspect LedBlinky, as running Hyperspin as Administrator is probably spawning a process that inheriting the administrator token from Hyperspin). In 2014, you should have very minimal situations where a process needs to be administrator. So something in that chain of execution isn't being done quite right and should be fixed. (Demand loading of a device driver wrong, or a manifest missing something if its loading a DLL to do it.)

I haven't quite gotten to that point of configuration on my setup (the buttons aren't wired up, so I haven't touched LedBlinky yet other than installing the license). If I see the same problem, I'll fire up procmon/procexp, figure out what call is failing without admin rights and report it to the offending party.