Main > Main Forum

How to set sensitivity for TT2 spinner and mouse in MAME32?

Pages: << < (2/3) > >>

mimic:

got it thx!

Joystick Jerk:

Speaking about these sorts of devices, what should the windows mouse sensitivity be set at when using a TT2 and Happ USB Trackball?

shorthair:


--- Quote from: Joystick Jerk on May 29, 2007, 05:58:40 am ---Speaking about these sorts of devices, what should the windows mouse sensitivity be set at when using a TT2 and Happ USB Trackball?

--- End quote ---

You generally leave them as is. And on Mame, I know there's a doc, but having been through it, it could use a rewrite and re-organisation...although, maybe they should make it so that you HAVE to read it before being able to use it.

ahofle:

There is actually a slight issue with this.  Because of the TT2's very high resolution, it will move the cursor many times faster than an arcade trackball.  So if you adjust sensitivity for the trackball, the TT2 will probably move too fast -- if you adjust for the TT2 the TB will be too slow.  If I remember correctly, leaving it as defaulted in windows is best (and then dialing down sensitivity for the spinner games in MAME for the TT2).  You could also get a trackball booster kit from GGG to give the trackball more resolution.

u_rebelscum:


--- Quote from: ahofle on May 29, 2007, 05:38:24 pm ---There is actually a slight issue with this.  Because of the TT2's very high resolution, it will move the cursor many times faster than an arcade trackball.

--- End quote ---

I wish windows would let you set each mouse's settings separately.  My laptop has four mice (desktop mouse, touch pad, travel mouse, & presetation mouse) with four different speeds (fast, slightly slow, very slow, & medium, respectively).  It's a pain changing the mouse sensitivity speed and accelaration exhancement level each time I change which mouse I use; it's not a quick switch. 
I wish the same in mame, for each axis on both mice & analog joystick devices, but since it's (remotely) possible I could fix this, I won't mention it.  Maybe the on-the-horizon input change will fix it.... ;)




Pages: << < (2/3) > >>

Go to full version