8bitdo SFC30 - Glitch at Retropie Main Menu?

hiulit

Same here! I'm using an NES30 controller and I've already followed @Rion 's steps.

steveieboy

Good news! This is what I did to get it to work:

Backed up my ROMs and BIOS to a local drive
Re-installed disk image from retropie to my SDCard
Updated scripts/installed latest packages
Rebooted
Followed this guide, I just turned the controller on, didn't need to put it into pairing mode: https://retropie.org.uk/docs/8Bitdo-Controller/

denisuu

I also reinstalled retropie from from the latest image on the website. Still the same problem :(

I'm on firmware 2.70 how about you?

steveieboy

@denisuu Yes on 2.70 controller firmware. On a Pi 3.

BuZz

@denisuu 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 (Best to start a new topic in the future and provide full info about set-up)

This topic is about another issue.

You probably have the wrong 8bitdo hack mode - you need to reconfigure after switching it off - did you follow the guide here ? https://retropie.org.uk/docs/8Bitdo-Controller/ ?

flandigt

Hi there,

I do not know if it's the correct topic but I had to install some of

these files

into the directory

/opt/retropie/configs/all/retroarch/autoconfig/

to get the controllers working while playing roms.

My configuration also is

2* 8bitdo SFC30 controllers
raspberry pi 3
retropie 4.1

denisuu

@BuZz I did follow that guide it's been posted already the post above mine.

I did a clean install
turned off the "8bitdo mapping hack = off "
paired the SFC30
udev rule
rebooted
setup the controller in ES

Still when I turn it on it starts scrolling left until I press right.

BuZz

@denisuu does the controller work in games ? That was the issue I was replying about - the issue with it navigating left until a button is pressed is a known kernel issue and affects a lot of controllers - nothing can be done about it in retropie by us automatically - but it's possible to manually fix it, but it requires a kernel recompile.

denisuu

@BuZz Yes it is now, but I will open another topic about that isue.

Is there any fool proof tutorial on how to recompile the kernel? Or is that advanced stuff?

Rion

@denisuu I wouldn't mind that you posted a new thread on how to compile the kernel with this fix.

hiulit

@BuZz It's good to know that it's a kernel bug. Thanks for the info.