Build Your Own Arcade Controls Forum
Main => Main Forum => Topic started by: Afterburner on December 31, 2011, 10:53:39 am
-
This has been driving me nuts and I see that others have had the same problem, but I've not found anyone that posted how they fixed it, if indeed they did.
I'll start with a simple game....Lunar Lander. Controls are a rotate left button and a rotate right button. No problem..those work fine with pretty much any control I wish to assign to them.
The problem is with the thrust. The game expects this to be an analog (Pedal) input.
In past versions of MAME I've simply mapped this control to a button (Pedal 1 Analog Inc = Mouse1B0) and it worked fine. I did this for pretty much any game that needed a pedal input.
I'm using MameUI32 0.144u3 and I absolutely for the life of me cannot get it to allow me to configure the pedal to anything other than the following:
P1 Pedal1 Analog = n/a
P1 Pedal1 Analog Dec = Mouse0B1 or Mouse X or Mouse Y
P1 Pedal1 Analog Inc = Ctrl
It does not matter which of those three inputs I attempt to change, it always reverts back to what is shown above. I don't get it.
I obviously have mouse input enabled. I have tried configuring pedal input for both Mouse and Keyboard. Same result no matter which one I select.
If I push the Ctrl key on the keyboard, I get the behavior I expect in the game. Problem is, I apparently can't map that control to anything other than the Ctrl key.
Is there an INI file somewhere that I can manually force this for this particular game?
-
Still no replies?
In addition to the above issue, I found a similar one last night.
I plugged in my USB analog flight stick (Saitek). I calibrated it under windows and then fired up Tron.
I previously had the trackball set up to be the dial. But I noticed anytime I made an input on the flight stick X axis I got dial movement in the game.
When I looked, sure enough the analog dial was set to Mouse 0 X Axis or Joystick 0 X Axis. So I cleared the selection. But anytime I try to set it to the mouse only, it goes back to both mouse and joystick.
I can't seem to make it accept mouse only input for the dial. What are some things I can check to find what is causing this?
-
In the Mame options can't you turn off the options for analogue control?
-
I'm not sure? If so, that might be part of the problem.
In fact it may explain both problems. Lunar lander wants an analog and I'm trying to assign a digital.
In Tron I was using the rotary action on my joystick to turn the arm and it worked fine. But now I want to assign an actual analog control and it seems like it won't let me.
Is there such a setting?
-
Did some additional testing. Thought maybe this might be a quirk of mameui32. So I downloaded the command line mame 0.144u4 and gave it a try.
I get a slightly different, but similar result.
I can assign my analog joystick as the analog device. I can assign just about any keyboard key or joystick button to the Pedal Inc or Pedal Dec. All of those assign and behave as I would expect.
I cannot assign the mouse as the Pedal 1 analog, and I cannot assign any mouse buttons to the Pedal 1 Inc or Pedal 1 Dec. It is as if that particular game refuses to recognize the mouse as an input device.
If I run:
mame llander -verbose
I get the following output, so it would appear it is detecting both USB trackballs and the analog joystick correctly.
RawInput: APIs detected
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Mouse #1: HID-compliant mouse
Input: Adding Gun #1: HID-compliant mouse
Input: Adding Kbd #0: Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
DirectInput: Using DirectInput 7
Input: Adding Joy #0: Saitek ST90 USB Stick
What am I doing wrong here that I can't get this to work?
-
I think I have finally determined this is a quirk/bug in Mame32ui build.
I was able to get this working correctly in the command line version of mame 0.144u4.
I even took the command line version of mame.ini that was working properly and copied it over to the mame32 ini folder. Same result, so it seems like it has to be a bug in Mame32ui.