Main > Main Forum
Calling all controller experts... (strange MAME mouse issues)
Shoegazer:
Bizarre, this:
I've been getting a strange problem lately since I've installed my two LCD Topguns, though I don't think it's related to them since it's happening with my trackball mouse buttons as well...
Whenever I'm in MAME's control configuration screen, I select a button, and then push either the LCD TopGun button mapped as "button 3" or right-most trackball mouse button). On the screen I get:
Mouse 5 button 3 Mouse 5 button 4
...where I *should* get:
Mouse 5 button 3
I realize there is a feature in MAME where if you click a button, push enter, and then click a button again, you can map multiple buttons to the same function - but I'm not pushing enter at all here! I can also start from scratch (i.e. the controller button is initially mapped as "None") but I get the same result as above. I know it isn't a faulty button since it happens with both of the Topguns AND the trackball buttons. Using XP SP2 and MAME32 .112 full.
Thanks,
Shoegazer
Shoegazer:
Still having the same issues after several days of tinkering... curious if anyone may know more about this.
u_rebelscum:
--- Quote from: Shoegazer on February 02, 2007, 01:02:48 pm ---I've been getting a strange problem lately since I've installed my two LCD Topguns, though I don't think it's related to them since it's happening with my trackball mouse buttons as well...
Whenever I'm in MAME's control configuration screen, I select a button, and then push either the LCD TopGun button mapped as "button 3" or right-most trackball mouse button). On the screen I get:
Mouse 5 button 3 Mouse 5 button 4
...where I *should* get:
Mouse 5 button 3
I realize there is a feature in MAME where if you click a button, push enter, and then click a button again, you can map multiple buttons to the same function - but I'm not pushing enter at all here!
--- End quote ---
The feature you describe is for 'OR' inputs. What's happening is the 'AND' feature. If you press enter then more than one button at a time, mame takes it as you have to push those buttons at the same time for that input to register as "pressed". IOW, "Mouse 5 button 3 Mouse 5 button 4" means you have to press both "button 3" & "button 4" on mouse 5. (More info at MameFAQ h03, near middle of answer.)
I had something like what you have on one of my systems, too. At the time I was guessing it had to do with (conflicting?) mouse drivers & some (incompatible?) mouse devices (a Topgun IIRC). Anyway, my "fix" was to hand edit the cfg file in a text editor and remove the not wanted button. IIRC, the buttons worked even without the "fix", but I liked the cleaner look. Do yours work on you system as is?
Shoegazer:
Regards, Robin:
Thanks for getting back to me. You are absolutely right - it's an "AND" feature in action, rather than "OR". I was trying to remember what might cause this under normal conditions while posting, and I just remembered wrong. Thanks for the clarification.
No doubt you are right about conflicting drivers as well, though it is a little strange that it *once* worked, even after I had the LCD Topguns and trackball installed, and now it doesn't. Anyway, regarding your manual fix I'm assuming you mean MAME's cfg file, correct? It looks like I may need to do this as well. The buttons do not work when they are mapped in this strange way - for example, in "Operation Wolf" the grenade, for which I'd like to use button 3, simply doesn't work since it's mapped as "Mouse 5 button 3 Mouse 5 button 4". I have to map it to some other button on the gun before it'll register, and fire.
Stranger still - I'm using Smog's "Guncon" drivers, and the button registers just fine with his "Guncon2Mouse" application (i.e. the on-screen button 3 turns red when you press the real button 3). If you've used his app, you know what I mean. From this information, I deduced that this is a MAME issue, but maybe I'm wrong. As you now know, it wouldn't be the first time. ;)
Thanks much for your help.
Shoegazer
ahofle:
I've seen similar strangeness when you try mapping your inputs with the game paused. Unpausing usually allows the actual key presses to be mapped correctly. Why is that anyway?
Navigation
[0] Message Index
[#] Next page
Go to full version