Autofire switch was broken. Now it's ok!

@IanDaemon i found that when I'm in game and I bring up the retroarch menu, I can't move anything in the UI. The cursor will not move with keyboard or controller. I'm stuck there until I hard reset the pi because I have no input. I thought about a reinstall but I spent a lot of time scraping and setting up and I'd hate to have to do it all again.

Thanks for the update, it's interesting to follow your way to a working solution.

Yeah, it seems that it is a kind of game of chance to get the right BT controllers for the Pi, may it be that I was lucky or you and @gpmcty were unlucky.

And yes, it seems to be either direct connection without the home key, or using an adapter. Ironically, I'm fine with my adapter although I don't use the home key anyway. :)

@TheSkyrish It seems this is a mobile geared device - for IOS and Android - so it might not be compatible. Looking over some reviews and specs, it seems to have a 'mode switch' between different conenction modes (Gamepad/Mouse/ICade ?).
Can you try switching between them, re-pair and see if it's detected as gamepad ?

I mapped the C-Down button to A, the A button to B, and the B button to Y.

Problem solved. Reread the config directions and was sucessful. Sorry for the post.....

I believe I have figured it out, although I'll see how everything acts for the next few days.

I did have to use a separate bluetooth controller for each switch pro controller. I did everything using bluetoothctl. I left scan on both bt controllers, discovery off, and agent to NoInputNoOutput. I then connected one switch pro to each bluetooth controller and trusted the switch pro controller. Seems like I can now turn off a controller and turn it back on and it will connect automatically, nothing manual required.

I can't figure out the analog sticks with two controllers. I saw a post about using xboxdrv and a udev rule and a systemd service file, I tried that, but only one controller was being recognized as a "Switch Pro Controller", the other still only recognized as a "Pro Controller" (so no analog up or right). Also, for some reason when I had all of this enabled and I would try to configure the inputs on a switch pro controller it would say that 5 gamepads were detected. Couldn't get anything to actually work in a game either, only in emulationstation. Once I uninstalled xboxdrv and deleted the udev rule and systemd service file and restarted retropie then worked correctly, only seeing 2 gamepads and they work in games.

Maybe one day the analog sticks will just werk without messin around with it. Until then I just won't be playing n64, which I guess doesn't work all that well anyway

Do you have higher resolution versions posted somewhere? 720 or 1080 16:9 ratio?

Thanks in advance, I like the simplicity.

hey @dask, i spent a little time with this and managed to figure out a few things..

expanding on your idea of using the overlay/bezel system, it's possible to (using a hotkey combo) swap a transparent overlay with a control image overlay. this can be done on a per-system basis using the retroarch.cfg files located in /opt/retropie/configs/<system>

retroarch.cfg:

overlay_directory = "/your/path/to/overlays" input_overlay_enable = true input_overlay_hide_in_menu = true input_overlay = "/your/path/to/overlays/mame-controls.cfg" input_overlay_opacity = 0.9 input_overlay_scale = 1.0 input_overlay_next_btn = "6"

i think you can substitute the last line with input_overlay_next = "<keyboard key>" and input_overlay_next_axis = "<joystick axis>" to adapt this to your hardware scheme.

next, create the two images needed: transparent.png, and mame-controls.png

and here are the contents of mame-controls.cfg:

overlays = 2 overlay0_overlay = transparent.png overlay1_overlay = mame-controls.png overlay1_name = "mame-controls" overlay0_full_screen = true overlay1_full_screen = true overlay0_descs = 1 overlay0_desc0 = "overlay_next,400,460,rect,40,20" overlay0_desc0_next_target = "mame-controls" overlay1_descs = 0

there probably already exists a much better way of doing it, so this is just a proof of concept.
either way, hope it's enough to help you get started.

Nobody has any ideas?

I updated to version 4.4. from 4.1 aswell and i have the same problem.
Sometimes when a game starts (every emulator) i must wait 10-20 seconds before the controller responds
(for example "press START to start Tetris or Super Mario Land").
But the green text, that appears when i start a game, on the botton left appears and says "Controller Xbox 360 worked".

Sometimes the controller doesn't work in a game.
On 4.1 everything was fine.
Thats probably the same problem that FuerDrauka has.

I dont belive that we are the only ones with this problem, that must be an update issue and i dont know how to solve this.
I reinstall the xbox driver but nothing helps.
Maybe someone has a solution sometimes.

Now i'll create a new partition and reinstall 4.1

I need to point something out here as I had problems using them over bluetooth.
Not sure if anybody else has the same problem but it been there since I started using retropie a couple of years ago and is still there now.
It does not effect all games but I have noticed it in a few, hogs of war is one that comes to mind.
I use to use 2 normal ps2 controllers via usb adapter and 2 ps3 controllers via Bluetooth for some 4 player fun. The 2 ps3 controllers over bluetooth always use to cause stuttering whilst holding the button to fire your rockets in hogs of war, the 2 wired controllers never did this.
The way that solved this for me was to disable the built in wifi on my pi3, then they worked perfectly.
I now use 4 ps3 controllers via Bluetooth with no problems what so ever now since disabling built on WiFi.
Hope this helps just incase you come across same problem.
Rob

@omg209 got it figured out. Had to use key bindings in retroarch. Bind all for player 3 and 4.

nice post

@pme said in Logitech Attack 3 Joystick Configuration:

I've read that if you PRESSS AND HOLD any button on the device, it will skip the current configuration option and move to the next (https://retropie.org.uk/forum/topic/2108/can-t-skip-joystick-configuration/5) but this does not seem to be working.

The D-Pad is necessary to be configured to navigate in Emulationstation, you can't skip it entirely. Configure the joystick as D-pad, or use any other of the 11 buttons, and then you'll be able to configure your gamepad in detail in RetroArch or any other emulator you might use.

@stepea Then I can recommend the Mayflash Arcade Sticks. I have the predecessor of the F500.

@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 pressing ctrl+c and return to Emulation Station with the command exit.

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.

Hello and thanks for the answer again. Every emulator, even if I enter Retroarch to move between commands I have to use the controller 2 instead of 1. Image the last one, 4.4 and about the retropie version don't know what you mean, I have updated the script but don't know about the version, how do I see it? Sorry and thanks again.