Wireless controllers constantly scroll down in RGUI

[jabberwock101]

I am running RetroPie 4.0.2 on a Raspberry Pi 3. I have a problem in which anytime I access the RGUI using any wireless controller (whether it is connected via a dongle or directly through my RPi3's bluetooth) the cursor will constantly scroll down. I do not experience the same issue in EmulationStation or in any ROM, it only occurs in RetroArch. I have had this issue in the past, but thought it was just an issue with the controller having some sort of hardware glitch. I have tried five different controllers (two different OUYA controllers, a T3+ controller, and two Rock Candy PS3 controllers) and all have the same issue. I do not experience this issue with any wired controller or keyboard that I have tried, and the Rock Candy controllers only experience the issue after making an initial selection in the RGUI (i.e. entering a second menu from the main one) or if they attempt to access the RGUI directly from within a game. The issue only seems to pop up after the initial configuration is done, and does not seem to be an issue when I first configure or tweak a controller in RetroArch.

This issue makes remapping my controllers extremely difficult. The one thing that has worked is accessing RetroArch with a wired keyboard, hovering over the "Bind All" option in User 1 Binds, and then selecting it just as my controller is connecting. If I time it just right I can rebind the keys, however, this does not always work.

I have an 11 month old son who enjoys pulling on cords, so wired controllers really aren't a very good option for me right now. Any assistance or direction would be greatly appreciated.

[edmaul69]

@jabberwock101 are you sure its not scrolling up?? If it is you need to apply this linux patch

https://retropie.org.uk/forum/topic/4516/how-to-apply-raphnet-kernel-patch-to-fix-northwest-drift

[jabberwock101]

@edmaul69
If it's scrolling up, it's doing so in a very downward manner. That patch might be the start to a fix though...

[edmaul69]

@jabberwock101 yes i would still try this patch. I would say it is most likely to fix it.