RGB Commander confused by Clone ROMs; how do i “check” ROM name…?

[aechadwick]

I am using RGBCommander to control LEDs on my RetroPie (Raspberry PI 3, RetroPie 4.2).

Sometimes, RGBCommander does not load the button colors, deferring to the "default" color set.

Typically, RGBCommander does this when it cannot identify a ROM’s name, either because there is no entry in rgbcmdd.xml or the entry uses an incorrect name (a misspelling, or an errant character)

Specifically, RGBCommander does not load the button colors for some cloned ROMs (not all just some).

All my MAME ROMS are running in either LR-FBALPHA or LR-MAME2003 (to wit, always LibRetro, and all the ROMS are running fine).

I have a few clone ROMs, like, the 2-player version of X-Men.

xmen.zip runs fine and loads the correct button colors.

xmen2p.zip runs fine, but loads the default button colors.

the runcommand window claims “launching xmen2p” but RGBCommander (via rgbcmdd.xml) does not react to that ROM name. (that is: there is an entry <rom id="xmen2p"> but RGBCommander loads <rom id="default"> instead.)

/usr/sbin/rgbcommander/rgbcmdd.log shows the name of the ZIP, but then claims the ROM is unknown... (the lines look like this, i’ve snipped out a bunch of setstate-buttoncolor and so on)

[DEBUG] [retropiefifo] picked up command -> START~arcade~xmen2p.zip
[DEBUG] [retropiefifo]cmd -> START core -> arcade rom -> xmen2p
# rgbcommander does some stuff
[INFO] [setState] setting state for arcade xmen2p
# rgbcommander does some stuff
[INFO] [setState] supplied rom is unknown -> reset to default -> appending default to state
# rgbcommander does some stuff
[INFO] [retropiefifo] arcade xmen2p started -> setState -> success

So, RGBCommander sees the name of the ROM as it’s loading… but at some point there’s a disconnect, something that prevents the daemon from connecting the ROM to the XML entry.

This is NOT a problem with the XML file, i have tested it (repeatedly) by changing & adding games & colors.

I kind of think maybe it's a problem with the ROM name maybe being different from the ZIP name…? That doesn’t make sense, but it’s the only disconnect i can imagine.

Is there a way to check the name of the active ROM? like, the actual name of the ROM as percieved by LibRetro while running it…? (I mean, anOTHER way to check the name, as the runcommand window provides the name of the ZIP'd ROM, but maybe that's not the ACTUAL name...?)

I welcome any other insight.

(I’ve searched the forum and can’t find anyone else affected by this, but please excuse me if I missed something.)

[aechadwick]

Solved.

turned out it was actually a malfunction in RGBCommander; the developer contacted me directly to say he was working on a solution. He let me test a rebuilt daemon, and will roll the fix into his next release.

Check out this thread at Arcade Controls.

—Æ