Main > Main Forum
Turbo Twist 2 & Trackball won't play nice!
mybrainhurtz:
Thanks for continuing to work on this u_rebelscum. Right now, I am still running the mouse hack for my trackball. If you don't come up with a solution, next time I place an order with GGG, I will pick up an opti-wiz so I can hook things up right!
And thanks for clarifying the situation Randy. When I first had this problem about a month ago, I had trouble finding an explanation. Hopefully this will help others that are having the same sensitivity issues.
Oh, and I just want to say... I love the GP-Wiz and the TT2 now that I am able to play with them...they are both fantastic products! :)
u_rebelscum:
Okay, some info from last night:
Confirmed: TT2 Z axis sends mame too big counts, and cannot be fixed by decreasing mame sensitivity to 1%
Confirmed: the Z axis for TT2 and my kensington TB have a minimum step of 120 counts, in both RI & DI in XP.
Confirmed: mame currently does not divide for the Z axis either RawInput not DirectInput anymore (used to be / 30 starting ver. 0.110u5)
Tested: current mame works sort of okay for normal Z axis (on my mouse I tested)
Tested: if Z axis count is divided by 120, then normal mice Z axis suck (and mame sensitivity can't be set to 12000% to compensate)
Tested: if Z axis count is divided by 120, then TT2 on Z axis works great
Still have
TODO: find & test the couple mice I have that have "scaled Z axis" that might have < 120 count minimum. (true in DI & win9x, IIRC)
TODO: look at older versions of mame to see when changes were made
TODO: (maybe) dig out my 9x box and repeat tests on it
Randy, I can't remember the details of the z axis, and can't find threads on it (besides the 0.110u5 what's new). Do you have better memory or searching skillz?
RandyT:
--- Quote from: u_rebelscum on February 13, 2008, 07:09:18 pm ---Randy, I can't remember the details of the z axis, and can't find threads on it (besides the 0.110u5 what's new). Do you have better memory or searching skillz?
--- End quote ---
That's the first version with the fix. The only other info I have is from an email from Derrick Renaud, who was responsible for it. He wrote:
------
This is how the Z-axis will now work.
Windows Input changes:
Scaled Mouse Z axis by 30 to make it usable. Most mice inc/decrement by 120 for each wheel click. Some rare ones are 30. So this means for most mice, using a Sensitivity setting of 25%, you will get 1 inc/decrement for each wheel click.
I did not want to make this a MAME core change because I do not know how Linux, Macs, etc handle the Z-axis.
------
Does that help?
RandyT
u_rebelscum:
--- Quote from: RandyT on February 13, 2008, 08:37:15 pm ---...Does that help?
--- End quote ---
A little, jogged my memory some, thanks. :)
On the testing news:
I tested one of the accelerated Z axis mice, and it does non 120 steps (as I remembered, yah! ::)). However the minimum still is 120. Z axis values at my settings included: 120, 127, 140, 183, 202, 331, 364, & 448, and others higher and in bewteen but less often. (The mouse is a MS wireless laser mouse 5000 with the MS IntelliPoint driver.)
More later.
Encryptor:
--- Quote from: u_rebelscum on February 15, 2008, 07:28:27 pm ---
--- Quote from: RandyT on February 13, 2008, 08:37:15 pm ---...Does that help?
--- End quote ---
A little, jogged my memory some, thanks. :)
On the testing news:
I tested one of the accelerated Z axis mice, and it does non 120 steps (as I remembered, yah! ::)). However the minimum still is 120. Z axis values at my settings included: 120, 127, 140, 183, 202, 331, 364, & 448, and others higher and in bewteen but less often. (The mouse is a MS wireless laser mouse 5000 with the MS IntelliPoint driver.)
More later.
--- End quote ---
u_rebelscum,
I just want to say thank you very much for looking at and trying to come up with a solution to this problem. I appreciate it a great deal.
Encryptor