Problem with 8bitdo Wireless Adapter and N64 conversion kit + mapping

[Dominik82]

Hello all,

I'm using the MiSTer FPGA since a long time and it's working great in comnibation with my PS4 controller and a 8bitdo Wireless Adapter (not 2).
Last days I ordered the N64 conversion kit from 8bitdo and built it into my old N64 controller.

First try failed, no pairing possible.
Afterwards I updated the stick to v2.05 (before it was 1.xx), and after that the controller could be paired. But the pairing was only done while it was powered. After power-switching I'd to pair it again
After 1-2 days I tried again and then no pairing was possible with the N64 controller (Pairing to the PS4 controller still works). I tried also to re-flash the stick, tried an old version, no chance - no pairing

Does anyone know how to fix this?

And another question regarding the mapping of the N64 controller.
As far as I've found I've to pair it at first in the main menu and then in the core menu?
In the main menu I've to use DPad, Analog and C-Pad?

And which option needs to be set in the core menu to use all buttons + stick?

Thanks for your help

[dickhardpill]

I only have experience mapping the controller as I’m wired.
I remember having to try a few times. Something about the C buttons being recognized as either a stick or a d-pad. It’s been a few months since I got it working and honestly I’m afraid to clear the settings and try again.

I didn’t have to change any setting in the core once I got the controller mapped in the menu and I used the regular mapping in the N64 core

[edr]

Not sure what the pairing issue might be but about the mapping. In the main mister menu map the N64 analog stick 1, dpad and A/B buttons, Start, and you can use some combo like Start+down to invoke the mister menu, make sure to go all the way to the end of the mapping where it asks for stick 1 a second time. In the n64 core menu, map dpad and all the buttons. Do not map the analog stick 1 at all in the n64 core menu. Everything will work fine when mapped this way.

[Dominik82]

Hi all,

thanks for your help.
The bluetooth connection isn't anymore the primary problem. I used another BT stick and it is connected.
So far, so good.

But still the problems with the mapping.
At first I connected the controller to my laptop (with windows 11) and tested - all buttons are working fine

Back to the MiSTer (doesn't matter if wired or via BT).
I did the mapping in the main menu (DPAD, Stick, AB, LR, Start) - Works
Then I start the N64 core and load a controller_test.z64 for testing.
At beginning only DPad, Analog and some buttons are working.
Then I start the N64 core mapping (DPad, AB, LR, Z, Start) - Fine. From the CPad only down and right are recognized, up and left not. But in windows everything is working.

Is this a problem with the linux driver? Or something else what needs to be configured?

[edr]

I thought the N64 core mapping also asks for all the c buttons as well, maybe I don't remember properly. I haven't had any issues, all the buttons have worked fine for me using the Nintendo nso N64 controller.

[dickhardpill]

These are the inputs I assume are associated with my 8bitdo conversion kit.

my controller is wired.

The files are;
N64_input_2dc8_2869_v3.map
input_2dc8_2869_v3.map

if you plug your controller in and run dmesg in the terminal it will show the idVendor=2dc8 and idProduct=2869 which you may need to change in the filename if you show different strings. I have no clue if this will work but it's worth a try?

the maps go in /media/fat/config/inputs/

[Dominik82]

Hi all

thanks for your help and also sharing your input mapping @dickhardpill
Today I tried one more time for myself and it's working
In my mind the missing step was to assign stick 2 to the CPad in the main menu.
Afterwards all buttons are recognized in the N64 core

Maybe that helps someone else