LedBlinky

[bob.records]

Hope some one can help, since updating HS\RL to ataest LEDBlinky keeps showing game profiles on launch then reverting back to the hyperspin profile while the game is still running.

 

It mentions it in LEDblinkys support page about an option you can tick in config to get rounf this, but I still get same problem.  Log seems to show code 4 gets sent after game launch.  Anyone have this issue?  Turning off xpadder sorts this in RL but I use xpadder so..... hopefully someone knows a fix

 

B

[middric]

I see the same behaviour - doesnt happen with MAME games but for example using PCLauncher:

06:43:16 PM |  Launching Game 
06:43:16 PM |  Command Line is: "C:\LEDBlinky\LEDBlinky\LEDBlinky.exe" 3 "PAC-MAN Championship Edition DX+" "Steam" 
06:43:16 PM |  Using HyperLaunch
06:43:16 PM |  Getting Launcher path 
06:43:16 PM |  Launcher located at C:\Hyperspin\RocketLauncher\RocketLauncher.exe
06:43:16 PM |  Running Launcher 
06:43:16 PM |  Launcher Command Line is: C:\Hyperspin\RocketLauncher\RocketLauncher.exe "Steam" "PAC-MAN Championship Edition DX+"
06:43:18 PM |  Command Line is: "C:\LEDBlinky\LEDBlinky\LEDBlinky.exe" 4 
06:43:18 PM |  Command Line is: "C:\LEDBlinky\LEDBlinky\LEDBlinky.exe" 4 

The game is running, and has focus. But LEDBlinky has been sent the game stop event (final 2 lines)

[middric]

@bob.records - I have configured rocketlauncher to hit LEDBlinky for me as a PostLaunch step:

 

PostLaunch set to the LEDBlinky.exe path

PostLaunchParameters to: 3 "rom name" "emulator name"

 

Works, but obviously its a a bit of a pain!