LEDBlinky Input Map for buttons 17-28

[elsie]

I am trying to figure out how to set up LEDBlinky Input Map for joystick buttons 17-32.  I am using a gpwiz with some buttons in the 17-28 range connected.  The problem is that in the GenLEDBlinkyInputMap application, only options for buttons 1-16 are listed.  These buttons work and are recognized in mame, but I just dont know how to get LEDBlinky to know about them.

Thanks!

[arzoo]

Try this - using the GenLEDBlinkyInputMap app, configure all your ports and temporarily use any input code for the unlisted input code buttons (17-28). Then manually edit the DevicePort-Input.ini file in the LEDBlinky folder using notepad (or any text editor). Change the temporary codes to the correct values.

For example, say you've temporarily assigned JOYCODE_1_BUTTON1 to port 17, but in reality that button is wired to button 17 on the gpwiz. in the DevicePort-Input.ini file, find the line for port 17;
Port17=P1B17,S,JOYCODE_1_BUTTON1
and change it to;
Port17=P1B17,S,JOYCODE_1_BUTTON17

I believe that should do the trick.

[elsie]

Thanks!  I actually wound up adding them to <baseInputCoes> in LEDBlinkyControls.xml and that seemed to do the trick, except that the button numbering seems to be off by one.  On the GPWiz, button 1 is identified in mame as Joy 3 Button 0, and LED Blinky calls it JOYCODE3_BUTTON1.  Same for all of the other buttons I have connected in the 1-16 range (buttons 1,2,3,10,11,12, and 13 are the only ones I have connected from 1-16)  However for button 21, mame identifies it as Joy 3 Button 20 and LEDBlinky also calls it JOYCODE3_BUTTON20 (instead of BUTTON21).  Same for all of the other buttons above 16.  Not a big deal for me since I am not using all of the inputs, but based on this pattern it seems Joy 3 button 15 and joy 3 button 16 in mame might both be identified as JOYCODE3_BUTTON16 in LEDBlinky.

On an unrelated note, right now I am using the trial version.  I know that the splash screen will go away when I purchase the license.  Is anything else affected?  Specifically, it takes much longer to launch a game from mala with the ledblinky plugin.  Will that speed up with the license?

[arzoo]

I'm not sure why you are seeing a discrepancy with the button numbering but bottom line is - blinky must match mame.

The registered version is exactly the same as the trial version but with the splash screen removed and the frame limit on the animation editor.

Blinky does take some extra time on startup while it parses all the data files (mame.xml is rather large), but there should not be any noticeable delay when loading each game. Do you have any animations or options to blink and speak the controls on game start enabled?