Main > Software Forum
RGBcommander 0.4 released for Windows, Linux and rPI2/3
mahuti:
Well I got another ledwiz. This time, instead of the full led-wiz, I got the ledwiz gp, but didn't realize I had to get a different ID'd device. GroovyGameGear's site directions say for this EXACT device, get another number if you're using two... I didn't think about the fact that the Ledwiz Gp is the same reported device as a ledwiz... so now I guess I'll just order another one with a different ID so I can use both at once (it's ok, the "wrong" one will get used elsewhere). In any case, I wired it up to test it out and it looks great for what I'm using it for.
Here's a link to the video of it (work in progress).
in the light:
in the dark:
I still need to make custom animations (and wire it up a little better inside) And I need to change up the other ledwiz in the control panel so I get my button lighting back (sigh)
Gaucho:
thank you @ZoOl007 I've got everything set up. However I am having issues with coleco it's like the system doesn't even look at the xml file for this emulator. Do you know if you've had success with coolcv on PI3? The only other issue i've run across is I'm unable to shutdown or reboot correctly anymore it seems to hang for almost 5minutes then shutsdown or reboots. I'll post my log file when i get home and maybe something you see makes sense. thank you again.
ZoOl007:
Hi,
on RetroPie it is no different than the other ones. You need to specify the folder name where the roms reside as the binary="RomFolder" in the respective emulator tag and it has to be tagged as a retropie="1" in that same tag.
Furhtermore you can open an ssh session to your pi and tail the log file by tail -f /usr/sbin/rgbcommander/rgbcmdd.log
As you launch games you'll be able to follow what it does. It'll depict [DEBUG] [retropiefifo] picked up command -> and then what it got.
That way you should be able to troubleshoot.
If you can't sort it out mail your config file and a representative log please
5 minute reboot delay -> yes... I've had that sporadically - it has to do with the init.d system and the way I stop the daemon... I can't pinpoint it because I can't reproduce it...
I am however porting the old init.d to systemd to make it run on GoovyArcade and I expect that that issue will go away then... no eta
regards
Gaucho:
Thank you for getting me back so quickly. I'll work on this tonight. BTW I did find out that if when I do an ssh session that's when I'm getting the delay but if I just play and reboot or shutdown its fine. Again thank you.
Gaucho:
Here is my log:
--- Code: ---20/05/17 23:47:09 [DEBUG] [retropiefifo] picked up command -> START~coleco~Lady Bug (USA, Europe).col
20/05/17 23:47:09 [DEBUG] [retropiefifo]cmd -> START core -> coleco rom -> Lady Bug (USA, Europe)
20/05/17 23:47:09 [INFO] [retropiefifo] waiting for process retroarch to appear...
--- End code ---
then nothing
Here is my config:
--- Code: --- <!--coleco-->
<emulator binary="coleco" name="coleco" active="Green" inactive="Off" retropie="1">
<rom id="default">
<control name="P1_BUTTON1" colour="White"/>
<control name="P1_BUTTON2" colour="White"/>
<control name="P1_BUTTON3" colour="White"/>
<control name="P1_BUTTON4" colour="White"/>
<control name="P1_BUTTON5" colour="White"/>
<control name="P1_BUTTON6" colour="White"/>
<control name="P1_START" colour="Green"/>
<control name="P2_BUTTON1" colour="White"/>
<control name="P2_BUTTON2" colour="White"/>
<control name="P2_BUTTON3" colour="White"/>
<control name="P2_BUTTON4" colour="White"/>
<control name="P2_BUTTON5" colour="White"/>
<control name="P2_BUTTON6" colour="White"/>
<control name="P2_START" colour="Green"/>
</rom>
</emulator>
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version