| Main > Main Forum |
| Argh!! Control panel is wrecking my head - two stupid problems... |
| << < (3/3) |
| u_rebelscum:
--- Quote from: nickf21 on June 03, 2008, 08:30:29 am ---as for the trackball - still a bit confused here. i do have a regular mouse plugged in. would this cause that weird conflict in MAME32 where the trackball works in the menu (and in windows) but not "in-game" if i use the in tab menu during a game and try to change the "this game settings" i cant seem to get my trackball to register. --- End quote --- Which version of mameUI (used to be called mame32) are you using? Note that mameUI is just normal mame with a GUI FE attached. As coded, a mouse or joystick working in the GUI to select games has absolutely nothing to do with a mouse or joystick working during the emulation of a game. The mouse needs to be enabled to work in the emulation part. Do as Portnoy instructed, and see if that helps. And as st said, check if the normal mouse works (for a few versions, multiple mouse was hardcoded on, which is why I asked what version you're using). |
| surface tension:
--- Quote from: u_rebelscum --- (for a few versions, multiple mouse was hardcoded on, which is why I asked what version you're using). --- End quote --- Can you give me some more info on this please? Like when it was hardcoded, then when it became selectable. Or point me in the right direction. Thanks |
| u_rebelscum:
--- Quote from: st on June 03, 2008, 03:35:14 pm --- --- Quote from: u_rebelscum ---for a few versions, multiple mouse was hardcoded on --- End quote --- Can you give me some more info on this please? Like when it was hardcoded, then when it became selectable. Or point me in the right direction. --- End quote --- When mame changed from DirectInput to RawInput for the mouse, no previsions were made for lots-o-mice-to-act-as-one-mouse to continue, as the change was done to add support for multiple mice to control different players to winXP. (0.104u5) IIRC, the thought was you could still remap to "use any mouse", and adding commandline options were discouraged. The -multimouse and -multikeyboard options were added starting with 0.117u1. I think the thought was too many people complained about the "mouse not working" with the above setting, even though it was working just not acting like the windows pointer cursor does. (Now the problem is that people enable this option when they don't want to.) So... from 0.117u1 and and on, we've had -multimouse option defaulting to off. Disabled acts like the pointer cursor does in windows desk top with multiple mice plugged into the computer: all mice control the same pointer/player, and the app cannot tell which physical the info is coming from. Enabled, mame can see each mouse separately, so you can do things like play 2 player marble madness. Between 0.104u5 & 0.117 (inclusive), mame acted as if the option was "hardcoded enabled", even though there never was (yet) an option to hardcode in the first place. Mouse 1 controlled player 1, mouse 2 did player 2, etc by default. To map so any mouse could control P1, you could remap player 1 TB to mouse 1 or mouse 2 or mouse 3 etc, but people didn't like this or had problems remapping. Ending with 0.104u4, mame acted as if the option was "hardcoded disabled", even though there never was (yet) an option to hardcode in the first place. (Win9x was a different story, as it acted as if -multimouse was both enabled and disabled for a long time before 0.104u5, but I won't waste space unless you want me to go into it.) |
| surface tension:
I couldn't have asked for a better explanation! I'm running 0.116, so I'm just outside of the multimouse-selectable threshold. I'm not entirely happy with the way it works, so I'm going to try a slightly later version. Thanks rebel :) |
| Navigation |
| Message Index |
| Previous page |