Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: u360 issue in mame .107  (Read 1394 times)

0 Members and 1 Guest are viewing this topic.

emerica

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 219
  • Last login:September 18, 2024, 09:27:07 pm
  • Goodtimes!
    • My ongoing projects
u360 issue in mame .107
« on: August 19, 2009, 07:55:04 am »
hello all,

I searched but couldn't find a solution. My problem is that I am using an older variation of mame and I am having trouble with my u360. It seems when I start a spinner and or trackball game, there is conflict with the stick. If I go under mame settings to change the dial device or whatever, the trackball or mouse is not being recognized if I spin them. The joystick however will allow a change in settings.  :banghead:

I used a newer version of mame, .119 I believe, for a awhile with the u360 but decided to go back to .107 to get mame runner a bit quicker on my celeron machine.
I saw the best minds of my generation destroyed by madness, starving hysterical.

fatfingers

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 966
  • Last login:April 17, 2025, 05:26:08 pm
  • Got UltraStiks?™
Re: u360 issue in mame .107
« Reply #1 on: August 20, 2009, 06:17:28 am »

I have your combination of controls working just fine with MAME 106.  Are you certain you enabled mouse support in the mame configuration file?  mouse 1, I believe it is?

My DK low scores
-------------------
1) 180700
2) 165000
3) 162900
4) 162600
5) 158500


W.W.P.M.D.?                                       I'm here to help ... I just don't do it. ™

emerica

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 219
  • Last login:September 18, 2024, 09:27:07 pm
  • Goodtimes!
    • My ongoing projects
Re: u360 issue in mame .107
« Reply #2 on: August 20, 2009, 07:11:14 am »
mouse is enabled in the config file, although it only says "mouse" not "mouse1" or " mouse2", etc. Perhaps that is the distinction that I am missing. But I do remember being able to start a game, hit taab, go into controls for this game, and spin the spinner or trackball for its specific control. Now when I do that, only the u360 gets recognized and not the trackball or mouse. The control will say " joy 1 x axis or mouse x axis" <-- not word for word. Then when I enter a control I can't get the spinner or trackball to show up. Hope this this sense. I'll post my config if you need.

I had this version of mame working awhile back with a spinner (mouse hack) and a trackball. I had it backed up on an external drive and decided to go back to it. I never had an issue until I put the u360. Not sure if mame is seeing my u360 as a mouse as well.
I saw the best minds of my generation destroyed by madness, starving hysterical.

gatordad

  • Trade Count: (+11)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 828
  • Last login:July 13, 2025, 02:34:26 pm
  • This is your brain on games.
Re: u360 issue in mame .107
« Reply #3 on: August 20, 2009, 09:18:30 am »
Is this for every game or just a few?
Based on your comments, I have a hunch that you accidentally programed your u360's as the control device in the mame settings.

fatfingers

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 966
  • Last login:April 17, 2025, 05:26:08 pm
  • Got UltraStiks?™
Re: u360 issue in mame .107
« Reply #4 on: August 20, 2009, 09:56:02 am »

mouse is enabled in the config file, although it only says "mouse" not "mouse1" or " mouse2", etc. Perhaps that is the distinction that I am missing.

I'm pretty certain it needs to say 'mouse 1'.

My DK low scores
-------------------
1) 180700
2) 165000
3) 162900
4) 162600
5) 158500


W.W.P.M.D.?                                       I'm here to help ... I just don't do it. ™

emerica

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 219
  • Last login:September 18, 2024, 09:27:07 pm
  • Goodtimes!
    • My ongoing projects
Re: u360 issue in mame .107
« Reply #5 on: August 21, 2009, 08:08:40 am »

mouse is enabled in the config file, although it only says "mouse" not "mouse1" or " mouse2", etc. Perhaps that is the distinction that I am missing.

I'm pretty certain it needs to say 'mouse 1'.



after going through it again, I realized it does say mouse 1.
Is this for every game or just a few?
Based on your comments, I have a hunch that you accidentally programed your u360's as the control device in the mame settings.


Not sure what you mean by this. I have joystick enabled in the mame config. I am going to delete my config file and make a new one. There is probably something that I am missing. Besides speed, I also switched back to play tempest, for some reason tempest doesn't work for me in newer versions of mame even though maws doesn't show any changes that would prohibit me from playing the game.
I saw the best minds of my generation destroyed by madness, starving hysterical.

u_rebelscum

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 3633
  • Last login:April 21, 2010, 03:06:26 pm
  • You rebel scum
    • Mame:Analog+
Re: u360 issue in mame .107
« Reply #6 on: August 21, 2009, 04:47:26 pm »
What you're seeing has been a common issue.  The way mame is set up is that joystickk data overrides mouse data (assuming both are mapped to the same input).  This isn't much of an issue for 4/8-way digital sticks.  But with analog joysticks with no deadzone, if the joystick is just off from center, mame uses the joystick data instead of the mouse data.

So there are a bunch of ways to fix this.  They include:
a) disable joystick in mouse input games
b) remap the inputs so the mouse is mapped but NOT the joystick
c) increase the deadzone settings in mame
d) remap the u360 so it has a bigger deadzone

I prefer b), which seems you've tried.  Hmm, are you remapping in "Input (general)" or "Input (this game)"?  Which input names are you remapping?  (should be mapping mouse to TB/dail analog, and unmapping the joystick from the same + TB/dial inc/dec)

For testing reasons, disable joysticks and see if it work and if you can remap the mouse. And enable verbose mode so you'll get more info displayed at the command line.

If the mouse works for, say, arkanoid, but you still can't remap, you might be trying to remap to a digital port instead of the analog one.  If it doesn't work in mame but does in windows, you could have multiple mice installed (IIRC that was when you were forced to use each mouse seperately), or have mouse disabled in sub ini files (usually in the ini folder).  If it does work in mame and remaps, remap with joysticks disabled in Input (general so you do it only once, and then reable joysticks.
Robin
Knowledge is Power