Main > Main Forum
4 player options besides iPac
AndyWarne:
--- Quote from: rCadeGaming on May 11, 2014, 11:52:21 pm ---
OP there is nothing wrong with your IPAC. Fix the problem by setting it up properly. As mentioned by others, disable shift functions, unmap keys like CTRL, ALT, F keys, etc. Don't try just throwing money at the problem. It's wasteful, the work of installing a different encoder is totally unnecessary, and you might just add a different problem.
--- End quote ---
+1
The original choice of keys in Mame was not an ideal one but all can be changed. If you cant overcome the issues drop me an email and I will try to help.
andy@ultimarc.com
WakiMiko:
--- Quote from: AndyWarne on May 13, 2014, 06:43:46 pm ---The original choice of keys in Mame was not an ideal one but all can be changed.
--- End quote ---
This is just a guess, but the MAME developers probably chose the modifier keys (CTRL, ALT, SHIFT) as defaults in order to get around ghosting/rollover issues.
When pressing multiple "letter" keys together, most cheap keyboards will fail to recognize certain key combinations. The IPAC handles it just fine, however.
wirenut:
--- Quote from: AndyWarne on May 13, 2014, 06:43:46 pm ---
--- Quote from: rCadeGaming on May 11, 2014, 11:52:21 pm ---
OP there is nothing wrong with your IPAC. Fix the problem by setting it up properly. As mentioned by others, disable shift functions, unmap keys like CTRL, ALT, F keys, etc. Don't try just throwing money at the problem. It's wasteful, the work of installing a different encoder is totally unnecessary, and you might just add a different problem.
--- End quote ---
+1
The original choice of keys in Mame was not an ideal one but all can be changed. If you cant overcome the issues drop me an email and I will try to help.
andy@ultimarc.com
--- End quote ---
Do this. I was sure that I had a dead PAC 64 and after several emails, Andy brought it back to life! There is a reason that the Ipac is the most used encoder. Just fix it.
RandyT:
--- Quote from: rCadeGaming on May 11, 2014, 11:39:25 am ---You should be avoiding joystick encoders, they add more input lag in MAME than keyboard encoders.
--- End quote ---
This really couldn't be further from the truth. At the system level, joystick controls are given high priority, as latency is very undesirable in the applications for which they are used. Conversely, keyboard priority can be lower, as people typically can only type so fast, and low latency is far less important for keyboards. There's also the fact that the USB gaming control reports use bitmapped representations of buttons, meaning that these require far less processing at the system level, and require as much as 1/8 or less of the data required by keyboard key reports to travel over the USB bus.
However, every interface is different, and latency is very dependent on the manner in which the hardware is implemented, and the quality of the device used. Just because you found a cheap joystick controller which doesn't perform well, is no indication that all joystick encoders have those kinds of issues. It's very much the same as driving a 1982 Geo Metro, and concluding that all cars can only reach speeds of 75mph, and get 32mpg.
That being said, a properly implemented device of either type, supported by a mature OS, is just fine for gaming requirements. Especially in the case of older system emulation, where inputs are usually only read at 60hz (about 16ms). If the controller latency, combined with the system processing of those events ends up beyond that, you might notice. Otherwise, there should be few, if any, issues.
rCadeGaming:
You sure about that? That may be true in Windows, all things being equal, but not necessarily in MAME if a different API is being used for keyboards than joysticks. I'm just going off what I've heard from knowledgeable people in the GroovyMAME section.
http://forum.arcadecontrols.com/index.php/topic,133194.msg1386069.html#msg1386069
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version