Manettes N64 originales sur Recalbox

[J3R3M]

Bonjour à tous,

Je suis l'heureux propriétaire d'un Raspberry 3 conditionné dans un Nespicase depuis plus d'un mois maintenant. Il s'agit là de mon premier post, mais sachez que j'ai déjà passé de nombreuses heures sur ce forum et le Github qui sont de véritables mines d'or!!

Je vais essayer d'être le plus clair et concis possible, n'hésitez pas à me dire si je devais avoir omis des informations!

Je possède 4 Manettes de N64 (deux officielles et deux copies) avec le connecteur original (en 3 points).
Je me suis procuré deux convertisseurs N64 x2 to USB afin de pouvoir les connecter sur Recalbox, mais ça n'est pas aussi simple que sur les tutos en ce qui me concerne.

Premièrement, à partir du moment où cet adaptateur est câblé, plus aucune ROM ne peut se lancer.
Pire, même après qu'il ait été débranché et RB redémarré plusieurs fois, les ROMs ne se lancent toujours pas.
J'ai déjà procédé à 3-4 réinstallations complètes pour corriger cela, mais ça commence à prendre beaucoup de temps et c'est certainement trop radical. Je suppose qu'il y a plus simple pour refaire fonctionner les ROMs ?

Dans un second temps, je ne suis pas en mesure de suivre les tutos existants, car voici ce que me donne la commande sdl2-jstest -l, que des manettes soient connectées ou non :

Found 2 joystick(s)

Joystick Name: 'USB GamePad USB GamePad'
Joystick Path: '/dev/input/event0'
Joystick GUID: 03000000790000007918000010010000
Joystick Number: 0
Number of Axes: 4
Number of Buttons: 16
Number of Hats: 1
Number of B***s: 0
GameController:
not a gamepad
Axis code 0: 0
Axis code 1: 1
Axis code 2: 2
Axis code 3: 5
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297
Button code 10: 298
Button code 11: 299
Button code 12: 300
Button code 13: 301
Button code 14: 302
Button code 15: 303
Hat code 0: 16

Joystick Name: 'USB GamePad USB GamePad'
Joystick Path: '/dev/input/event1'
Joystick GUID: 03000000790000007918000010010000
Joystick Number: 1
Number of Axes: 4
Number of Buttons: 16

Number of Hats: 1
Number of B***s: 0
GameController:
not a gamepad
Axis code 0: 0
Axis code 1: 1
Axis code 2: 2
Axis code 3: 5
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297
Button code 10: 298
Button code 11: 299
Button code 12: 300
Button code 13: 301
Button code 14: 302
Button code 15: 303
Hat code 0: 16

J'ai néanmoins suivi le tuto, mais, évidemment, ça ne fonctionne pas du tout.
Je pense que l'adaptateur nécessite une installation différente, mais celle-ci m'échappe complètement...

Chers amis, pouvez-vous, s'il-vous-plaît, m'aider dans mes légères difficultés?

Merci d'avance du temps accordé à mon cas!

[Substring]

@j3r3m plop
2 choses :

• avec ton sdl2-jstest, tu avais branché com ien d'adaptateurs ? 1 ou 2 ? Réciproque : si tu ne branches qu'un seul adaptateur, sdl2-jstest te sort quoi ? 1 ou 2 pads ?
• archive de support please

J'ai ma petite idée sur ton problème

[J3R3M]

Merci de ta réponse et de ta réactivité @Substring !
Alors, j'avais branché qu'un seul adaptateur et ça me donnait bien deux pads.

Voici l'archive de support avec seulement un adaptateur (sans manettes) : https://file.ac/MRhuYK7KVQM/
Archive avec Adaptateur + 2 Manettes connectées : https://file.ac/dzm0X23St6w/
Archive avec 2 adaptateurs seuls : https://file.ac/UcjCmVH9lgc/

(Bon, ne pas hésiter à me dire si les différentes archives sont inutiles, évidemment)

Merci beaucoup de ta réponse !

[paradadf]

@j3r3m @Substring sorry to jump in and change the language, but I have the same adapter and made it work (haven‘t used it since, and necer finished the configuration).
Related topic:
https://forum.recalbox.com/topic/12909/n64-mayflash-adapter-oem-controller

I haven‘t translated the previous messages, but I‘m pretty sure you must erase that weird character on es_system.cfg to make it work.
That rectangle gets shown properly on the mupen64plus config files though.

Note: it would be great if those kind of weird characters wouldn‘t break configgen or launching emulators.

On a perfect world, we should be able to map n64 from EmulationStation individually! That way

[Substring]

@paradadf said in Manettes N64 originales sur Recalbox:

On a perfect world, we should be able to map n64 from EmulationStation individually! That way

Wut ? Missing a part of your answer ?

[paradadf]

@substring ups, sorry.

I was saying that it would be great if we could overwrite the standard ES controller configuration on another entry on the menu just for n64, as that controller is really particular. That way the user wouldn‘t need to mess around with configfiles. Adding the dummy on recalbox.conf isn‘t very friendly with mupen64plus standalone.

[Substring]

@paradadf prolly ... Too much work for too little result. Contributors are rare and very valuable

[J3R3M]

@paradadf @Substring

No worries about the language change and thank you for your answers ! I read your initial topic.
After deleting "&#24" in my es_input.cfg file, all my roms are now playable and it's better than reinstall RC !

However, I still can't use my N64 controller. Nothing's happen with any button...
One more thing, I can't anymore exit the emulator because my others controllers seems to be disabled and my N64 controllers don't work. I have to shutdown and restart my Raspberry for each test.

What's wrong ?

One more question, if the controller was a bit okay, should it be able to navigate in Recalbox or should it works only when a N64 ROM is playing ?

I agree your sentence about an easier way to add and map N64 controllers

[paradadf]

@j3r3m can you use the controller in any retroarch core after deleting that html entity?

[J3R3M]

@paradadf
I did another remote configuration on Recalbox.
All my ROMs did not launch before I edit es_input.cfg file.
After a reboot, my controllers can navigate in Recalbox, but can't be used in any core after the file editing : no reaction when I press any button, whatever used emulator.

[paradadf]

@j3r3m try configuring it again in ES. I could navigate right after the mapping.

[J3R3M]

@paradadf, actually, I can navigate in ES, but the remote is not usable when a rom is started.
Or maybe I misunderstood ?

[paradadf]

@j3r3m after configuring the controller in ES and deleting the weird character in es_input.cfg I was able to play.

[J3R3M]

@paradadf, my official remotes are able to play on N64 ROMs!
I just meet some issues :

• The L+R keys pressed together don't exit the emulator
• The joystick seems "unatural".
  For example, for Super Mario 64 ROM, I have to push strongly on the joystick for the up-side and Mario only walks.
  But, on the others joystick sides, its reactions are smoothier.
  However, I have no issue with this remote when using it on N64.

Sorry if I'm not clear about this, it's a bit abstract and I don't know how to describe this with my middle-level english!

I also have to test my two unofficial remotes... Later in my daily list!

[paradadf]

@j3r3m for all your difficulties you should read the topic I posted above. That‘s the hard part which needs configuration. Joytick sensibility is also an issue, that‘s why it feels unnatural. And you must du all those configurations manually.

[J3R3M]

@paradadf Okay, I hope it will be quick to configure!

However, It seems good for another remote.
In fact, original remotes have almost 20yo and I bought 2 copies a few months ago.
I think it explain why I don't have the same sensibility between 2 remotes.

I tried N64 games on Emulation Station for the first time a few minutes ago.
I tried GoldenEye and Im disapointed because I met a lot of computeur slowdowns...
Do everybody meet this issue ?