Main > Software Forum
RocketBlinky - 3rd Party LEDBlinky Quick Setup Tool
newoski:
--- Quote from: Titchgamer on October 09, 2016, 04:14:53 pm ---Sorry just noticed that was a bad example as ime not sure whats going on with p2 on that cp?
Should be as per p1 though.
--- End quote ---
Thanks, I figured. My question was... the game list should be identical for MVS/AES, right? I'll take a look at the latest HyperSpin XMLs and then add the missing system. I've got an updated XML that I'm itching to release. Minor fixes and tons more MAME games added. I'll add the 2nd Neo Geo system, before releasing.
Titchgamer:
Good stuff.
Again great work :)
newoski:
--- Quote from: Titchgamer on October 09, 2016, 04:17:21 pm ---Good stuff.
Again great work :)
--- End quote ---
Oh, I bet I can guess your issue with the CPS systems... Are you using RocketLauncher? If so, you'll need to use the LEDBlinky name function. Let me know and I'll walk you through it. Super easy.
Titchgamer:
Yes I use HS and RL.
I have it set up now ok anyway but may be worthwhile posting it up here for future people?
newoski:
--- Quote from: Titchgamer on October 09, 2016, 04:21:27 pm ---Yes I use HS and RL.
I have it set up now ok anyway but may be worthwhile posting it up here for future people?
--- End quote ---
I just added this to a short FAQ on the HyperSpin thread. I'll update the original post here, shortly.
2. I'm using RocketLauncher with LEDBlinky and most of my systems, including MAME, are working.... But none of the MAME-related systems, like SNK Neo Geo, CAVE or Capcom Play System, are working. What's wrong?
Before fixing this, it's important to understand why it is happening. RocketLauncher communicates with LEDBlinky via command line arguments. The format looks like this:
LEDBlinky.exe "romname" "systemname"
For example:
LEDBlinky.exe "1942" "MAME"
LEDBlinky needs all MAME-related systems to be named "MAME" so that it can pull the correct control and color information. The problem is that RocketLauncher uses specific names for each system. As a result, RocketLauncher sends LEDBlinky command line arguments that it doesn't know what to do with. Here is an example:
LEDBlinky needs to receive:
LEDBlinky.exe "2020bb" "MAME"
RocketLauncher is sending:
LEDBlinky.exe "2020bb" "SNK Neo Geo"
The solution is to use RocketLauncher's LEDBlinky System Name function. This function allows a custom System Name to be used, on a per system basis. To fix each MAME-related system, we need to tell RocketLauncher to send "MAME" as the system name for that system:
Select the MAME-related system in RocketLauncher, for example, SNK Neo Geo
Settings -> Main Settings -> LEDBlinky -> System Name
Add MAME to this empty field
RocketLauncher will now tell LEDBlinky to use "MAME" as the system name for this system, and LEDBlinky should work as desired.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version