Phantom controller movements only on ARCADE menu
-
Pi Model or other hardware: B
Power Supply used: Anker 2.1 amp USB
RetroPie Version Used: 4.4
Built From: https://github.com/RetroPie/RetroPie-Setup/releases/download/4.4/retropie-4.4-rpi2_rpi3.img.gz
USB Devices connected: none
Controller used: knockoff Pro Controller U
Error messages received: none
Log found in /dev/shm/runcommand.log (if relevant): n/a
Guide used: n/a
File: not sure
Emulator: not sure
Attachment of config files: not sure what is relevant
How to replicate the problem: not sureI've setup my RetroPie and then installed many ROMs for a number of non-Arcade systems. All was good. Then I added Arcade ROMs. It seems that ONLY in the Arcade menu (and none of the other menus), I get phantom/ghost controller issues. I am using a third party Nintendo compatible Controller Pro U over Bluetooth. A couple things about the Arcade ROMs. There are over 2000 whereas the other menus have maybe 100-200 items. The Arcade ROMs have videos with them (snap and wheel folders) and the other folders do not. Any ideas as to why I get the weird issues just in this one menu? I've seen many threads about similar issues but they are all mostly 1-2+ years old without any clear solutions. Thanks!
-
Maybe because entering the Arcade folder solicits the system more - RAM/CPU - and your power source is below the recommended specs. You can try looking in the system's log (running
sudo dmesg
from the command line) and see if you spot any warning/errors.
Do you get the under-voltage lightning bolt when you browse the folder ? Do the ghost inputs appear if the controller is connected via USB instead of Bluetooth ? -
@lex3001 Please excuse the question, but are you really sure about the ghost inputs only happening in the Arcade menu? I ask because It sounds rather strange. Did you wait long enough in all of the menus to rule out mere coincidence of it happening only in the Arcade menu?
You can test a controller for ghost inputs out of Emulation Station by pressing F4 (you'll land in Retropie's command console) and entering this command:
jstest --event /dev/input/js0
Any inputs coming from the device will be listed while the command is running. You may have to change
js0
to the device name of your controller, e.g.js1
,js2
etc. You can end the test by pressingctrl+c
and return to Emulation Station with the commandexit
.As for solutions for ghost inputs from bluetooth controllers, I fixed those that came from my Qumox Wii U Pro controllers by using a Mayflash Wii U Pro wireless adapter instead of the Raspberry Pi's own bluetooth to connect them. That got rid of the ghost inputs for good.
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.