Hi, sure, I wrote a little manual
if you encounter problems just reply and I'll try to help - be as clear as possible - It took my friend more than half a day to make it work and to me the instructions are clear so..
but than again I'm not that much of a writer but ok , here we go...
just so you know :
It supports the maximum that one can get out of the situation and that is :
LWAX anim everywhere all the time - in game : all consoles and mame have specific colors - mame is game specific
It's beautifull to see in action without that show stopping error
and the FE is faster too because there is no more need to 'double' write the bat on each FE action.
You can not use the FE list change animation - we can only interfere just before launch and after game quit.
What and how:
------------
Maximus Arcade 2.10 and LEDBlinky_5_1_0_3um have been used during development. I don't know if it'll work in other combinations but logically I don't see why not...
Written in c++ with code::blocks and compiled with gcc
Setup:
-----
It's not difficult to setup. It just requires some attention. Follow to the letter and you'll be fine, everything has a reason.
1/you'll have to configure LB correctly - no LB no show...
2/select in ledblinky config that you'll be using another FE and set an FE active animation
3/put maximusbroker.exe and maximusbroker.ini in the LB dir, eg the same dir as the Ledblinky.exe executable.
4/for ALL emulators deselect that you'll be using ledblinky. I found that it doesn't erase everything from the MA default.ini file so remove it manually.
It's actually easier to do things directly in the ini file.(backup first if you need a fallback)
5/for all your configured emulators add the follwing (partly) CASE SENSITIVE entries - maximusbroker is very picky about spacing etc - LB is kinda picky too - follow EXACTLY as below
Quotes are necessary in the PrelaunchLoc, PostlaunchLoc, RunOnStartupLoc, RunOnExitLoc if you have spaces... bad idea spaces...
this is the relevant part of my config - CUT and PASTE and adapt it to your system in the default.ini file in the MA dir:
PostlaunchPath=short
PostlaunchState=hidden
PostlaunchArg=9 :%name//7 :%console//:3forsweep.lwax
PostlaunchLoc=G:\LEDBlinky_5_1_0_3um_Maximus\LEDBlinky\MaximusBroker.exe
PrelaunchPath=short
PrelaunchState=hidden
PrelaunchArg=7 :%console//9 :%name//3 :%name
PrelaunchLoc=G:\LEDBlinky_5_1_0_3um_Maximus\LEDBlinky\MaximusBroker.exe
and also
Postlaunch=1
Prelaunch=1
next put this in the MA default.ini under [General]
RunOnStartupState=hidden
RunOnStartupArg=1//7 :MAME
RunOnStartupLoc=G:\LEDBlinky_5_1_0_3um_Maximus\LEDBlinky\MaximusBroker.exe
RunOnExitState=hidden
RunOnExitArg=2
RunOnExitLoc=G:\LEDBlinky_5_1_0_3um_Maximus\LEDBlinky\MaximusBroker.exe
MaximusBroker.ini allows you to switch logging on and off allowing you to see what's happening in combination with the verbose LB logging
ttwms is the time in milliseconds between each command 250 should be fine - too low and commands get out of sync in the LB buffer causing it it to cease functioning. (eg no leds)
at most 3 commands are needed each time so execution time is below 1 second.
bugs:
----
none that I know. I did notice I got no leds when starting a new emulator when it should display the std unknown leds but a second time it functions and continues to do so
It's not every day I add one so that shouldn't be a problem?
remark:
------
On starting LB takes 20 to 30 seconds on my system to prepare everything for Mame. If you happen to start a game before that's complete LB will buffer your request until it's ready.
It'll show the correct colours later on. This only happens once and it's normal behaviour.
It could be enhanced in a number of ways but I think it's fine as it is now...after all - people pursuing cabs and emulators are used to something no?
rgds