HELP!!! Trackball registers as "Mouse 1 Z " when mapping in MAME!!!

[dochlywd]

My trackball works fine in Microsoft, but when playing Golden Tee, it doesn't function correctly. When I go into general input, player one, and choose track x analogue, it registers as Mouse 1 Z when I roll the trackball along the x-axis. It also registers as Mouse 1 Z when I roll it along the y-axis in track y analogue.  Can anyone please help me out as I have a party tomorrow and this is the last piece of the puzzle to put together so the guys can play Golden Tee.

Thanks!

Mike

[FrizzleFried]

Not sure which version of MAME you are using,  but with at least .109 - .111 the mouse is assigned simply as MOUSE 1,  MOUSE 2,  etc.   MOUSE 1 includes X and Y axis,  MOUSE 2 the same, etc.

My MOUSE is "MOUSE 1".  My TRACKBALL is "MOUSE 2".  My SPINNER is "MOUSE 3".

[Kremmit]

What are you using to interface the trackball to the PC?  Opti-Wiz, Opti-Pac, Mouse Hack, ? ? ? ?

[u_rebelscum]

Not sure which version of MAME you are using,  but with at least .109 - .111 the mouse is assigned simply as MOUSE 1,  MOUSE 2,  etc.   MOUSE 1 includes X and Y axis,  MOUSE 2 the same, etc.

I'm not sure what mame deviv you're using, but when you remap the mouse, official mame includes the axis in remaps: IE "Mouse 1 X" of you more than one mouse, or if you only have one mouse "Mouse X".  If you look at the cfg files, the same axis shows as "MOUSECODE_1_ANALOG_X".  This way you can do things like map mouse 1 Y axis to the game's player 2 X axis.

And since windows cannot tell mame if the Z axis is used or not (dang windows, again), mame has to assume all mice have three axes, X, Y & Z, to be able to use the Z axis (which mame can).  When remapping to an analog axis, mame registers the first analog axis it sees move "more than a small amount". 


Dochlywd, from what it sounds like, you have to roll the TB for mame to see "mouse 1 Z"?  Do you know the numbering of the other mice devices you have plugged in?  (If all register with "Mouse 1 Z", try testing by remapping the buttons for the devices you have with buttons and noting the numbers.)  IOW, is your TB mouse 1, or is some other mouse mouse 1?  It could be that the Z axis is also sending a signal, and mame sees it move past the threshhold before mame sees the TB's axis if the wiring is crosswired.

[dochlywd]

Thanks for the replies! It sounds like you  need a little more info. The first part of the info is that I am a newb and some of what you said went over my head but I kind of understand what you are saying.  I have two mouses: a regular mouse plugged into the USB port (which worked fine for golden tee when MOUSE 1 X and 1 Y was in there but now doesn't since my dumb-a@@ started trying to remapp ) and then my trackball is plugged into the PS2 port. Can the trackball function properly in Windows (pointer follows every movement of the trackball perfectly) and be cross wired(?) as you asked?

I am using MAME32.

Yes. I do have to roll the trackball for mame to see "mouse 1 z".

I don't know the numbering of the other mouse but I now assume it is mouse one since it worked fine with goldne tee before I remapped. I would roll the mouse back and the club would backswing. I would roll the mouse forward and the club would swing through as normal.

Last, I'm not sure what interface the trackball is using. I purchased a premade CP. But, here are a couple of pics of the underside.

Thanks again for all your help!

Mike

[Kremmit]

Your trackball is using a mouse hack:  the internal circuit board from a regular PS/2 ball-type mouse, with wires from your trackball soldered in place of the optical sensors from the mouse.  The areas circled in blue below control the X and Y axes of the mouse; it looks like all the wires are going there, although it's hard to tell for sure from that (cellphone?) pic.  The area circled in red controls the Z-axis; the Z-axis is the scroll wheel from the mouse.  Are there any wires going to that area? 

Since you get good cursor movement from the Trackball in Windows, you're probably not cross-wired.  I'm betting that the scroll wheel optical sensors are still present on the mouse and are sending out a "tick" that MAME sees before you get a chance to send it some movement from the X or Y axes by rolling the ball. 

Assuming there are no wires going to the Z-axis area:
A better pic of that area would help, but what you're looking for is a small black component with three legs soldered to the PCB- that's the optical receiver.  It'll have a smaller clear component with two legs sitting right next to it- the optical emitter.  If the encoder wheel is still present (round spin-able thing with notches cut in the rim), it'll be right between the two.  If the wheel is there, remove it, and see if your problem goes with it.  Next, try putting a piece of electrical tape around the receiver, to block any light from getting in.  If that doesn't work, then remove the receiver, either by de-soldering it, or if that spooks you, you can probably just break it off with pliers, but be really careful not to break anything else.

[dochlywd]

Sorry for not posting. I was out of town and couldn't get back to this problem. Thanks for the advice. I will try it sometime tomorrow and if it doesn't correct it, then I will get a better pic using my digital camera instead of cell phone.

Thanks again!

Mike