| Main > Main Forum |
| Calling all controller experts... (strange MAME mouse issues) |
| << < (2/3) > >> |
| u_rebelscum:
--- Quote from: Shoegazer on February 07, 2007, 08:56:32 pm ---Anyway, regarding your manual fix I'm assuming you mean MAME's cfg file, correct? --- End quote --- There is no single "mame's cfg file". There is the mame.ini file; there was mame.cfg back when mame was still dos based. I mean the cfg file(s) in the cfg folder. If you're remapping all games, "Input (general)", you'll want to edit default.cfg. If you're remapping a specific game, you'll edit specificgamename.cfg. --- Quote from: ahofle on February 08, 2007, 01:28:31 pm ---Unpausing usually allows the actual key presses to be mapped correctly. Why is that anyway? --- End quote --- RawInput and DirectInput (foreground mode), the two methods mame uses to read joystick, mouse & keyboard inputs, make it so either: mame sees the inputs but not other (normal) apps, or other apps but not mame. When mame is paused, mame is set up so other apps can use the mice and keyboard. If windows wasn't a multiple threaded OS, mame wouldn't need to do this, but since windows can run more than one app at a time, it makes sense (plus windows almost forces this behavior). However, this isn't what happened to me and it doesn't sound like him either. |
| Shoegazer:
--- Quote from: u_rebelscum on February 08, 2007, 06:41:31 pm --- --- Quote from: Shoegazer on February 07, 2007, 08:56:32 pm ---Anyway, regarding your manual fix I'm assuming you mean MAME's cfg file, correct? --- End quote --- There is no single "mame's cfg file". There is the mame.ini file; there was mame.cfg back when mame was still dos based. I mean the cfg file(s) in the cfg folder. If you're remapping all games, "Input (general)", you'll want to edit default.cfg. If you're remapping a specific game, you'll edit specificgamename.cfg. --- End quote --- Well that's what I meant - default.cfg. Semantics. ;) I'll try editing this file, or the overriding "opwolf.cfg" but I don't believe it's going to fix the issue. --- Quote from: u_rebelscum on February 08, 2007, 06:41:31 pm --- --- Quote from: ahofle on February 08, 2007, 01:28:31 pm ---Unpausing usually allows the actual key presses to be mapped correctly. Why is that anyway? --- End quote --- RawInput and DirectInput (foreground mode), the two methods mame uses to read joystick, mouse & keyboard inputs, make it so either: mame sees the inputs but not other (normal) apps, or other apps but not mame. When mame is paused, mame is set up so other apps can use the mice and keyboard. If windows wasn't a multiple threaded OS, mame wouldn't need to do this, but since windows can run more than one app at a time, it makes sense (plus windows almost forces this behavior). However, this isn't what happened to me and it doesn't sound like him either. --- End quote --- Hmmm.. well this DOES sound like something to try at least, couldn't hurt, though I'm with you that it's probably not the issue. Actually I have sortof found a workaround in that, using smog's Guncon2Mouse app, I simply don't map the offending mouse button to a usable button on the gun. So, given that "button 1" is what causes the problem, I just don't use it - instead I use "button 2". Now in MAME, it appears to be ok with that, even though I've lost one whole button from the list of five usable buttons Guncon2Mouse allows me to use. Of course, the trackball buttons are a different story... I'm still having issues with trackball "button 1", sadly. Shoegazer |
| Shoegazer:
...An update, of sorts. Still having problems with the third mouse button (right-click). I'm definitely leaning towards a bug in MAME - that is, when I try to register the third mouse button in MAME, it maps as "Mouse 4 button 0 Mouse 4 button 1" rather than "Mouse 4 button 0". This only started occurring when I installed my two LCD TopGuns, and it only happens in MAME. When you try right-click in Windows, everything is fine. ack. |
| Shoegazer:
Another update.. I see where the problem is, and again - pretty sure it's a mame bug, though it might be a "feature" of some sort and I'm just not clued in. All I did was uncheck "offscreen shots reload" and now mouse buttons are working properly. If someone can help me verify this, I'll submit it to MAMEtesters. Thanks, Shoegazer |
| u_rebelscum:
--- Quote from: Shoegazer on February 14, 2007, 02:19:19 pm ---Another update.. I see where the problem is, and again - pretty sure it's a mame bug, though it might be a "feature" of some sort and I'm just not clued in. All I did was uncheck "offscreen shots reload" and now mouse buttons are working properly. If someone can help me verify this, I'll submit it to MAMEtesters. --- End quote --- [smacks head] If it's due to offscreen reload, it's not a bug. If you want I can go into how mame remaps and how the offscreen reload option works, but basically -offscreen_reload steals all mouse "button 1"s (the second button) for reloading. This is hardcoded, and set at compile time. Changing this behavior is a "feature increase". Not a bad feature increase, but still not a real bug. (I've looked into changing this, but it's coded three different ways in four different places, and I don't see a clean way of setting some mouse devices to reload, some not.) Can you test some of these again? Some of your numbers support the reload cause, but other don't quite (it could be semantics though): --- Quote from: Shoegazer on February 02, 2007, 01:02:48 pm ---..either the ... button mapped as "button 3" or right-most trackball mouse button... I get: Mouse 5 button 3 Mouse 5 button 4 ...where I *should* get: Mouse 5 button 3 --- End quote --- Almost makes sense if you had enabled both -dual_lightguns & -offscreen_reload, except I'd expect the buttons to be 2 & 3, but still "should get ... 3" (assuming mouse button numbers start at 0). Unless you changed the button numbering with the driver, of course. --- Quote from: Shoegazer on February 08, 2007, 08:15:34 pm ---... I have sortof found a workaround in that, ... I simply don't map the offending mouse button to a usable button on the gun. So, given that "button 1" is what causes the problem, I just don't use it - instead I use "button 2". Now in MAME, it appears to be ok with that, even though I've lost one whole button from the list of five usable buttons Guncon2Mouse allows me to use. Of course, the trackball buttons are a different story... I'm still having issues with trackball "button 1", sadly. --- End quote --- Okay, these numbers match with what -offscreen_reload is designed to do. --- Quote from: Shoegazer on February 13, 2007, 11:57:10 pm ---Still having problems with the third mouse button (right-click). I'm definitely leaning towards a bug in MAME - that is, when I try to register the third mouse button in MAME, it maps as "Mouse 4 button 0 Mouse 4 button 1" rather than "Mouse 4 button 0". --- End quote --- Don't you mean "... rather than 'Mouse 4 button 1"? |
| Navigation |
| Message Index |
| Next page |
| Previous page |