Tribe Fan Posted January 6, 2016 Posted January 6, 2016 This is a weird problem I've never encountered before. Since upgrading to oldhag270's no nag .168, MAME will only accept inputs from my primary, connected keyboard. Xpadder inputs do not register. Is there a configuration file I can edit to enable inputs from any connected device? Thanks.
Metalzoic Posted January 6, 2016 Posted January 6, 2016 This dude having same issue. Maybe post there too. http://www.hyperspin-fe.com/topic/13882-hyperspin-keyboard-2-input-issue-skipping-over-games-in-menu
Tribe Fan Posted January 6, 2016 Author Posted January 6, 2016 His issue seems to be with the HyperSpin interface. Mine is specifically with MAME. Very strange problem. If I use the USB keyboard connected to the PC, MAME registers the inputs perfectly fine. As soon as I use my controller mapped with xpadder, though, MAME is completely unresponsive. Also, if I access the computer remotely, the remote keyboard doesn't work either. MAME only seems to respond to the primary connected keyboard. I tried changing multikeyboard in MAME.ini from 0 to 1, but that did not garner any results. Very odd. Any ideas?
Metalzoic Posted January 6, 2016 Posted January 6, 2016 Afraid not man. I use an iPac keyboard encoder so I've never needed to use Xpadder for anything. Someone else will probably have an idea though.
Tribe Fan Posted January 6, 2016 Author Posted January 6, 2016 Someday I'll join the cab builder ranks. For now I'm an HTPC guy. For most systems, MAME included, I configure controls directly within the emu. I like to use Xpadder for secondary controls such a saves states, number pads, coins, etc. Xpadder has a cool set selection feature where a button can act as a kind of shift key enabling you to map secondary inputs for all your buttons. This way I won't inadvertently load a state or use up all my buttons for number pad inputs. Vanilla MAME isn't having this keyboard issue by the way. Seems to only be happening with oldhag270's compiled MAME.
Spawk Posted January 6, 2016 Posted January 6, 2016 I am just a controller (xbox360, ps3) type guy too, I also do most configs in emu's. I use joytokey (same as xpadder) for some odd stuff like you, most important of which is to be able to exit the emulator with the controller (not having to reach for the esc key). Keymappers don't create another keyboard or anything, they just send keystrokes. I doubt it's the keymapper especially if it is working in vanilla mame. I would try a different build. Perhaps oldhag's didn't have directinput enabled??? Not sure but I would start with that.
Tribe Fan Posted January 6, 2016 Author Posted January 6, 2016 Thanks a lot for the help. It is the direct input version, but I'm not sure whether or not it's enabled. Is it possible to enable/disable it? Thanks again.
oldhag270 Posted January 6, 2016 Posted January 6, 2016 Try using the regular version of MAME , I'm wondering if they removed Direct Input support.
Tribe Fan Posted January 6, 2016 Author Posted January 6, 2016 I actually just tried again with regular MAME .169 and Xpadder keystrokes are not working. Physical keyboard inputs are registering though.
oldhag270 Posted January 6, 2016 Posted January 6, 2016 Try my mameuifx version , you can turn Direct Input and Hi Score on in the Settings.
Tribe Fan Posted January 6, 2016 Author Posted January 6, 2016 Thanks a lot. I found hiscore support, but I'm not sure what I should be looking at for enabling directinput. Is it under Default Game Options>Controllers? Thanks!
oldhag270 Posted January 7, 2016 Posted January 7, 2016 Options,Default Game Options,Controllers should be what your looking for.
Tribe Fan Posted January 7, 2016 Author Posted January 7, 2016 Well, I found a solution to force directinput into any version of MAME from this forum: http://forum.arcadecontrols.com/index.php/topic,141243.msg1461776.html#msg1461776 The first poster suggests modifying some lines in MAME or MAMEUI in a hex editor, but he also provides an exe at the bottom that automates everything for you. I just threw that into the root of my MAME directory, ran it, and lo and behold, xpadder inputs are working again.
Metalzoic Posted January 8, 2016 Posted January 8, 2016 So it was because you used a version of MAME that wasn't compiled for direct input, or was it because the MAME devs changed the way direct input is implemented?
Tribe Fan Posted January 8, 2016 Author Posted January 8, 2016 I'm really not sure actually... My keyboard was registering inputs fine, but xpadder and joy2key were not. I tried several different versions of MAME (including older versions of vanilla MAME that, to my understanding, supported directinput). None of them were accepting keystrokes sent from anything other than the physical keyboard. That exe did the trick across the board. EDIT: I'm gonna try a few more vanilla versions to see if they work. EDIT: I tried vanilla MAME as far back as .143 and it didn't work. This compiled version did work though: http://neo-nebuwaks.blogspot.com/2013/06/mame-0149-nonag-hiscores-cave.html
Recommended Posts
Archived
This topic is now archived and is closed to further replies.