Main > Driving & Racing Cabinets
Hmm I don't think I read this schematic correctly. Steering wheel help?
dmworking247:
--- Quote from: BadMouth on November 20, 2013, 07:04:15 am ---Is mouse enabled in mame.ini?
If it is, is multimouse enabled?
If multimouse is enabled, mame will look at each mouse separately instead of the windows system mouse. So you'd have to make sure that it's mapped to the correct mouse.
The pulse count on that wheel looks crazy low.
Crank the sensitivity way up under analog settings in mame's in game menu (tab)
sent from my phone while driving
--- End quote ---
Ok investigations continue on this optipac issue. Mouse is enabled, and so is multimouse. The wheels control the windows mouse cursor successfully.
I go into mame and into the tab menu, then try to map the P1 analog paddle controk (for example). i can get any real physical mouse to register (mouse 1 x, mouse 2 x) but moving the wheel/optipac doesnt register. Its worthwhile noting that the optipac cursor movement in windows is a bit slow, so I tried turning windows cursor speed to maximum in case turning the wheel wasnt enough of a movement to pick up in mame settings... still no joy.
Yet the plot thickens... if I set multimouse to 0 (off) so that any mouse controls the same mouse/cursor, the optipac does move the cars in game (in mame) yet STILL doesnt register when using the mame tab setup menu (whereas a real mouse does).
The only possibilities I see is that the optipac isnt a 'mouse' to mame (unlikely) or these particular sensor boards from the hot rod cabinet are such low sensitivity that I simply cant get enough movement of the cursor for the mame tab menu to pick it up.
I had a quick go at editing the .cfg file of default controls manually to try and force mouse1,2,3,4 or 5 to move p1 analog but that didnt work when I turned multimouse back on. What gives?! Im getting a bit stuck. Any ideas appreciated!
PS: problem is the same in mame 106, 134, and 151b.
Sent from my GT-N7105T using Tapatalk
BadMouth:
Any way to try a wheel with more teeth?
I suspect the input system in MAME changed at some point and it doesn't register lower resolutions as well as it used to. (no idea which version)
I had some miniature 12 count per revolution encoders that I wanted to use in rotary sticks and MAME would not pick them up at all.
It would pick up the same interface with the same settings just fine if using a higher count encoder.
If multimouse is enabled, MAME is getting the input directly from the device, so adjustments in windows wouldn't make a difference.
If multimouse is turned off, MAME gets the input of the "system mouse" through windows, so those adjustments would help.
This kinda follows what you are experiencing.
dmworking247:
Thanks for the tips BadMouth, I think we are on to something with the low res encoders, although my experiments so far have already been using a high pin count encoder wheel typical of a happ trackball.
I will try dialing up the analog sensitivity in mame itself, then the next step will have to be trying a sensor board from an old trackball or mouse. It will be a pain if I have to use different encoders since I was trying to use all of the original hardware, but not impossible.
Sent from my GT-N7105T using Tapatalk
Navigation
[0] Message Index
[*] Previous page
Go to full version