@mitu said in Weird Emulationstation controller issue.:

There you go...

I only deleted it after the issues though. In case for some random reason it wasn't being able to be read and the option to reset in the configuration tools wasn't working.

I'll give that all a go tomorrow and see how i get on.

@mitu the thing i should know do is to open the retropie datas in which the retropie folders are is it right?

I'm not sure what you mean. If you're referring to the installation of the Nintendo HID driver I mentioned before, that can be done outside of any RetroPie folders, since it's not directly related to RetroPie.

@slaan1974 said in Controller setup for GameCube in dolphin:

@YFZdude Hi, So I got this piece of software running,

select Controllers , select GC standard controller, press configure, select XInput2/0/Virtual core pointer, press all the individual buttons, they do react

select Emulate Wii BT, Emulated Wii, Config, select XInput2/0/Virtual core pointer, press all the individual buttons, they do react , i save this as profile sln

the buttons do react, and i saved it, but still i am not able to press buttons in a GC or Wiiware game

It sounds like you are doing the setup properly. You can confirm your controller settings have 'stuck' by re-opening the GUI and looking at the screens.

When you launch a game, does the runcommand box (grey with text) say it is launching with dolphin-gui ? That's how I run it so it may be necessary.

I haven't configured an emulated wii remote before but I did previously use a Logitech F710 as a gamecube controller and as long as the input is selected to match your device it should work. Double check that part. On my system, the Xinput2/0/Virtual core pointer is my keyboard and touchpad combo I think. I can try to verify that later tonight when I am in front of my system again.

EDIT: I just checked my setup at work that I forgot I had access to. Indeed on this system I have Xinput2/0/Virtual core pointer (keyboard and mouse) and evdev/0/Logitech Gamepad F310 (controller).

to add to the story i use a Wii Pro Controller

Is this the same controller you use with other emulators and it works fine?

Another couple of things you can try:

When you launch the Dolphin GUI, you can set (add) a ROMs directory and the games should show in the list on the main GUI page. Try launching a game directly from the emulator itself instead of through RetroPie and verify if the controller works this way. If that still doesn't work, try launching the Dolpin GUI with the sudo command in front of it and trying again. If the controller works this way, then you will need to add a udev rule to allow the emulator to have proper access to the controller.

on all other emulations i notice there is a bar in the bottom when a game starts this tells me the controller is enabled, but with GC/Wii there is no bar

The bar with the controller information is most likely a RetroArch notification. This would be present in any emulator whose name starts with lr-* which indicates the libretro version of the emulator. Correct me if I'm wrong but I think you are running the standard version of dolpin and not lr-dolphin. So those messages wouldn't appear the same way.

Yeah, unfortunately knock offs are rarely great. My SN30 Pro is my favorite since it combines the old (SNES shape and layout) with the new (L2, R2, and dual analog sticks).

I have a couple of Vilros NES USB controllers and they aren't bad. They aren't high quality by any means, but they do the job better than other clone controllers I've owned.

@nunna78 hi there. I must complète this Thread:

XpadNeo: Xbox-One Controller does not fully works on SteamLink. X and R1 Button are not recognized

Xboxdrv: Xbox-One Controller work perfectly on SteamLink.

So if you want to play SteamLink i'll recommand Xboxdrv instead of Xpadneo

@mitu and to any future readers - I fixed it!

After much searching, I found this link https://github.com/goodtft/LCD-show/issues/278 for an issue with an LCD display I tried to use years ago. Apparently, it updated my /boot/cmdline.txt file to put ttyAMA0 in my console, instead of the default serial0. Swapping it back to console=serial0,115200 and rebooting, and now bluetooth works again!

@sleve_mcdichael Thanks! I will try this out.

@barbudreadmon , thanks for the heads up. Will keep that suggestion in mind in case of any issues.

I use a Pro Controller with the Pi thanks to those instructions. It works wired and wireless.

Did you have any error messages while installing either the HID module or the userspace driver?
How are the lights on the controller behaving when you connect the cable? Do they start blinking "side to side" quickly? If they do, did you press L + R to pair?

@unknown nah the memory is emulated, don't think a proper emulator could read the data from a real memory card; that would be cool though.

@fretman yeah anything will do just to get the bluetooth ones sorted. These are all things you'll learn as progress as a Raspberry Pier

@erickwilson thank you for the advice. I am currently playing with a temporary keypad. Waiting for some of the retro keypads to come back in stock. Seems like there's a shortage on them right now.

I tried multiple solutions suggested here, but to no luck. In the end, I just started the whole installation all over again and it's working fine now. God knows what happened, but it seems re-installing everything seems to have fixed it... weird.

Thanks for the replies everyone!

Thanks @mitu this did the trick! All working well now.

pitfall.jpg

They were on the latest update.
I already figured it out for myself.
I've uninstalled the xpad and xpadneo drivers from the RetroPie setup utility.
Then I installed the latest neoxpad driver from github, with this patch applied: https://patch-diff.githubusercontent.com/raw/atar-axis/xpadneo/pull/283.patch
Finally I edited the /etc/modprobe.d/99-neoxpad-bluetooth.conf file, comment out the disable ertm thing and make sure to load it with xpad emulation enabled:
# options bluetooth disable_ertm=y
options hid_neoxpad xpad_emulation=1

Reboot and pair both controllers in xpad mode.

Setup both controllers in emulationstation and skip the non-working left and right triggers.
When done simply close emulationstation and add the triggers manually:
input_r2_axis = "+5"
input_l2_axis = "+2"

Et voila!

Both controllers working in x-input mode, without the shitty startup delay when launching retroarch and working rumble for my psx and dreamcast games.

This issue has been fixed with an RPI OS update for the Bluetooth packages, so the workaround is no longer necessary - an update of the packages/OS is enough.

You can update the packages as part of RetroPie's update menu or manually with

sudo apt update sudo apt upgrade

The bluez package version that fixes the issue - 5.50-1.2~deb10u2+rpt1.

@sleve_mcdichael

BLAH! I had a feeling that was coming. Cool. Thanks for the info!

@edward_ci that's how I understand it, yeah. As far as the emulator is concerned, it's just another USB gamepad. If the two gamepads have identical device names/IDs, then they'll use the same config file. So whatever mapping like button_12 = "A" or whatever is set in the config file, will be the same for both gamepads. If "button 12" is whatever button is wired in position "6F" on the board or whatever, and you have that wired to a different physical button, then your "A" button will be that different physical button. They need to be exactly the same.

@mitu I feel so dumb I am so sorry to bother you. It worked turns out it was wring problem like you said.

Thank you for everything though