Kerm Posted November 5, 2020 Share Posted November 5, 2020 (edited) So, I'm having a new issue that has cropped up with LEDBLINKY. Basically, when selecting a game in BigBox I get the controls "demo" for that game. When game launches the controls come up again and then the LEDs revert to the BIGBOX animation I have. Attached is a debug. It almost looks like BLINKY is getting a false that I have reverted to BIGBOX when I am still in Daphne(HD) in the attached log. Maybe someone has seen this or has some idea. I usually try to figure things out on my own - but I have not cracked this yet and it's been a few days of messing around. Emulator launch is at 20:19:06 *** Added note: Mame seems to work as expected...*** Edited November 6, 2020 by Kerm Deleted log file Quote Link to comment Share on other sites More sharing options...
Kerm Posted November 6, 2020 Author Share Posted November 6, 2020 (edited) After additional digging I know what's happening. @arzoo It has to do with the way LB/BB launch my Daphne games. Games being launched are using a launcher.exe that takes the file name (ready dummy file) and serves up the proper command line to launch the game in Daphne with settings. LB/BB > Launcher.exe ("ROM") > Launcher pushes to > Daphne.exe -"file/settings/ect." When this happens LB/BB send the information to LEDBlinky as the program running is "Launcher.exe". Once this files does it's magic and phases and passes the data to "Daphne.exe" it closes. This causes LEDBlinky to assume that game was terminated. I have tried to add both "Launcher.exe" and "Daphne.exe" - but because LB/BB only sends out the information once, for the originating "emulator" (Launcher.exe) - LEDBlinky knows nothing of Daphne running. I guess at this point I'm looking for a solution that would allow the launching of my Daphne games directly using the Daphne.exe. Thoughts? How is this handled with other games that use a batch file or other type of pre-run software??? Thanks in advance to anyone with some thoughts! Edited November 6, 2020 by Kerm Quote Link to comment Share on other sites More sharing options...
arzoo Posted November 6, 2020 Share Posted November 6, 2020 (edited) 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 Edited November 6, 2020 by arzoo Quote Link to comment Share on other sites More sharing options...
Kerm Posted November 8, 2020 Author Share Posted November 8, 2020 Thanks for the tip - no dice. Still reverting. Not an issue with LEDBlinky at this point, Guess I'm going to have to seek an alternative way of launching my Daphne games. The only way LEDBlinky would be able to "notice" is if it was monitoring focus and not running task. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.