@fonzman great, thank you.

@liankain not possible at all and impossible to install also.

Recalbox is a custom linux built using Buildroot to be as low-weight and dedicated to retrogaming as possible, it doesn't even include apt or any package manager.

@quemandoacromo said in (S)NES mini controller can be used via Wii remote:

Brand?Model?

Brand/model of what? =)

My Wiimote is a pirate clone of an original Wii Remote. Bluetooth detects it as "Nintendo RVL-CNT-01" NES mini controller is official one. Brand: Nintendo, Model: CLV-002 =) Bluetooth adapter is integrated in Raspberry Pi 3b+, I dunno what chip is used.

I just connected the NES mini controller to Wiimote. And it worked fine for me. BTW Wiimote is still functional. For example, 1P can use Wiimote to control the game and 2P can do it with NES controller and vice versa =)

@substring said in Recalbox PC64 + Wii remote comment faire fonctionner le tout ?:

@sebdepringy ça se passe dans les options de dolphin je crois. Donc HK+B, et là il faut chercher un peu une fois dans le menu de configuration de dolphin. Mieux vaut avoir une souris de branchée

Bon il va falloir que je branche du filaire je pense, recalbox ne voit pas mon clavier sans fil Logitech avec pad intégré…. par contre je ne sais pas par qu'elle miracle la manette ps3 a l'air d'etre reconnu par contre avant c'etais fluide en mode "demo" et maintenant le jeux lague a 10fps ….

Thanks!!!

@miso117 sadly no. There is a bug in advancemame regarding controls, doesn't look lik it's fixed yet

@farbkasten I really don't know.
I tried it many times to correct the wiki and take the screenshots, and I didn't have this issue.
Once mapping over, I pressed enter key, and the software asked me to press many time the same button, and that was over.

Did you affect the button to different functions ?
Did you try with an other one remote ?
I have one that get stuck on previous step.

@elbcore write about your setup, otherwise you are just expressing your feelings (and there are surely better forums for that :) )

Hi, I had the same problem with kodi in librelec and I find this solution for the remote not is coming to be detected as joystick in the link https://github.com/denilsonsa/udev-joystick-blacklist

I only had to do this:

cd /storage/.config/udev.rules.d/
curl -o /etc/udev/rules.d/51-these-are-not-joysticks.rules \ https://raw.githubusercontent.com/denilsonsa/udev-joystick-blacklist/master/51-these-are-not-joysticks.rules
curl -o /etc/udev/rules.d/51-these-are-not-joysticks-rm.rules \ https://raw.githubusercontent.com/denilsonsa/udev-joystick-blacklist/master/51-these-are-not-joysticks-rm.rules

I know it not is valid for recalbox, but may be exist a similar option in Recalbox.

Regards.

I'm also having the same issues.

Wii Remote + Classic Controller pairs correctly, is configured and works in EmulationStation. However, it fails to work with games. This is on the latest 4.1.

I also had an older image of some 4.0 beta where the Wii Remote + Classic Controller combo worked with a bluetooth dongle. After updating that image to the latest 4.1 (to use internal bluetooth), the controller was only partially working. In particular, I had the following issues: 1) games recognized the controller as Player 2 (might explain why it doesn't work with some games), 2) Hotkey button was not working although configured properly.

Since the controller appears to pair correctly, maybe this is just a configuration issue. Unfortunately, if the controller is not recognized in game (or the Hotkey button doesn't work), I can't even use the retroarch menu to reconfigure.

The Wii Remote + Classic Controller is such a great combination for retrogaming. It would be really great if someone from the Recalbox team or someone with more expertise could chime in on these issues. Thanks.

Hello
No chance.

@paradadf That is awesome news! I will try to find out if the first one works (because it looks awesome), otherwise I will get the Rii i8.

Thanks for answering, mate!

@lackyluuk said in If can i use wii remote???:

dongle

thank you very much

Please use the Topic Tools to mark a thread as solved

cat devices I: Bus=0005 Vendor=2820 Product=0009 Version=0100 N: Name="Bluetooth Wireless Controller   " P: Phys=00:15:83:49:94:89 S: Sysfs=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/bluetooth/hci0/hci0:43/0005:2820:0009.0001/input/input0 U: Uniq=9a:fc:dd:48:fb:f8 H: Handlers=sysrq kbd mouse0 js0 event0 B: PROP=0 B: EV=12001f B: KEY=4 0 ffff0000 1f0000 10000 2000007 ff9f307a c14057ff febeffdf ffefffff ffffffff fffffffe B: REL=103 B: ABS=30627 B: MSC=10 B: LED=1f   I: Bus=0005 Vendor=1949 Product=0404 Version=011b N: Name="Broadcom Bluetooth Wireless  Remote Control                  " P: Phys=00:15:83:49:94:89 S: Sysfs=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/bluetooth/hci0/hci0:44/0005:1949:0404.0003/input/input2 U: Uniq=74:c2:46:7d:62:f6 H: Handlers=kbd event1 B: PROP=0 B: EV=10001b B: KEY=10000 1110 40000800 1681 0 0 0 B: ABS=100 0 B: MSC=10

It's a known Kodi issue and would require key mapping especially for Kodi to fix it.