Main > Main Forum
ipac - laggy pushbuttons
<< < (3/3)
DNA Dan:
Assuming the issues is the "shifted" button connection, is it possible to use an older firmware version for the ipac that does not include the shift function?
AndyWarne:
Start1 is by default the shift button.

The behavior of the shift button is described on this page:

http://www.ultimarc.com/ipac3.html

If you do not want the shift button you can assign the shift button to another control or not have one at all, using WinIPAC. But it is the easiest way of achieving control functions without dedicated buttons for coin, esc, pause etc. Of course if you have dedicated buttons you dont need this feature and can easily configure it out.
Its difficult to replicate this in Mame as you usually get the primary keycode in addition to the shifted keycode. The I-PAC logic avoids the primary code from being sent if the button is being used as a shift.

Andy
Spacejack:
I had a thing for a while where some of the switches on my Ipac started registering only when released. I changed the ports around, but I recently changed them back and the problem was gone.
jtslade:
I had a similar issue but it was player one button two that was laggy..

I fixed by making sure that the ALT key (mame default) for player one button two was mapped to a letter. Stay away from all non-letter keys. Numbers of course are good as well.

I know this is not your defined problem but It can prevent further issues.
TopJimmyCooks:
Let me just say here that after figuring out the cause of the issue (which I could have RTFM and found out) I now believe that this is a good implementation of the shift key functionality.  Sending the P1 start keypress at release of the momentary switch works well.  This is the least likely control to receive repeated pounding/gameplay.  I don't currently shift anything but I'm glad to know that this is an option for the future. 
Navigation
Message Index
Previous page

Go to full version