Main > Main Forum
Centipede and MAME .143
paigeoliver:
The original machine is a cabaret with a newer Happ trackball and a leaf switch fire button (just recently replaced the vertical microswitch button that was on it when it first arrived).
My setup has mame .55, mame .72, mame .106 and a really bleeding edge install that has nothing but robotron on it. The trackball is a 3" happ model with no wear. The buttons are normal happ microswitch buttons, the OS is windows xp and the PC would have passed as a fairly hot gaming PC 7 or 8 years ago.
Gatt:
I'd be willing to bet your mini-pac or trackball is failing. It's hardware related, you isolated it to the control panel. If I had to bet on a component, I'd say it's the Mini-pac going bad. If the trackball were going bad, it would likely be mechanical failure and would be consistent.
The Mini-pac OTOH, could initially appear to be ok, but as it's used whatever component is failing slowly degrades performance. I'm not familiar with that kind of board/processor design to comment more specifically on what might be failing in it, on a PC that's behavior I'd expect to see with failing memory/cache memory. Anyways, each time you stopped using it as input, or switched it to another system, it initially works/improves but then degrades. Replace the Mini-pac IMO.
Edit: Actuallly, double check me, play marble madness for a bit. If you see the same behavior, replace the mini-pac. Apologies...sleepy!
boardjunkie:
Trackball has nothing to do with the fire switch. Its in the software...I can even hear the delay in the sound. If I smack the button hard enough to get a nice "crack" sound, you can hear the delay when the game produces its fire sound. Its somewhere around 60-80ms, which is quite noticable and *annoying* when play'n the game.
boardjunkie:
I keep an old .37 version around just because. I just fired C-pede up in that and...same lag.
Calamity:
Hi boardjunkie,
Are you using any sort of vsync (-syncrefresh, -triplebuffer, etc.)?