Main > Software Forum
LEDBlinky - Arcade LED Control software and Animation Editor - v8.2
rdenis:
Vista 64 Issues:
Just finsihed setting up a Vista 64 bit machine with Mame 122, Mala and LED Blinky 3.5. Some weird stuff happens in the 64 bit world with Blinky 3.5:
1) Microsoft Sam has been replaced with Microsoft Anna in the 64 bit OS. Microsoft Mary and David install but when you try and select them in the Other Options menu of Blinky, there is an error.
2) Speech only enables AFTER pausing a game (where you have selected the Mame in game option to speak and flash controls when pausing or entering the admin menu). Once you do this, all speech options seem to work (except I can't confirm when Mala starts as you need to go ingame and pause first....).
Weird huh? Not sure if anyone has encountered the above or if Arzoo has any suggestions. I haven't noticed any other weird issues with Vista 64 but I'll post if I do.
arzoo:
--- Quote from: rdenis on February 18, 2008, 04:22:33 pm ---Vista 64 Issues:
Just finsihed setting up a Vista 64 bit machine with Mame 122, Mala and LED Blinky 3.5. Some weird stuff happens in the 64 bit world with Blinky 3.5:
1) Microsoft Sam has been replaced with Microsoft Anna in the 64 bit OS. Microsoft Mary and David install but when you try and select them in the Other Options menu of Blinky, there is an error.
2) Speech only enables AFTER pausing a game (where you have selected the Mame in game option to speak and flash controls when pausing or entering the admin menu). Once you do this, all speech options seem to work (except I can't confirm when Mala starts as you need to go ingame and pause first....).
Weird huh? Not sure if anyone has encountered the above or if Arzoo has any suggestions. I haven't noticed any other weird issues with Vista 64 but I'll post if I do.
--- End quote ---
rdenis,
I've been working on a minor update to LEDBlinky which may solve the Vista issue. The current version of the LEDBlinky MaLa plugin works in a synchronous mode - MaLa waits for LEDBlinky to complete each event (FEStart, GameStart, ScreensaverStart, etc.). My updated version allows MaLa to run asynchronously - it's possible that this will solve the speech problem, but that's just a stab in the dark. I'll send you a pm with a link to the update.
To all LEDBlinky users,
While I'm on the subject - here's some info on this latest update. A number of people have asked for the ability to light LEDs based on the joystick configuration (8-way, 4-way, diagonal, etc.). My cp has a 49-way wired to a GP-Wiz49 for digital restriction, so I too considered adding LED's around the joystick to indicate its current mode. Adding this feature was relatively simple. I also added a feature to speak the primary controls. For example, if you start Tron it will speak and blink the button functions and then speak "Primary Control 8-way Triggerstick and Spinner".
Then I got to thinking about my need to set the GP-Wiz49 mode when each game starts. I had planned on creating a new MaLa plugin for this. But it makes no sense for a second plugin to load all the controls.dat and mame.xml data into memory when LEDBlinky already has that data. So even thought it's out-of-scope for LEDBlinky to set the digital joystick mode, I'm going to add that feature - it's literally no more than 10 lines of code beyond what I'm already doing. If it's not too difficult, I'll also add support for the Ultimarc 360. For those (most) who don't need this, the feature will be disabled by default.
One other new feature - well it's not really new - I've fixed the "Abort Speech" option which turns out to be broken in v3.5. Prior to 3.5, LEDBlinky ran in the same thread as MaLa and hence it was able to detect FE key presses so that a user could abort the control speaking/blinking by pressing any button. But with v3.5, LEDBlinky runs in its own thread and requires a new method to detect key presses. The advantage to this new design it that LEDBlinky can now also detect a key press from mame, so you can abort the control speaking/blinking when mame is paused. But don't worry, I'm only checking the key messages for the brief period when LEDBlinky is speaking and blinking - otherwise the key hook is turned off.
Coding is 90% complete and the release should be ready in a few weeks. :)
CatttDaddy:
Hey Arzoo this seems to be a great application. I just cant seem to get it to work in AtomicFE. I have followed all of the instructions in the document but I don't get anything at all. In all of the LED Blinkey apps it seems my LEDS function correctly. It seems that none of the information is getting over to Atomic FE. Can you help me at all with this?
:-\
I have run the GenLEDBlinkyInputMap.exe and completed that. All my lights work correctly in there. Then I ran the LEDBlinkyConfig.exe. All of my animation tests work fine. I do get an error when I try to test any of the speaking options "SAPI Error Speaking: OLE error 8004503a" that's is a very cool feature but all i really want are for my LEDs to respond. I'm not too concerned about the voices. Like I say every hing seems fine until I run Atomic FE. Nothing happens.... :cry:
Please Help I have been working on this for over 24 hours and cant sleep.... :banghead:
arzoo:
--- Quote from: CatttDaddy on February 19, 2008, 08:24:59 pm ---
Hey Arzoo this seems to be a great application. I just cant seem to get it to work in AtomicFE. I have followed all of the instructions in the document but I don't get anything at all. In all of the LED Blinkey apps it seems my LEDS function correctly. It seems that none of the information is getting over to Atomic FE. Can you help me at all with this?
:-\
I have run the GenLEDBlinkyInputMap.exe and completed that. All my lights work correctly in there. Then I ran the LEDBlinkyConfig.exe. All of my animation tests work fine. I do get an error when I try to test any of the speaking options "SAPI Error Speaking: OLE error 8004503a" that's is a very cool feature but all i really want are for my LEDs to respond. I'm not too concerned about the voices. Like I say every hing seems fine until I run Atomic FE. Nothing happens.... :cry:
Please Help I have been working on this for over 24 hours and cant sleep.... :banghead:
--- End quote ---
CatttDaddy - go to sleep! ;)
Then, after you wake up, run the config app and turn on the debug log (Misc Options tab). Also check the Verbose option. Run Atomic and launch a game. Then check the LEDBlinky folder and post the debug.log file back here.
arzoo:
CatttDaddy,
I just thought of something - did you activate the LEDBlinky plugin in the AtomicManager? On the General tab, check the Advanced Options box, then select the Advanced tab. Go to the Plugin's tab, and enable the LEDBlinky plugin. Hopefully this was your problem. If not, get me the debug log.
arzoo
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version