MAMEWorld Forums - Ultimarc - Issues with Mame and Aimtraks

I have 2 Aimtraks. They work fine in windows. They work fine in other emulators. They work fine in mame with trigger and not when a red button is set to anything.

My config:

Trigger left mouse trig.
Red button right mouse.
Off screen trig right mouse.

When you go into mame it sets the gun x and y axis fine. When you set the buttons it sets both buttons as gun button 0. For instance if you set player 1 button 1 in mame to the trigger it shows as button 0. If you set player 1 button 2 to the red button it sets it as gun button 0. I know it sees the buttons as separate, well at least I think if you set player 1 button 1 to the trigger and red button it will show 2 separate entries for gun button 0. With both of them showing up 2 button games don't work right you shoot and reload at the same time.

What I have done:
- Tested with either gun same result.
- Tested different gun ids in aimtrack utility, same result.
- setting make cfg for the game manually setting player 1 button 2 to guncode button 1 instead of 0. This results in the red button doing nothing which seems logical as mame is pickup both buttons as button 0.
- reinstalling the devices via remove all usb related things from device manager, unplug plug back in.
- tested Controller Remap Utility on arcade controls site however this did not help as mame detects the buttons as gun button 0 setting the buttons to another button wont help as mame doesn't detect the gun button 1.
- tested mame 153
- tested mame 152

Now sometimes it will work and will work just on that session(as long as mame is running) so I know mame can detect it properly. I do not move the USB devices around nor does this computer get rebooted except on a rare occasion(and I have tested rebooting). Any help would be appreciated as I have been struggling with this for days. I thought it was the custom build of mame however it does this on any build of mame I use (currently just using the one off mamedev).

The issue appears to only be related to mame. I tested turning error logging on in mame and see a bunch of GUN R entries and do not know if that is the issue. I also tested debugging in mame however that seemed more for CPU than for inputs.