RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    RGB Commander mame

    Scheduled Pinned Locked Moved Help and Support
    rgbcommanderultimarc
    8 Posts 2 Posters 989 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      Purplehays86
      last edited by

      hi all,
      I am using a pacLED from ultimarc and running RGB Commander to illuminate my buttons. for the most part I have had no issues, until now. My problem comes to games loaded in my "Arcade" file. Not every game in that file run the same mame core, and that is causing some issues when getting buttons to light up. I can get into the config file for RGB Commander and edit just fine but in honest I don't know exactly what i'm doing. roms running fbalpha light up fine and some other cors do fine as well, but some like advmame-0.94 I cannot get to work. when i load up a game no lights turn on at all. can someone help me find a way to get this to work.
      thank you
      ~Justin~

      1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator
        last edited by

        That's a RGB commander issue - can you add some more info about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first ?

        From the documentation available with the program, I think you need to modify the configuration file (rgbcmd.xml) and add the emulator's name to the list. I see it's already configured for advmame

        	<emulator binary="mame-advmame" name="MAME non core" active="Blue" inactive="DimGray" arcade="1" retropie="1" retropiebinary="advmame" reference="arcade"/>

        but the name for advmame-0.94 is different. Is there a reason you're using such an old AdvMame release instead of 3.x ?

        P 1 Reply Last reply Reply Quote 0
        • P
          Purplehays86
          last edited by

          I am using a rpi3b+ using the updated version of retropie (4.4.12).

          it's actually not just advmama-0.94 that doesn't light up. Its any rom that is running any advmame. So advmame, advmame-0.94, and advmame-1.4. I see the entry for mame-advmeme in the xml file, from what it looks like to me is that the "reference" part of it doesn't seem to be working. From that I have found online is that all of the advmame cores have the same binary listing? not sure of that is right. when I load a rom using an advmame core the lights on my cabinet go from the blinking pattern used when at the ES front-end to just off. Any other rom that i load up not using advmame will load the correct led mapping as specified in the arcade section on the xml file.

          Some roms that I have run better on older versions of advmame like 0.94 like asteroids and battle zone. that's why I am using some older versions of advmame. But, like I said, it's actually not just the older versions that aren't working, but any advmame core.

          I'm really at a loss. the line for advmame cores in the xml file must be wrong somehow, but I don't know what to change or to what.

          thx for the help.

          P mituM 2 Replies Last reply Reply Quote 0
          • P
            Purplehays86 @mitu
            last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • P
              Purplehays86 @Purplehays86
              last edited by

              also here is what the log says when i load up an advmame game and when i exit out of it

              23/05/19 16:07:47 [INFO] [RGBAstop] animation stop -> success ...
23/05/19 16:07:47 [INFO] [processMonitor] advmame is running
23/05/19 16:08:02 [INFO] [processMonitor] advmame is no longer running
              1 Reply Last reply Reply Quote 0
              • mituM
                mitu Global Moderator @Purplehays86
                last edited by

                @Purplehays86 It seems like the advmame is detected by RGBCommander, so it might something else that's not configured or - maybe - incorrectly interpreted by the tool. Is there any debug switch you can turn on and see what it tries to execute ?

                P 1 Reply Last reply Reply Quote 0
                • P
                  Purplehays86 @mitu
                  last edited by

                  @mitu
                  There isn't a debugging switch that i know of. I do have access to the logs and a rgbcmdcon utility that can tell me... well..
                  "Emulator/application process names used in this configuration file must match the actual process name. If you have trouble with a specific process name that can't be found by the RGBcommander's daemon, use the included "rgbcmdcon" utility. To find the process"

                  after further investigating the log file i found something interresting.

                  Load GT97

31/05/19 19:28:00 [DEBUG] [rgbcmddMsgQueue] msg from rgbparse -> emu -> arcade -> rom -> gt97
31/05/19 19:28:00 [INFO] [rgbcmddMsgQueue] waiting for process retroarch to appear...
31/05/19 19:28:04 [INFO] [RGBAstop] awaiting animation stop...
31/05/19 19:28:04 [INFO] [fadeSpeed] PACLED64_1 fadespeed set to  0 -> SUCCESS
31/05/19 19:28:05 [INFO] [RGBAthread] rgba Pattern05_32 playback stop -> anim runtime ->  32.7389s
31/05/19 19:28:05 [INFO] [RGBAstop] animation stop -> success ...
31/05/19 19:28:05 [INFO] [processMonitor] advmame is running

Close GT97

31/05/19 19:28:22 [INFO] [processMonitor] advmame is no longer running
31/05/19 19:28:22 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/05/19 19:28:22 [WARNING] [connect] failed to detect deviceSERVOSTIK
31/05/19 19:28:22 [INFO] [setWay] setting SERVOSTIK to 8 failure
31/05/19 19:28:22 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStop.sh"  'advmame'
31/05/19 19:28:22 [INFO] [RGBAstart]random animation chosen -> Pattern33_32
31/05/19 19:28:22 [INFO] [fadeSpeed] PACLED64_1 fadespeed set to  0 -> SUCCESS
31/05/19 19:28:23 [INFO] [setRGBAspeed] RGBA Pattern33_32 speed set to 100
31/05/19 19:28:23 [INFO] [RGBAthread] rgba Pattern33_32 play back start at speed 100

Load Airwolf

31/05/19 19:28:54 [INFO] [RGBAstop] awaiting animation stop...
31/05/19 19:28:54 [INFO] [fadeSpeed] PACLED64_1 fadespeed set to  0 -> SUCCESS
31/05/19 19:28:54 [INFO] [RGBAthread] rgba Pattern33_32 playback stop -> anim runtime ->  31.7613s
31/05/19 19:28:54 [INFO] [RGBAstop] animation stop -> success ...
31/05/19 19:28:54 [INFO] [processMonitor] retroarch is running
31/05/19 19:28:54 [INFO] [setState] setting state for arcade gt97
31/05/19 19:28:54 [INFO] [setState] emu friendly name MAME core
31/05/19 19:28:54 [INFO] [setState] emu default active colour Orange r 255 g 128 b 0
31/05/19 19:28:54 [INFO] [setState] emu default inactive colour Off r 0 g 0 b 0
31/05/19 19:28:54 [INFO] [setState] emu default joyway 8
31/05/19 19:28:54 [INFO] [setState] emu default rgba RANDOM at speed 100
31/05/19 19:28:54 [INFO] [setState] emu default monitor rotation -> horizontal
31/05/19 19:28:54 [INFO] [fadeSpeed] PACLED64_1 fadespeed set to  0 -> SUCCESS
31/05/19 19:28:54 [INFO] [setState] gt97 known in minimame
31/05/19 19:28:54 [INFO] [setState] joyway set according to rom data -> 8
31/05/19 19:28:54 [INFO] [setState] rom monitor rotation is horizontal
31/05/19 19:28:54 [INFO] [setState] gt97 -> preconfiguration data available -> appending to state
31/05/19 19:28:54 [INFO] [setState] appending PACLED64_1 button name P1_BUTTON1 button colour Maroon r 128 g 0 b 0
31/05/19 19:28:54 [INFO] [setState] appending PACLED64_1 button name P1_BUTTON2 button colour Maroon r 128 g 0 b 0
31/05/19 19:28:54 [INFO] [setState] appending PACLED64_1 button name P1_COIN button colour Green r 0 g 255 b 0
31/05/19 19:28:54 [INFO] [setState] appending PACLED64_1 button name P1_START button colour White r 255 g 255 b 255
31/05/19 19:28:54 [INFO] [setState] appending PACLED64_1 button name P1_TRACKBALL button colour Gold r 255 g 215 b 0
31/05/19 19:28:54 [INFO] [setState] appending PACLED64_1 button name P2_BUTTON1 button colour OFF r 0 g 0 b 0
31/05/19 19:28:54 [INFO] [setState] appending PACLED64_1 button name P2_BUTTON2 button colour OFF r 0 g 0 b 0
31/05/19 19:28:54 [INFO] [setState] appending PACLED64_1 button name P2_COIN button colour Green r 0 g 255 b 0
31/05/19 19:28:54 [INFO] [setState] appending PACLED64_1 button name P2_START button colour White r 255 g 255 b 255
31/05/19 19:28:54 [INFO] [setState] skipping P2_TRACKBALL not present in control panel configuration
31/05/19 19:28:54 [INFO] [setState] preparing blinking led2 active colour Maroon r 128 g 0 b 0
31/05/19 19:28:54 [INFO] [setState] preparing blinking led2 inactive colour Off r 0 g 0 b 0
31/05/19 19:28:54 [INFO] [setState] preparing blinking led0 active colour White r 255 g 255 b 255
31/05/19 19:28:54 [INFO] [setState] preparing blinking led0 inactive colour Off r 0 g 0 b 0
31/05/19 19:28:54 [INFO] [setState] preparing blinking led1 active colour White r 255 g 255 b 255
31/05/19 19:28:54 [INFO] [setState] preparing blinking led1 inactive colour Off r 0 g 0 b 0
31/05/19 19:28:54 [INFO] [setState] committing state to led hardware -> PACLED64_1
31/05/19 19:28:55 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/05/19 19:28:55 [WARNING] [connect] failed to detect deviceSERVOSTIK
31/05/19 19:28:55 [INFO] [setWay] setting SERVOSTIK to 8 failure
31/05/19 19:28:55 [WARNING] [setState] failed to commit joyway to joystick hardware
31/05/19 19:28:55 [INFO] [setState] total setState processing time -> 0.299719s
31/05/19 19:28:55 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStart.sh"  'arcade' 'gt97'
31/05/19 19:28:55 [WARNING] [rgbcmddMsgQueue] arcade gt97 started -> setState -> failure
31/05/19 19:28:55 [DEBUG] [rgbcmddMsgQueue] msg from rgbparse -> emu -> arcade -> rom -> airwolf
31/05/19 19:28:55 [INFO] [rgbcmddMsgQueue] waiting for process retroarch to appear...
31/05/19 19:28:55 [INFO] [setState] setting state for arcade airwolf
31/05/19 19:28:55 [INFO] [setState] emu friendly name MAME core
31/05/19 19:28:55 [INFO] [setState] emu default active colour Orange r 255 g 128 b 0
31/05/19 19:28:55 [INFO] [setState] emu default inactive colour Off r 0 g 0 b 0
31/05/19 19:28:55 [INFO] [setState] emu default joyway 8
31/05/19 19:28:55 [INFO] [setState] emu default rgba RANDOM at speed 100
31/05/19 19:28:55 [INFO] [setState] emu default monitor rotation -> horizontal
31/05/19 19:28:55 [INFO] [fadeSpeed] PACLED64_1 fadespeed set to  0 -> SUCCESS
31/05/19 19:28:55 [INFO] [setState] airwolf known in minimame
31/05/19 19:28:55 [INFO] [setState] joyway set according to rom data -> 8
31/05/19 19:28:55 [INFO] [setState] rom monitor rotation is horizontal
31/05/19 19:28:55 [INFO] [setState] airwolf -> preconfiguration data available -> appending to state
31/05/19 19:28:55 [INFO] [setState] appending PACLED64_1 button name P1_BUTTON1 button colour Blue r 0 g 0 b 255
31/05/19 19:28:55 [INFO] [setState] appending PACLED64_1 button name P1_BUTTON2 button colour Red r 255 g 0 b 0
31/05/19 19:28:55 [INFO] [setState] appending PACLED64_1 button name P1_COIN button colour Gold r 255 g 215 b 0
31/05/19 19:28:55 [INFO] [setState] skipping P1_JOYSTICK not present in control panel configuration
31/05/19 19:28:55 [INFO] [setState] appending PACLED64_1 button name P1_START button colour White r 255 g 255 b 255
31/05/19 19:28:55 [INFO] [setState] appending PACLED64_1 button name P2_BUTTON1 button colour Blue r 0 g 0 b 255
31/05/19 19:28:55 [INFO] [setState] appending PACLED64_1 button name P2_BUTTON2 button colour Red r 255 g 0 b 0
31/05/19 19:28:55 [INFO] [setState] appending PACLED64_1 button name P2_COIN button colour Gold r 255 g 215 b 0
31/05/19 19:28:55 [INFO] [setState] skipping P2_JOYSTICK not present in control panel configuration
31/05/19 19:28:55 [INFO] [setState] appending PACLED64_1 button name P2_START button colour White r 255 g 255 b 255
31/05/19 19:28:55 [INFO] [setState] preparing blinking led2 active colour Blue r 0 g 0 b 255
31/05/19 19:28:55 [INFO] [setState] preparing blinking led2 inactive colour Off r 0 g 0 b 0
31/05/19 19:28:55 [INFO] [setState] preparing blinking led0 active colour White r 255 g 255 b 255
31/05/19 19:28:55 [INFO] [setState] preparing blinking led0 inactive colour Off r 0 g 0 b 0
31/05/19 19:28:55 [INFO] [setState] preparing blinking led1 active colour White r 255 g 255 b 255
31/05/19 19:28:55 [INFO] [setState] preparing blinking led1 inactive colour Off r 0 g 0 b 0
31/05/19 19:28:55 [INFO] [setState] committing state to led hardware -> PACLED64_1
31/05/19 19:28:55 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/05/19 19:28:55 [WARNING] [connect] failed to detect deviceSERVOSTIK
31/05/19 19:28:55 [INFO] [setWay] setting SERVOSTIK to 8 failure
31/05/19 19:28:55 [WARNING] [setState] failed to commit joyway to joystick hardware
31/05/19 19:28:55 [INFO] [setState] total setState processing time -> 0.306067s
31/05/19 19:28:55 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStart.sh"  'arcade' 'airwolf'
31/05/19 19:28:55 [WARNING] [rgbcmddMsgQueue] arcade airwolf started -> setState -> failure

Close Airwolf

31/05/19 19:29:09 [INFO] [processMonitor] retroarch is no longer running
31/05/19 19:29:09 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/05/19 19:29:09 [WARNING] [connect] failed to detect deviceSERVOSTIK
31/05/19 19:29:09 [INFO] [setWay] setting SERVOSTIK to 8 failure
31/05/19 19:29:09 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStop.sh"  'retroarch'
31/05/19 19:29:09 [INFO] [RGBAstart]random animation chosen -> Pattern33_32
31/05/19 19:29:09 [INFO] [fadeSpeed] PACLED64_1 fadespeed set to  0 -> SUCCESS
31/05/19 19:29:09 [INFO] [setRGBAspeed] RGBA Pattern33_32 speed set to 100
31/05/19 19:29:09 [INFO] [RGBAthread] rgba Pattern33_32 play back start at speed 100

load airwolf

31/05/19 19:29:38 [DEBUG] [rgbcmddMsgQueue] msg from rgbparse -> emu -> arcade -> rom -> airwolf
31/05/19 19:29:38 [INFO] [rgbcmddMsgQueue] waiting for process retroarch to appear...
31/05/19 19:29:42 [INFO] [RGBAstop] awaiting animation stop...
31/05/19 19:29:42 [INFO] [fadeSpeed] PACLED64_1 fadespeed set to  0 -> SUCCESS
31/05/19 19:29:43 [INFO] [RGBAthread] rgba Pattern33_32 playback stop -> anim runtime ->  33.6779s
31/05/19 19:29:43 [INFO] [RGBAstop] animation stop -> success ...
31/05/19 19:29:43 [INFO] [processMonitor] retroarch is running
31/05/19 19:29:43 [INFO] [setState] setting state for arcade airwolf
31/05/19 19:29:43 [INFO] [setState] emu friendly name MAME core
31/05/19 19:29:43 [INFO] [setState] emu default active colour Orange r 255 g 128 b 0
31/05/19 19:29:43 [INFO] [setState] emu default inactive colour Off r 0 g 0 b 0
31/05/19 19:29:43 [INFO] [setState] emu default joyway 8
31/05/19 19:29:43 [INFO] [setState] emu default rgba RANDOM at speed 100
31/05/19 19:29:43 [INFO] [setState] emu default monitor rotation -> horizontal
31/05/19 19:29:43 [INFO] [fadeSpeed] PACLED64_1 fadespeed set to  0 -> SUCCESS
31/05/19 19:29:43 [INFO] [setState] airwolf known in minimame
31/05/19 19:29:43 [INFO] [setState] joyway set according to rom data -> 8
31/05/19 19:29:43 [INFO] [setState] rom monitor rotation is horizontal
31/05/19 19:29:43 [INFO] [setState] airwolf -> preconfiguration data available -> appending to state
31/05/19 19:29:43 [INFO] [setState] appending PACLED64_1 button name P1_BUTTON1 button colour Blue r 0 g 0 b 255
31/05/19 19:29:43 [INFO] [setState] appending PACLED64_1 button name P1_BUTTON2 button colour Red r 255 g 0 b 0
31/05/19 19:29:43 [INFO] [setState] appending PACLED64_1 button name P1_COIN button colour Gold r 255 g 215 b 0
31/05/19 19:29:43 [INFO] [setState] skipping P1_JOYSTICK not present in control panel configuration
31/05/19 19:29:43 [INFO] [setState] appending PACLED64_1 button name P1_START button colour White r 255 g 255 b 255
31/05/19 19:29:43 [INFO] [setState] appending PACLED64_1 button name P2_BUTTON1 button colour Blue r 0 g 0 b 255
31/05/19 19:29:43 [INFO] [setState] appending PACLED64_1 button name P2_BUTTON2 button colour Red r 255 g 0 b 0
31/05/19 19:29:43 [INFO] [setState] appending PACLED64_1 button name P2_COIN button colour Gold r 255 g 215 b 0
31/05/19 19:29:43 [INFO] [setState] skipping P2_JOYSTICK not present in control panel configuration
31/05/19 19:29:43 [INFO] [setState] appending PACLED64_1 button name P2_START button colour White r 255 g 255 b 255
31/05/19 19:29:43 [INFO] [setState] preparing blinking led2 active colour Blue r 0 g 0 b 255
31/05/19 19:29:43 [INFO] [setState] preparing blinking led2 inactive colour Off r 0 g 0 b 0
31/05/19 19:29:43 [INFO] [setState] preparing blinking led0 active colour White r 255 g 255 b 255
31/05/19 19:29:43 [INFO] [setState] preparing blinking led0 inactive colour Off r 0 g 0 b 0
31/05/19 19:29:43 [INFO] [setState] preparing blinking led1 active colour White r 255 g 255 b 255
31/05/19 19:29:43 [INFO] [setState] preparing blinking led1 inactive colour Off r 0 g 0 b 0
31/05/19 19:29:43 [INFO] [setState] committing state to led hardware -> PACLED64_1
31/05/19 19:29:43 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/05/19 19:29:43 [WARNING] [connect] failed to detect deviceSERVOSTIK
31/05/19 19:29:43 [INFO] [setWay] setting SERVOSTIK to 8 failure
31/05/19 19:29:43 [WARNING] [setState] failed to commit joyway to joystick hardware
31/05/19 19:29:43 [INFO] [setState] total setState processing time -> 0.300989s
31/05/19 19:29:43 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStart.sh"  'arcade' 'airwolf'
31/05/19 19:29:43 [WARNING] [rgbcmddMsgQueue] arcade airwolf started -> setState -> failure

Close Airwolf

31/05/19 19:29:52 [INFO] [processMonitor] retroarch is no longer running
31/05/19 19:29:52 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/05/19 19:29:52 [WARNING] [connect] failed to detect deviceSERVOSTIK
31/05/19 19:29:52 [INFO] [setWay] setting SERVOSTIK to 8 failure
31/05/19 19:29:52 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStop.sh"  'retroarch'
31/05/19 19:29:52 [INFO] [RGBAstart]random animation chosen -> Pattern50_32
31/05/19 19:29:52 [INFO] [fadeSpeed] PACLED64_1 fadespeed set to  0 -> SUCCESS
31/05/19 19:29:53 [INFO] [setRGBAspeed] RGBA Pattern50_32 speed set to 100
31/05/19 19:29:53 [INFO] [RGBAthread] rgba Pattern50_32 play back start at speed 100

                  from the looks of it, the program recognizes any advmame rom; and, does know which configuration under the "arcade" section to reference when loading each rom. it, for some reason, seems to just get stuck mid way. when I load up another game that is not having these problems (in this case a fba rom) the refrence to the game that isn't working shows up then gets shutdown in favor of the correct process. when i close out of the rom and load up the exact same one, it only shows the correct process.
                  so, to me, it seems as tho the process is getting hung-up somewhere.

                  also here is what the rgbcmgcon utility spat out... i put in some notation saying what i was doing.

                   _____ _____ _____                               _
| __  |   __| __  |___ ___ _____ _____ ___ ___ _| |___ ___
|    -|  |  | __ -|  _| . |     |     | .'|   | . | -_|  _|
|__|__|_____|_____|___|___|_|_|_|_|_|_|__,|_|_|___|___|_|
RGBcommanderConsole 0.1.0.1 linux
a *nix arcade cabinet led and joystick driver - GUI dev tool
Copyright 2015-2017 Gijsbrecht De Waegeneer
compilation date Dec 25 2017 16:37:25

connected to localhost:2724 RGBcommander linux build 0.4.0.5
get,procdiff
modify processes and rerun command to get diffs
get,procdiff

Open Airwolf	

(--)kworker/3:0-events(++)kworker/3:0-mm_percpu_wq,retroarch,sh
get,procdiff
modify processes and rerun command to get diffs
get,procdiff

Close airwolf	

(--)kworker/0:0-mm_percpu_wq,kworker/0:1H-kblockd,kworker/2:0-mm_percpu_wq,kworker/3:0-mm_percpu_wq,kworker/u8:0-brcmf_wq/mmc1:0001:1,retroarch,sh(++)kworker/0:0-events,kworker/0:1H-mmc_complete,kworker/2:0-events,kworker/3:0-events,kworker/u8:0-events_unbound
get,procdiff
modify processes and rerun command to get diffs
get,procdiff

open GT97		

(--)kworker/0:1H-kblockd,kworker/1:2-events,kworker/3:0-mm_percpu_wq(++)advmame,kworker/0:1H-mmc_complete,kworker/1:2-mm_percpu_wq,kworker/3:0-events,sh
get,procdiff
modify processes and rerun command to get diffs
get,procdiff

Close GT97	

(--)advmame,kworker/0:0-events_power_efficient,kworker/2:0-events_freezable,kworker/3:0-events,sh(++)kworker/0:0-events,kworker/2:0-events,kworker/3:0-events_power_efficient
get,procdiff
modify processes and rerun command to get diffs
get,procdiff

open airwolf

(--)kworker/0:1H-kblockd,kworker/0:2-events_power_efficient,kworker/2:2H-kblockd,kworker/3:2-cgroup_destroy,kworker/u8:0-events_unbound,kworker/u8:2-brcmf_wq/mmc1:0001:1(++)kworker/0:1H-mmc_complete,kworker/3:2-events_power_efficient,kworker/u8:0-brcmf_wq/mmc1:0001:1,kworker/u8:2-events_unbound,retroarch,sh
get,procdiff
modify processes and rerun command to get diffs
get,procdiff

close airwolf

(--)kworker/2:0-events_freezable,kworker/u8:0-events_unbound,retroarch,sh(++)kworker/2:0-events,kworker/u8:0-brcmf_wq/mmc1:0001:1
get,procdiff
modify processes and rerun command to get diffs
get,procdiff

Open Airwolf

(--)kworker/2:0-events,kworker/3:1-cgroup_pidlist_destroy,kworker/u8:0-brcmf_wq/mmc1:0001:1,kworker/u8:1-events_unbound,kworker/u8:3(++)kworker/0:2-mm_percpu_wq,kworker/2:0-events_freezable,kworker/u8:0-events_unbound,kworker/u8:1-brcmf_wq/mmc1:0001:1,retroarch,sh
get,procdiff
modify processes and rerun command to get diffs
get,procdiff

Close Airwolf		

(--)kworker/0:2-events,kworker/2:0-events_freezable,kworker/3:3-cgroup_pidlist_destroy,kworker/u8:1-events_unbound,retroarch,sh(++)kworker/0:2-mm_percpu_wq,kworker/2:0-mm_percpu_wq,kworker/u8:1-brcmf_wq/mmc1:0001:1

                  im not sure what im looking at, but it seems like advmame is detected like it should.

                  1 Reply Last reply Reply Quote 0
                  • mituM
                    mitu Global Moderator
                    last edited by

                    From the logs, yes, it looks like the detection works ok. You can try contacting the author and provide the logs, maybe they have an idea what is going wrong here - the RetroPie side (emulators) is not changed from what is declared in the configuration.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post

                    Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                    Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.