@mammaplank Good to know you like it! :-)

If you solved your issue, please mark this topic as Solved. It improves the forum's quality. ;-)

Cheers!

That video worked fine for me with an original SNES controller. What problem are you having?

@giles2005 said in Retropie portable gpio controls problem.:

iv now solved the problem anyway. would have been nice to share the solution as a means to help others but nevermind

Before you share the solution to "the problem", you should tell us what "the problem" actually is!!?? You still have not done this. Currently, your problem is still "my project"does not work! Bizarre. I shall assume from your username that you were born back in 2005 and it shows.

YAHOOO!!! It finally worked! THANK YOU SO MUCH!!!
:)

@kevreh Just keep in mind, the two methods conflict with each other, so I think GPIOneer turns off RetroGame. You can't use both at the same time.

@cyperghost You mean this post? I used the Adafruit retrogame software for the GPIO to keyboard stuff. It was easy.

@spannernick1 This blog post may help since you basically want to detect a GPIO button press and then send a keypress (Select+B) to reset the game.

np. Configuring controllers is explained here - https://github.com/retropie/retropie-setup/wiki/First-Installation - configuring additional controllers is under the "start" menu in ES (as you have found). Once configured in ES other emulators are set up automatically etc.

Does anyone have any further information on this. I too was following the same Instructables info and can not get this to work.

I have a slightly different controller then what is displayed, but it is a NES controller and not USB. I traced out the different color wires and adjust accordingly.

How can I test if the gpio is seeing any input from the wires soldered to the Pi Zero?

@bfenty if it is activating the unused c buttons try mapping those c buttons to non existing button numbers. (Like 20 and 21)

@denisuu Hi i have the same problem i wanna how you do for fix it?

@Ziffel since no one else has chimed in I'll give my two cents

I use several wireless Xbox 360 controllers with a Generic Xbox 360 Wireless Gaming Receiver that plugs in USB and I was very surprised that I didn't have any noticeable input lag. I also have an ASUS Nexus Player Gamepad that connects using Bluetooth and it seams pretty responsive as well (but I only tried it once and I use it on my laptop more). I bet there's probably a few emulators that are slower than others at input but for the most part I feel like my Raspberry Pi 3 handles all this pretty well.

What kind of controller are you using?

Now you did mention TV lag which is a real thing. I had already optimized my TV a long time ago but you might try some of these and see if it helps with your input lag:

First, if your TV has Game Mode then turn that on! Second, disable any power saving settings or ambient screen dimming. Third, turn off all post-processing effects on your TV like dynamic contrast, etc. Forth, make sure you're not daisy chaining the HDMI through an Xbox or another device (sometimes even amplifiers can delay signals). Fifth, also test with each HDMI port in the back of the TV. Sometimes 1 or 2 HDMI ports are faster than the rest. Last, maybe try other TVs and monitors to see if you still have input lag

Also make sure you have the newest version of RetroPie (I think there is some fixes to the emulator input latency):
https://github.com/retropie/retropie-setup/wiki/updating-retropie

@benjamin great build there! I'm looking at doing something similar myself - as has been said before it's perfect due to the built-in fan and plenty of space.

Can I ask what version GameCube you used for the donor? I have an older version which has the separate power regulator board - I'm planning on taking 5v and 3.3v direct from this but haven't done any testing yet to be sure it'll work.

using /etc/module for module options has been deprecated for some time, but worked in Raspbian Wheezy. Now it doesn't - the wiki needs updating in this area - feel free :-)

@bfenty Glad you got it working! That problem stumped me once or twice--it's sometimes good just to have another pair of eyes on it.

It doesn't seem like this is possible due to my SPI screen and GPIO SNES controllers both needing the clock pin on the Pi, plus the scripts don't seem to be easily configurable, so I decided to order a USB SNES adapter. Hopefully I didn't fry my controller when I was trying to hook things up concurrently today.

I figured this out and wrote up a basic script to turn the backlight on and off for my secondary display. It's in a post in my Super Famicom build thread.

@tehswiftone said in Single GPIO button:

Add this inside of your controllers config, don't forget to replace button with a proper button ID. This will be similar to exiting an emulator, you will use select + button to use it. So don't worry about it taking up a button on your controller.

input_volume_down_btn = "button"
input_volume_up_btn = "button"

I have mine setup to use Up and Down on the D-pad. Just change the "btn" to "axis".

input_volume_down_axis = "+1"
input_volume_up_axis = "-1"

@moosepr That does help! Thanks! This has been quite an educational experience.

@obsidianspider
you may have some issues in connecting and configuring the buttons of your bluetooth controllers. But once it's done, it's really easy to switch between the available controllers in RetroArch.

Trying to ask your question "how does the system choose which controller to use?" (assuming system = RetroArch). Like I said in my first response, RetroArch define some indexes for the controllers. The default is player1 = index 0, player2 = index 1, and so on (I didn't make it clear in my first post). But you can change it in retroarch.cfg. What the RetroPie-Setup config editor and my joystick-selection tool do is just this: change these options in retroarch.cfg.

BTW: the options related to what we are talking about here are input_player1_joypad_index, input_player2_joypad_index, etc...