MAME trackball not working. mame.ini has mouse 1, trackball_device mouse

[Nocturnaloner]

The trackball is plugged in (to the PS/2 port) and working as a mouse in Windows.  It works in the mame64 (169) ui.  It doesn't work in any games, and none of them have .cfg files that would disable it.  As I mentioned, mame.ini has the lines 'mouse 1', 'trackball_device mouse' in it.  What else should I check?

[BadMouth]

When you try to map the controls in-game (TAB) what happens?

Is multimouse enabled?
If so, MAME will be looking for a specific mouse device.  So if your mouse shows up as Mouse1 and your trackball shows up as Mouse2, then only the one that is mapped in the game will work.
Even if this is enabled, you should be able to remap it in-game without any issue.

The last thing I can think of is that sometimes these UI builds have a different ini file of their own.
IIRC, back in the day I had an issue with this and MAMEPlus.  It was using a different mame.ini file located in a subfolder somewhere.
Look for the option in the drop down menus of MAMEUI to enable the mouse there.

[Nocturnaloner]

When you try to map the controls in-game (TAB) what happens?

Is multimouse enabled?
If so, MAME will be looking for a specific mouse device.  So if your mouse shows up as Mouse1 and your trackball shows up as Mouse2, then only the one that is mapped in the game will work.
Even if this is enabled, you should be able to remap it in-game without any issue.

The last thing I can think of is that sometimes these UI builds have a different ini file of their own.
IIRC, back in the day I had an issue with this and MAMEPlus.  It was using a different mame.ini file located in a subfolder somewhere.
Look for the option in the drop down menus of MAMEUI to enable the mouse there.

Multimouse is enabled, assuming that the correct location for the ini file is /ini/mame.ini.

When I try to map the controls in game, I can use the mouse to move up and down in the ui, but if I try to map anything to it, it doesn't register the mouse movement.  I have the trackball as a mouse in windows, and a spinner control connected via USB.  It moves the Windows mouse cursor horizontally, but also can't be mapped in MAME.  I am using mame64.exe as my MAME executable in Hyperspin, but I also have a mameui exe in the same folder for testing.  Mouse is enabled in that dropdown, but it has no effect, the mouse still doesn't work in games.

[BadMouth]

Multimouse is enabled, assuming that the correct location for the ini file is /ini/mame.ini.

mame.ini should be in the same folder as mame64.exe, not in the ini subfolder.

[haynor666]

It will work also if mame.ini is in ini folder.

[Nocturnaloner]

I've tried it in root, and in /ini, and still no go.

My only theory at this point is that I have some unknown device installed as mouse1.

I have ControllerRemap.  The problem is, I have no idea which installed device in Windows is my trackball, and which one is my spinner.  How can I determine this?

[haynor666]

Do You have trackball and spinner connected to one PCB? It was bought from GroovyGameGear ?

[Nocturnaloner]

Do You have trackball and spinner connected to one PCB? It was bought from GroovyGameGear ?

No, it's basically a hacked mouse.

[Nocturnaloner]

I have learned which Windows hardware IDs correspond with my physical devices, for what it's worth.  I tried using ControllerRemap to set my default controls, but so far running that with the -ctrlr flag just crashes MAME, and adding -log just generates an empty log file.

If I double-click and run mame64.exe, I can get the UI to recognize the trackball and spinner.  If I run any games, they all go to windowed mode, and the mouse cursor moves over the window, and neither my trackball or spinner are recognized when I try to configure them in specific games.

[Nocturnaloner]

Ok, I got the mouse devices recognized by starting with a fresh MAME directory, and using the regular 168 .exe.  Up to this point, I've been trying to use a couple variations of the ' x64 No Nag+Direct Input+Hi Score' versions from the Hyperspin forum.  So either one of the configuration files or the executables had issues with my system.  Wasted far too much time on this one!

[Nocturnaloner]

What seems to have happened is that vertical.ini and horizontal.ini in the /ini folder took precedence over mame.ini, and those had incorrect control settings.