|
Controller Input Not Always Recognized
#384157 - 11/02/19 11:43 PM
|
|
|
Hello, everyone.
I have MAME32 .84u2, Windows 10 Pro 64-bit, Sabrent 12-button Joypad.
I tried running it a week ago, and under the Tab menu, I'm unable to use the joypad to customize commands for the games, nor does the keyboard respond. I simply can't select anything on the menu. The "5" works for credit input and "1" works as start, but I cannot select characters or move. Oddly, MAME does recognize button input from the controller during the "Press any key to continue" intro screen. I have joypad input and mouse input both selected.
Previously, I was able to use both the keyboard and the joypad to set up games without problems. This was last June on my laptop. Everything was transferred directly over to my new desktop PC, and MAME on the laptop still works perfectly with this controller. The one difference was that I used the controller for Steam games on the desktop PC prior to playing MAME, though I believe I have eliminated the Steam controller profile.
On the off chance it's a system issue, I am having some problems with configuration on SNES9X and Fusion.
Thank you in advance for any help with this issue.
|
|
|
|
Re: Controller Input Not Always Recognized
[Re: Lycanthrokeith]
#384165 - 11/03/19 12:14 PM
|
|
|
You're running a MAME version from 11 July 2004 on a modern OS. That's a 15 year old piece of software, that was never tested in such an environment.
Fusion and Snes9X are just as old, and could also have compatibility issues running on an OS much newer than they are.
In terms of MAME tho you simply can't expect support on software that old (1 year at tops) The underlying code for the inputs has been rewritten a number of times in that period, and the emulation in such an old version will be atrocious anyway.
> Hello, everyone.
>
> I have MAME32 .84u2, Windows 10 Pro 64-bit, Sabrent 12-button Joypad.
>
> I tried running it a week ago, and under the Tab menu, I'm unable to use the joypad
> to customize commands for the games, nor does the keyboard respond. I simply can't
> select anything on the menu. The "5" works for credit input and "1" works as start,
> but I cannot select characters or move. Oddly, MAME does recognize button input from
> the controller during the "Press any key to continue" intro screen. I have joypad
> input and mouse input both selected.
>
> Previously, I was able to use both the keyboard and the joypad to set up games
> without problems. This was last June on my laptop. Everything was transferred
> directly over to my new desktop PC, and MAME on the laptop still works perfectly with
> this controller. The one difference was that I used the controller for Steam games on
> the desktop PC prior to playing MAME, though I believe I have eliminated the Steam
> controller profile.
>
> On the off chance it's a system issue, I am having some problems with configuration
> on SNES9X and Fusion.
>
> Thank you in advance for any help with this issue.
|
|
|
|
Re: Controller Input Not Always Recognized
[Re: Haze]
#384173 - 11/04/19 09:12 AM
|
|
|
I actually ended up fixing the issue. On the emulator that still functions just fine on Windows 10, as it has for years. Hence no need to change it.
But hey, thanks for taking the time to berate me.
|
|
|
|
Re: Controller Input Not Always Recognized
[Re: Lycanthrokeith]
#384178 - 11/05/19 01:56 AM
|
|
|
> I actually ended up fixing the issue. On the emulator that still functions just fine
> on Windows 10, as it has for years. Hence no need to change it.
>
> But hey, thanks for taking the time to berate me.
You're the one who came here asking about 15 year old software.
I'm not sure exactly what you expected? It was an unreasonable support request to put it politely. We're hobbyists, you wouldn't even get support for that long on premium paid commercial software. You got the correct answer, that part of the code has changed so much in those 15 years it's unreasonable to expect anybody to know.
Also, I'd be hard pressed to say that version works fine, I can't think of a single thing it runs where the emulation hasn't been massively improved since then, it's worse than the versions people are running on Pis etc. and those are tragic.
|
|
|
| Dullaron |
|
Diablo III - Dunard #1884
|
|
|
|
|
Reged: 07/22/05
|
|
Posts: 6118
|
|
Loc: Fort Worth, Tx
|
|
|
|
Send PM
|
|
|
Try out the newer MAME version. You missing out so many newer stuff.
[Re: Lycanthrokeith]
#384545 - 12/07/19 02:19 AM
|
|
|
https://www.mamedev.org/release.php
I can't believe you haven't got the latest version.
Also why are you posting here and not at the EmuChat? You asked for help on MAME. What I'm saying is you don't need help getting new stuff for a cabinet or what ever.
|
W11 Home 64-bit + Nobara OS / AMD Radeon RX 5700 XT / AMD Ryzen 7 3700X 8-Core 3.59 GHz / RAM 64 GB
|
|
|
Re: Controller Input Not Always Recognized
[Re: Lycanthrokeith]
#384878 - 01/01/20 05:30 AM
|
|
|
> Hello, everyone.
>
> I have MAME32 .84u2, Windows 10 Pro 64-bit, Sabrent 12-button Joypad.
>
> I tried running it a week ago, and under the Tab menu, I'm unable to use the joypad
> to customize commands for the games, nor does the keyboard respond. I simply can't
> select anything on the menu. The "5" works for credit input and "1" works as start,
> but I cannot select characters or move. Oddly, MAME does recognize button input from
> the controller during the "Press any key to continue" intro screen. I have joypad
> input and mouse input both selected.
>
> Previously, I was able to use both the keyboard and the joypad to set up games
> without problems. This was last June on my laptop. Everything was transferred
> directly over to my new desktop PC, and MAME on the laptop still works perfectly with
> this controller. The one difference was that I used the controller for Steam games on
> the desktop PC prior to playing MAME, though I believe I have eliminated the Steam
> controller profile.
>
> On the off chance it's a system issue, I am having some problems with configuration
> on SNES9X and Fusion.
>
> Thank you in advance for any help with this issue.
Ignoring the MAME version for now, is the controller being disconnected? MAME always hates it when hardware randomly vanishes (I had it happen when my USB keyboard fell out after switching speakers from my amp to quieter desktop speakers).
The controllers not responding could even be a DirectInput issue, since that's what MAME and most likely the other equally-old emulators used to use for game controllers back in the day (Windows 10 is probably using Xinput by default which the old emulators most likely don't support).
As for MAME 0.82, there really is no reason to keep running it on anything newer than a Pentium 4 (even if it is a case of simply keeping the old emulators with the old ROMs without having to re-download them for the newer emulators).
Unless you're only interested in the same set of games that happen to run in 0.82u2, you're missing out on literally hundreds of games which have been properly emulated, added, redumped (replacing the bad ROM dumps) and/or promoted to working. Additionally, running a 32-bit version of MAME on a 64-bit system is kind of pointless, it's like running 16-bit Windows 3.1 programs on Windows XP when the install CD (or floppy disk, remember those?) also offered 32-bit versions of the exact same program.
Some examples of what's changed since 0.82:
Raiden 2 and DX working (along with other protected Seibu games), protected Gaelco games working (Seibu and Gaelco were both deemed "The Impossible" back then), Toaplan games with working sound, Bubble Bobble AI working properly instead of using guesswork (Taito C-Chips dumped and emulated), CPS2 emulation not needing XOR files, Tekken Tag Tournament working (as well as Tekken 1/2/3 of course), Namco System 22 working (and without sound hacks that required substituting a Prop Cycle ROM to get it to work) and not needing theoretical 10 GHz CPUs etc.
|
|
|
|
Index 
Threaded 
Controller Input Not Always Recognized
Reply
[Re: 
