LEDBlinky! and ctrlr files

[jhabers]

I am having a hard time with LEDBlinky! and a ctrlr file. I am assuming that this will work the way I invision it. I will try to explain what I am trying to do.

Here is my button layout

  XXX
  XXX
X

I have my ctrlr file and it is working fine the following way:

For SF type games:

  123
  456
X

For neogeo type games

  XXX
  234
1

This all works fine

Where I run into a problem is trying to light them accordng to the ctrlr file. I am using a pac drive board with MALA and mame .123. The SF type games light correctly as follows

  123
  456
X

but the neo geo light up the same like this (no change):

  XXX
  234
1

the actual controls are right but the LEDs are wrong.

I cant figure out how to get a neo geo game light like this

  XXX
  234
1

Any help would be GREATly appreciated!

Here is my ctrlr file

-------------------------------------

<mameconfig version="10">
   <system name="default">

      <!--
         IPAC2/MINIPAC input customization file
         Sharkus
         Revision 1.0 - 1/24/06
      -->
      
      <input>

         <!--
            The following keys must be mapped to shifted buttons using WinIPAC or equivalent.
            P1B8 and P2B8 can also be used (if 8 buttons per player are not required).
         
-->
         <port type="UI_PAUSE">
            <newseq type="standard">KEYCODE_P</newseq>
         </port>
         <port type="UI_CONFIGURE">
            <newseq type="standard">KEYCODE_TAB</newseq>
         </port>
         <port type="UI_CANCEL">
            <newseq type="standard">KEYCODE_ESC</newseq>
         </port>
         <port type="UI_ON_SCREEN_DISPLAY">
            <newseq type="standard">KEYCODE_TILDE</newseq>
         </port>


                  

         <!--
            The following keys are the default mapping used by the IPAC2/MiniPAC
         -->

         <!-- IU Configuration -->
         <port type="UI_UP">
            <newseq type="standard">KEYCODE_UP OR JOYCODE_1_UP</newseq>
         </port>
         <port type="UI_DOWN">
            <newseq type="standard">KEYCODE_DOWN OR JOYCODE_1_DOWN</newseq>
         </port>
         <port type="UI_LEFT">
            <newseq type="standard">KEYCODE_LEFT OR JOYCODE_1_LEFT</newseq>
         </port>
         <port type="UI_RIGHT">
            <newseq type="standard">KEYCODE_RIGHT OR JOYCODE_1_RIGHT</newseq>
         </port>
         <port type="UI_SELECT">
            <newseq type="standard">KEYCODE_LCONTROL OR KEYCODE_ENTER OR JOYCODE_1_BUTTON1</newseq>
         </port>

         <!-- Player 1 Configuration -->
         <port type="START1">
            <newseq type="standard">KEYCODE_1 OR JOYCODE_1_START</newseq>
         </port>
         <port type="COIN1">
            <newseq type="standard">KEYCODE_5 OR JOYCODE_1_SELECT</newseq>
         </port>
         <port type="P1_JOYSTICK_UP">
            <newseq type="standard">KEYCODE_UP OR JOYCODE_1_UP</newseq>
         </port>
         <port type="P1_JOYSTICK_DOWN">
            <newseq type="standard">KEYCODE_DOWN OR JOYCODE_1_DOWN</newseq>
         </port>
         <port type="P1_JOYSTICK_LEFT">
            <newseq type="standard">KEYCODE_LEFT OR JOYCODE_1_LEFT</newseq>
         </port>
         <port type="P1_JOYSTICK_RIGHT">
            <newseq type="standard">KEYCODE_RIGHT OR JOYCODE_1_RIGHT</newseq>
         </port>
         <port type="P1_BUTTON1">
            <newseq type="standard">KEYCODE_LCONTROL OR JOYCODE_1_BUTTON1 OR MOUSECODE_1_BUTTON1</newseq>
         </port>
         <port type="P1_BUTTON2">
            <newseq type="standard">KEYCODE_LALT OR JOYCODE_1_BUTTON2 OR KEYCODE_L</newseq>
         </port>
         <port type="P1_BUTTON3">
            <newseq type="standard">KEYCODE_SPACE OR JOYCODE_1_BUTTON3 OR MOUSECODE_1_BUTTON2</newseq>
         </port>
         <port type="P1_BUTTON4">
            <newseq type="standard">KEYCODE_LSHIFT OR JOYCODE_1_BUTTON4</newseq>
         </port>
         <port type="P1_BUTTON5">
            <newseq type="standard">KEYCODE_Z OR JOYCODE_1_BUTTON5</newseq>
         </port>
         <port type="P1_BUTTON6">
            <newseq type="standard">KEYCODE_X OR JOYCODE_1_BUTTON6</newseq>
         </port>
         <port type="P1_BUTTON7">
            <newseq type="standard">KEYCODE_C</newseq>
         </port>
         <port type="P1_JOYSTICKRIGHT_UP">
            <newseq type="standard">KEYCODE_R OR JOYCODE_1_BUTTON2</newseq>
         </port>
         <port type="P1_JOYSTICKRIGHT_DOWN">
            <newseq type="standard">KEYCODE_F OR JOYCODE_1_BUTTON3</newseq>
         </port>
         <port type="P1_JOYSTICKRIGHT_LEFT">
            <newseq type="standard">KEYCODE_D OR JOYCODE_1_BUTTON1</newseq>
         </port>
         <port type="P1_JOYSTICKRIGHT_RIGHT">
            <newseq type="standard">KEYCODE_G OR JOYCODE_1_BUTTON4</newseq>
         </port>
         <port type="P1_JOYSTICKLEFT_UP">
            <newseq type="standard">KEYCODE_UP OR JOYCODE_1_UP</newseq>
         </port>
         <port type="P1_JOYSTICKLEFT_DOWN">
            <newseq type="standard">KEYCODE_DOWN OR JOYCODE_1_DOWN</newseq>
         </port>
         <port type="P1_JOYSTICKLEFT_LEFT">
            <newseq type="standard">KEYCODE_LEFT OR JOYCODE_1_LEFT</newseq>
         </port>
         <port type="P1_JOYSTICKLEFT_RIGHT">
            <newseq type="standard">KEYCODE_RIGHT OR JOYCODE_1_RIGHT</newseq>
         </port>

         <!-- Player 2 Configuration -->
         <port type="START2">
            <newseq type="standard">KEYCODE_2 OR JOYCODE_2_START</newseq>
         </port>
         <port type="COIN2">
            <newseq type="standard">KEYCODE_6 OR JOYCODE_2_SELECT</newseq>
         </port>
         <port type="P2_JOYSTICK_UP">
            <newseq type="standard">KEYCODE_R OR JOYCODE_2_UP</newseq>
         </port>
         <port type="P2_JOYSTICK_DOWN">
            <newseq type="standard">KEYCODE_F OR JOYCODE_2_DOWN</newseq>
         </port>
         <port type="P2_JOYSTICK_LEFT">
            <newseq type="standard">KEYCODE_D OR JOYCODE_2_LEFT</newseq>
         </port>
         <port type="P2_JOYSTICK_RIGHT">
            <newseq type="standard">KEYCODE_G OR JOYCODE_2_RIGHT</newseq>
         </port>
         <port type="P2_BUTTON1">
            <newseq type="standard">KEYCODE_A OR JOYCODE_2_BUTTON1</newseq>
         </port>
         <port type="P2_BUTTON2">
            <newseq type="standard">KEYCODE_S OR JOYCODE_2_BUTTON2</newseq>
         </port>
         <port type="P2_BUTTON3">
            <newseq type="standard">KEYCODE_Q OR JOYCODE_2_BUTTON3</newseq>
         </port>
         <port type="P2_BUTTON4">
            <newseq type="standard">KEYCODE_W OR JOYCODE_2_BUTTON4</newseq>
         </port>
         <port type="P2_BUTTON5">
            <newseq type="standard">KEYCODE_I OR JOYCODE_2_BUTTON5</newseq>
         </port>
         <port type="P2_BUTTON6">
            <newseq type="standard">KEYCODE_K OR JOYCODE_2_BUTTON6</newseq>
         </port>
         <port type="P2_BUTTON7">
            <newseq type="standard">KEYCODE_J</newseq>
         </port>
      </input>
   </system>
    <system name="neogeo">
        <input>
            <port type="P1_BUTTON1" mask="4096" index="26" defvalue="4096">
                <newseq type="standard">
                    KEYCODE_C
                </newseq>
            </port>
            <port type="P1_BUTTON2" mask="8192" index="27" defvalue="8192">
                <newseq type="standard">
                    KEYCODE_LSHIFT
                </newseq>
            </port>
            <port type="P1_BUTTON3" mask="16384" index="28" defvalue="16384">
                <newseq type="standard">
                    KEYCODE_Z
                </newseq>
            </port>
            <port type="P1_BUTTON4" mask="32768" index="29" defvalue="32768">
                <newseq type="standard">
                    KEYCODE_X
                </newseq>
            </port>
            <port type="P2_BUTTON1" mask="4096" index="36" defvalue="4096">
                <newseq type="standard">
                    KEYCODE_J
                </newseq>
            </port>
            <port type="P2_BUTTON2" mask="8192" index="37" defvalue="8192">
                <newseq type="standard">
                    KEYCODE_W
                </newseq>
            </port>
            <port type="P2_BUTTON3" mask="16384" index="38" defvalue="16384">
                <newseq type="standard">
                    KEYCODE_I
                </newseq>
            </port>
            <port type="P2_BUTTON4" mask="32768" index="39" defvalue="32768">
                <newseq type="standard">
                    KEYCODE_K
                </newseq>
            </port>
        </input>
    </system>
</mameconfig>


------------------------------------------------------

Here is my DevicePort-Input file

--------------------------------------------------------


[PACDrive-Device1]
Port01=P1B1,S,KEYCODE_LCONTROL
Port02=P1B2,S,KEYCODE_LALT
Port03=P1B3,S,KEYCODE_SPACE
Port04=P1B4,S,KEYCODE_LSHIFT
Port05=P1B5,S,KEYCODE_Z
Port06=P1B6,S,KEYCODE_X
Port07=P1B7,S,KEYCODE_C
Port08=
Port09=TRACKBALL,S,MOUSECODE_1_ANALOG_X|MOUSECODE_1_ANALOG_Y|MOUSECODE_1_ANALOG_Z
Port10=P2B1,S,KEYCODE_A
Port11=P2B2,S,KEYCODE_S
Port12=P2B3,S,KEYCODE_Q
Port13=P2B4,S,KEYCODE_W
Port14=P2B5,S,KEYCODE_I
Port15=P2B6,S,KEYCODE_K
Port16=P2B7,S,KEYCODE_J

-----------------------------------------------------

The rest should be stock I think. What am I doing wrong?

Thanks

Jonathan

[arzoo]

Jonathan,
There's nothing wrong with your config. I see what the problem is - mame picks up the layout from the ctrlr file using 'neogeo', but LEDBlinky is using the actual rom name, 'burningf' for example - so it's not using the neogeo layout for lighting the buttons. I guess I never tested a controller file with a neogeo game DOH! I'll look into a fix.

[jhabers]

Jonathan,
There's nothing wrong with your config. I see what the problem is - mame picks up the layout from the ctrlr file using 'neogeo', but LEDBlinky is using the actual rom name, 'burningf' for example - so it's not using the neogeo layout for lighting the buttons. I guess I never tested a controller file with a neogeo game DOH! I'll look into a fix.

Thank you very much, I will axiously be waiting for a fix. 

Jon

[headkaze]

Jonathan,
There's nothing wrong with your config. I see what the problem is - mame picks up the layout from the ctrlr file using 'neogeo', but LEDBlinky is using the actual rom name, 'burningf' for example - so it's not using the neogeo layout for lighting the buttons. I guess I never tested a controller file with a neogeo game DOH! I'll look into a fix.

Yep I had to add support for that in my plugin as I have the 7 button layout with the bottom row for neogeo.

The following topic might help.

http://forum.arcadecontrols.com/index.php?topic=67601.0

[arzoo]

Yep I had to add support for that in my plugin as I have the 7 button layout with the bottom row for neogeo.

The following topic might help.

http://forum.arcadecontrols.com/index.php?topic=67601.0

I remember that thread - as I recall my brain started to hurt when u_rebelscum chimed in. If I had kept reading I might have avoided the LEDBlinky bug with neogeo games. But better late than never! Thanks HK.

[jhabers]

Jonathan,
There's nothing wrong with your config. I see what the problem is - mame picks up the layout from the ctrlr file using 'neogeo', but LEDBlinky is using the actual rom name, 'burningf' for example - so it's not using the neogeo layout for lighting the buttons. I guess I never tested a controller file with a neogeo game DOH! I'll look into a fix.

arzoo, 8 years later and I am getting back into my cab (kids happened ) I am running into this same problem again as described in the first post. if I create a <romname>.cfg it works but when I use a ctrlr file it does not. Did the fix get cut out of your code along the way?

Thanks!

[arzoo]

arzoo, 8 years later and I am getting back into my cab (kids happened ) I am running into this same problem again as described in the first post. if I create a <romname>.cfg it works but when I use a ctrlr file it does not. Did the fix get cut out of your code along the way?

Thanks!

Yes, the issue with neogeo in controller files was fixed. Turn on the Debug Log option, run the mame rom that's not lighting correctly and email me back the debug.ZIP file so I can take a look. Please let me know exactly which rom and buttons are not lighting correctly.

[jhabers]

arzoo, 8 years later and I am getting back into my cab (kids happened ) I am running into this same problem again as described in the first post. if I create a <romname>.cfg it works but when I use a ctrlr file it does not. Did the fix get cut out of your code along the way?

Thanks!

Yes, the issue with neogeo in controller files was fixed. Turn on the Debug Log option, run the mame rom that's not lighting correctly and email me back the debug.ZIP file so I can take a look. Please let me know exactly which rom and buttons are not lighting correctly.

Thanks, emailing to you now

[jhabers]

Just emailed to support@LEDBlinky.net