Has anyone figured out how to use LEDspicer with MAME to automate which buttons are used per ROM? I have LEDspicer running but can not for the life of me figure this out.

@OneSwitch glad it worked for you too!

@GreenHawk84 - I think the vector code for mame2003 and mame2003-plus are pretty much identical now. One thing that has changed is instead of a vector resolution multiplier of 1, 2, 3, etc. it will be the actual render resolution under the Quick Menu -> Options settings. If one of the core resolutions match the native native resolution of your monitor it should like decent. If you can't match the resolution to the display exactly then shoot for something close. I find using an HD display (1920x1080) that 1440x1080 looks decent for both horizontal and vertical vector games. Try a vector beam width of 1 or 1.2 (Quick Menu -> Options) and if it still doesn't look satisfactory try turning on bi-linear filtering under Settings -> Video. Some of the options require a core restart, basically exit the game and restart it.

@hsamuels Same problem after update 1.7.5 - MAME 2003 (0.78) 95bb558 I'll open a new topic.

@wstanek Thanks, I would like to see that list. In the meantime I found out that Ultimarc's product page actually says that the SpinTrak has "1200 pulses per revolution". But if that's so, then I don't understand why the formula from my link above doesn't get the proper results. No big problem, just more work to find the right values by hand. My current approach is to try to find and setup the original rotation/movement ratio (e.g. those mentioned above for Arkanoid and Tempest), and then adjust them to my liking. APB is a good idea. At the moment, I'm collecting the games listed on my link above in two custom collections: driving games and any other spinner/paddle games. Affter that, I'll go through all of them to adjust their analogue settings and test their playability.