Controls go nuts after 30 secs with spinner or light guns

[Martin0037]

This is weird and doing my head in... I'm already going bald as it is and this isn't helping!

I'm just gonna throw this one out there...

after about 30secs or so of playing a driving game with the spinner or playing a shooting game with the aimtrack guns The car (chase hq, outrun etc) just goes nuts and does its own thing... i mean steering on its own, gas pedal on its own??? As with a light gun game,such operation thunderbolt, after about 30 secs or so the crosshair goes nuts on the screen! (I have checked the calibrate settings and it's not that)

I need to laugh at this to seriously keep my sanity or I will go insane!

My setup-
Just installed a fresh version of mame64 .171 raw input (I'm only using mame with hyperspin, nothing else)
Controls - iPac 4 for sticks etc (this is fine, no issues. A normal game runs fine with sticks
Trackball
Spinner
2 aimtrack lightguns

Everything is mapped fine, everything works great (at least for a small time)
All settings are as far as I know correct in the mame.ini file.

I have had issues with mame changing the device ids after rebooting etc but I'm told this is a problem across all mame versions and I've not found a cure for this. I had my machine set to boot mame straight away when windows starts and I think this was causing the ids to be changed as I'd not unplugged anything at all, but maybe Windows is starting mame before all devices have had a chance to start / log in if that's makes sense... might be wrong here. Have been by Andy at arcade world U.K. to try changing the mame.cfg file to read only to stop devices being changed but not tried this yet...

So other than this mame version I'm using being possibly knackered I've got no idea what is causing this to happen. I'm at the end of my build and it's been problem after problem as soon as I started trying to set guns and controls up.

What a pain in the arse!

So I'm really hoping someone might have a solution here. Failing that I'll try a different version of mame... or I might consider a crate of Guinness and a big hammer and try and fix it with that...





Ps - I used mameuifx.159 first off and it worked great... but it wouldn't recognise two guns, only both of them as gun#1 so I had to change but I never had half the issues I've had since. All the games worked perfect too... one or two in the different version I've used so far don't, or the sound is shite.

A mameuifx.159 raw input no nag version would be good - I'm told it needs to be raw input for the guns?


Thanks in advance guys

[Titchgamer]

That is indeed a curious problem!

Ime running similar hardware to you but never had those problems!

I run a no nag version of mame .168 (or 169 cant remember..)
And both AT's and spinner are fine.

But I know when I was still finishing the cab it was stored in a conservatory and when in windows the mouse pointer would go totally nuts with the AT's connected even if holstered.
I worked out in the end it was to do with the sunlight and reflective surfaces.
So do you have heavy sun light or reflective surfaces where you keep your cab?

As for the ID problem its a long running problem.
There are various apps out there to sort this problem and fix the ID's which is what i did on my set up.