is that also necessary for maximus arcade and auto mapping?
According to the notes for MA v 2.10b7
- Added support for LEDWiz & LEDBlinky 3.7.3
- Added LEDWiz tab within Configuration tab
- If animation file '%name.lwax' isn't found then automatically search for game %parent then %console '.lwax' file
- Animation files will need to be built within LEDBlinkyAnimationEditor
I'm also having trouble getting LEDBlinky/Maximus Arcade to program my U360's. I'm running the latest beta of MA (2.10b7), LEDBlinky 3.7.3, and MAME 0.95. I don't have any LEDWiz/etc boards, so I checked the "No LED" button in the LEDBlinky configuration program, and asked it to map the U360.
I've got MA set to launch LEDBlinky, and by default it puts %name.lwax in the command line. Since I don't have an LEDWiz/etc, I therefore don't have any lwax files - so I'm wondering if this is the problem? I also tried it with just %name in the command line, but that also didn't seem to work. I wonder if Maximus Arcade is set up to only program U360's with LEDBlinky? Maybe I should try to launch LEDBlinky pre- and post- MAME with batch files and the rom name?
I've only been messing with MA for a week, trying to figure out if it's worth the $25. So far it seems impressive (it flawlessly launches Virtual Pinball, which is a big plus for me), but if I can't auto-map my U360's, I don't think it will be that useful. I've got Mala working with the U360 plugin, but I have lots of resolution switching problems on returning to Mala (especially from Visual Pinball) and some loss of focus problems.
Has anybody got LEDBlinky working with Maximus Arcade to program their U360's?