according to sdl2_jstest, I have a bunch of buttons that are not recognized...

@tashman said something about that in the other A+ thread two days ago.

Well this is an interesting one I tried setting this input a few times and the triggers werent updating right. After i deleted (reset/clear the inputs through emulation station) it worked. Something must have been amiss somewhere.

I can see whats going on with the hotkeys in the list now it looks right.

ps the system(raspian) was up to date not sure if it was some binary update that fixed it.

If anyone is experiencing problems with xbox360 controllers update from binary's (always do the system as well). Clear your inputs through retropie setup and reboot and set your controller up and the jobs a good one. My triggers wouldn't set right they where double/tripple pressing without resetting/clearing the input first hope this helps anyone with the same issue.

input_a_btn = "1"
input_b_btn = "0"
input_device = "Xbox 360 Wireless Receiver"
input_down_btn = "16"
input_driver = "udev"
input_enable_hotkey_btn = "8"
input_exit_emulator_btn = "9"
input_l2_btn = "6"
input_l3_btn = "11"
input_l_btn = "4"
input_l_x_minus_axis = "-0"
input_l_x_plus_axis = "+0"
input_l_y_minus_axis = "-1"
input_l_y_plus_axis = "+1"
input_left_btn = "13"
input_load_state_btn = "4"
input_menu_toggle_btn = "3"
input_r2_btn = "7"
input_r3_btn = "12"
input_r_btn = "5"
input_r_x_minus_axis = "-2"
input_r_x_plus_axis = "+2"
input_r_y_minus_axis = "-3"
input_r_y_plus_axis = "+3"
input_reset_btn = "0"
input_right_btn = "14"
input_save_state_btn = "5"
input_select_btn = "8"
input_start_btn = "9"
input_state_slot_decrease_btn = "13"
input_state_slot_increase_btn = "14"
input_up_btn = "15"
input_x_btn = "3"
input_y_btn = "2"

If interested, I can also raise another PR at some point regarding my post above, where I have custom launching scripts for A500, A600, A1200, and CD32 and a modified emulators.cfg to suit. Maybe you can take a look at it and see if you are happy to add it in. I know it's x86 only and probably not a priority but I think it improves on the defaults for those who use it.

@GrandMasterYoda That doesn't seem to be a problem that Kodi or RetroPie can solve, but your VPN software. This forum is for RetroPie and related gaming questions - if you have a problem with your VPN then it's best to address it on their support channel (forum/mailing list/etc.).

I went through the FC30 stage, and ultimately moved on to Xbox One bluetooth controllers due to them being a little easier on my carpal tunnel. I had horrible problems with bluetooth disconnects on both, until I purchased/installed a USB Bluetooth adapter. Now, I have no problems at all. You'd be surprised how much this helps.

Might want to check out my advice here: https://retropie.org.uk/forum/topic/19950/xbox-one-blue-tooth-joy-pad-connection-problem/3

I believe you should only need to follow items 4 and 5 as the other instructions are Xbox One bluetooth specific. (Basically - Buy/install the adapter, disable onboard bluetooth, re-pair your joysticks/edit any additional configs items)

Nobody has any ideas?

@yorks361 Each line is one command to execute in the order they are listed.

@Sterophonick How did you get it to boot games? I seem to have installed it fine, got all the BIOS files and the emulator runs, but when I try to load up a game from a .D88 file it just sits on a black screen with "V2 4MHz" at the bottom and what look like a couple of disk-accessing indicator lights. Nothing else happens.

(I've also tried installing Quasi88, which seems to have gone fine, but attempting to boot a game disk just leaves me looking at a black screen saying "V2 4MHz". I can access the menus with F12, but nothing in them gets me anywhere.)

EDIT: Ah, wait - so far as Quasi88 goes, it seems I was just really unlucky in my choice of games. I managed to pick a 100% fail rate of ones it doesn't seem to run (eg Xevious and Pac-Man). Other stuff like 1942, Bomb Jack and Dig Dug all work. They still don't in AdvMESS, though.

I had the same problems using a USB sound card.

It worked everywhere except in advmame

I fixed this on two different retropi images using this process:

edit the advmame.rc

delete these lines:

device_alsa_device default
device_alsa_mixer channel
device_sound alsa

After that it magically started working :)

Thank you. That was it. I forgot it :-D

already plugged suction cups, but anyway for a lot of reasons (i want avoid boring you), i need to add weight to my ps1 case...
Are there some kind of issues with metals as Lead ? magnetic issues or i dont know...
becouse i really need more weight.

EDiT:
thanks a lot to steptoe, for totally answered to my first question.
i will do as you say.

now i need just to understand if there is some kind of problems with Lead in order to ad weight to my ps1 case.

@kjulius888 said in Controller won’t sync to my new RPI3:

I just got my new RPI3 console

Please fill out the information in https://retropie.org.uk/forum/topic/3/read-this-first. What do you mean by console?

Please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Go here and scroll down to the bottom.

https://retropie.org.uk/docs/Dreamcast/

Sorry for the delay in replying to this. Just wanted to update this post.

Ok so it looks like the joystick inputs, Start, Select and Buttons A and B cannot be skipped but once I get past those inputs I can skip away and save the config (by getting to the end).

So I just took some spare buttons I have and plugged them into the encoder and then once they were mapped I removed the psychical buttons I don't want leaving only one in my case.

Thanks to Mitu for the help

But there's more. I guess the /dev/hidraw0 device is something to with motion sensors. This appears to confuse emulationstation.

https://retropie.org.uk/forum/topic/17650/dualshock-controllers-on-4-4-with-3b

This has a udev rule to add that removes that second device. Fixed at least one game for me.

@Kentinator there are several threads concerning N64 Emulation with the Pi, but to say it with a few words: your experience nails it.
Mario64, MarioKart64 and a few others work well, a lot of other games do not.