arzoo

If no event identifier is specified, LEDBlinky will attemp to determine the event type by the first parameter; either a rom name or animation name (.lwax). For a rom it will default to GameStart event and for animation it will default to StartAnimation event. All other event types require the event identifier.

The correct format would be without the angle brackets. In your example, LEDBlinky would accept 236470 as the game name and windows as the emulator, and trigger the GameStart event. I'll have to check you log when I'm home and have a few minutes.

The GameStart command can optionally except both ROM and Emulator parameters. The error indicates a manual GameStart command was sent without a ROM parameter specified and without any prior GameSelected command. Hope this helps.

I'll need to see your debug log to help with this; enable the Debug Log option (Misc Options tab), run LB and a game where you've configured a color using P1_JOYSTICK_UP, then email me the debug.zip file and I'll take a look.

The LEDBlinkyInputMap is used by LEDBlinky, not LaunchBox, so I'm not sure exactly what your issue is? Are you getting a specific error message? Can you provide a bit more information?

I'm assuming you're assigning the animation as the "Game Play Animation"? If that's the case and you also have the "Light Game Controls" option enabled, then LEDBlinky will light the active game controls, overriding any LEDs used by the animation. If you only want your animation to light during game play, then uncheck the Light Game Controls option.

The trial version will work with BB and light up the specific buttons for each game.

LEDBlinky can only import from mame.

Sorry, I do not. Maybe someone else in the LB community can help with that?

Glad you got the audio mostly figured out. I'm pretty sure there are other voice packs offered for Windows TTS, but I don't think they are free for download. Sorry, it's not possible to reorder the spoken controls.

I've never heard of anything like that. Sounds like the emulator is taking control of the audio on your system somehow? Does this only happen with mame?

If you turn on the Debug Log option (Misc options tab), run a few games that don't light correctly, then email me the debug.zip and/or debug.log files and I'll take a look.

FE System Lists Names would be used for a list in LB that only contains emulators/systems (not games/roms).

LEDBlinky runs fine on Windows 11. Based on what you're describing, it sounds like BB is sending LEDBlinky multiple GameStart and Game Quit commands (not sure why but that would have something to do with your LB/BB configuration). LEDBlinky does have an option that might help; using the Controls Editor, double click the emulator and select the "Ignore GameQuit Commands" option. You could give that a try.

Maybe one of the joysticks is just malfunctioning? If you can't upload the latest firmware, I would suggest contacting Ultimarc for support.

Based on the log it looks like LEDBlinky is detecting 3 Ultrastiks, is this correct? Each U360 needs a unique ID. You may also want to make sure each U360 has the latest firmware. Also, try the UltrastickTest app and see if that correctly maps the sticks.

The I/O error is LEDBlinky trying to write a stream of messages to the log. Try turning off the Debug Log option and see if that helps.

Wow, there's so much unrelated info flying around in this thread, not even sure where to start ? @Golfboy01 The log you posted above is not the same as the one you provided me via email a few days ago. In the log above, you're using LEDBlinky without any LED controllers, but you don't have the "No LEDs Mode" option enabled, so LEDBlinky is basically doing nothing. Try again with "No LEDs Mode" checked and email me back a new debug log if the ServoStiks are still not switching based on the selected game. @kmoney I'm not sure what's going on with your U360s and LB/BB, but in some cases there is a problem with LEDBlinky reading the U360 data. I have a fix in the works, but for now you can manually edit the LEDBlinky settings.ini file (use any text editor) and set DetectJoysticks=0 under the [OtherSettings] section. @C-Beats Thanks for trying to help with this. In the log that @Golfboy01 posted I do see one instance where LB sent the GameSelected (9) command with "gryzor" as the game parameter. There's just not enough data here to come to any conclusions.

I don't see this as having anything to do with the platform name. This seems to be a global issue with LB/BB sending the correct commands to LEDBlinky. Here's my response on a similar thread; To provide some additional information on this issue, what seems to be happening is that LB/BB is not sending LEDBlinky the "GameSelected" command when a game is selected from a LB/BB list. The GameSelected command includes the Game/ROM name as a parameter. So then, when LB/BB sends LEDBlinky the GameStart command, LEDBlinky doesn't know which game is running and hence the error; "No ROM specified for Game Start event. Missing Parameters?" Maybe there's a version of LB/BB that has a bug with the LEDBlinky commands? Or maybe there's some combination of LB/BB configuration that for some reason doesn't trigger the correct code when a game is selected? As the LEDBlinky dev, I can only see what's happening on the LEDBlinky side. As for the LB/BB code, I'm just guessing.

To provide some additional information on this issue, what seems to be happening is that LB/BB is not sending LEDBlinky the "GameSelected" command when a game is selected from a LB/BB list. The GameSelected command includes the Game/ROM name as a parameter. So then, when LB/BB sends LEDBlinky the GameStart command, LEDBlinky doesn't know which game is running and hence the error; "No ROM specified for Game Start event. Missing Parameters?" Maybe there's a version of LB/BB that has a bug with the LEDBlinky commands? Or maybe there's some combination of LB/BB configuration that for some reason doesn't trigger the correct code when a game is selected? As the LEDBlinky dev, I can only see what's happening on the LEDBlinky side. As for the LB/BB code, I'm just guessing.

The "FE System Lists Names" are used to identify which lists/wheels contain lists of emulators/systems rather than lists of games, and it's primary used for Pixelcade integration. This should have nothing to do with running an FE List Change animation. I'm wondering if there's a bug in the LB/BB code?

Hey, the virtual XInput controllers may make this a bit tricky because LEDBlinky uses the mame .cfg files to determine how the inputs map to the buttons and I'm guessing the virtual controller alters the mapping. I guess let's start by emailing me a debug.log so I can see what's going on.

That's a great catch! You are correct, setting detectjoysticks=0 would have also worked.

LEDBlinky only responds to commands it receives (it doesn't monitor any processes). What's most likely happening is LB/BB is sending the GameQuit command to LEDBlinky when the launcher app is no longer in memory. LEDBlinky has a feature that can help with this issue; Using the Controls Editor, edit the Daphne emulator and check the "Ignore GameQuit Commands" option. What this means is when you quit a Daphne game, the lit controls will not immediately revert back to your FE layout (because LEDBlinky doesn't know the game has ended), so it's not a perfect solution. But as soon as you do something else on the FE (scroll for example), the FE buttons should light up correctly. The only other option is considerably more complex and involves turning off LEDBlinky support in LB/BB and then creating your own batch/script files to send the LEDBlinky commands. I can't really provide details on this solution, but I believe others have done this. arzoo

CitznFish; I've responded to your email.