@Khyron

In case someone ever asks the same question, the answer is

Hotkey+

A = Reset
X = Load SaveState
Y = Save SaveState

DPAD UP = INCREMENT SAVESTATE SLOT
DPAD RIGHT = FAST FORWARD
L1 = SCREEN CAPTURE

@kalmath

Problème réglé, pour ceux qui rencontreraient également ce petit soucis, allez donc dans /recalbox/share/system/configs/mupen64/input.xml

Supprimez le fichier "input.xml"

Same problem here. I also have SWITCH CO.,LTD. Controller (Dinput).
For me an InputAutoCfg.ini file was never create or overwritten after I created it myself.

@Lumbeechief081
Can you search your mupen64 ini file?
/recalbox/share/system/configs/mupen64/mupen64plus.ini I know it LONG but what I am looking for is the SaveType listed under Donkey Kong 64. There will be Multiple entries in your file so you can do the following

log in via SSH:
nano /recalbox/share/system/configs/mupen64/mupen64plus.ini
hit CTRL + w (search)
type Donkey Kong 64 and hit enter
check under the entry and make sure SaveType is "Eeprom 16KB"
hit CTRL + w again and the nenter for the next instance.
Check that each version of the rom has the seave type listed as Eeprom 16KB (if one is wrong change it)

This sometimes happens the save file is set to 4KB or 8KB

The alternative is to replace your ini file with a known good one. Some older ini files had it listed wrong. Not sure if this is the case but its worth looking into. It would absolutely cause this behavior.

@macu Think of a "core" as an emulator, for instance there are many emulators for SNES: Snes9x, higan, etc... Each one is a core.
Then there are libretro adapted cores (the ones that use the retroarch environment) and standalone cores (with their own environment, configs, etc). Recalbox uses libretro and standalone cores, sometimes you can choose between them as is the N64 case. Sometimes not (Dosbox for instance). The devs choose cores availability depending on the system (Raspi, PC, etc), they do so with performance un mind. N64 emulation is tricky, especially in lower end machines like Raspberry Pi, so its a matter of trial and error which core is better for a game.

bonjour !!!
Merci de vos réponse j'ai fait ce que vous avez dit et sa fonctionne

Hi guys!

Finally I got the solution for that. What I did is to move from mupen64plus to libretro core (mupen64 but from libretro) under the N64 emulator settings to use.
Key mapping is now working as expected using Xbox One controller.
The problem about slowness (using libretro - mupen64) was caused because I already set libretro snes9x to use run ahead (latency settings) and saved the configuration, so N64 emulation was also trying to use run ahead settings that are quite bit processor intensive.
I just disabled run ahead (lantency settings) for this N64 core only, and now I am ready to go!

Thanks!

@Substring
J'ai suivi le tuto en anglais comme tu m'as indiqué.
Tout fonctionne correctement, voici ce que j'ai fait :

recalbox/share/system/configs/mupen64/mupen64plus.cfg ghq_hirs = 1 ghq_hirs_gz = False Démarrer un jeu N64 avec l'émulateur Mupen64plus et le core Gliden64 Mettre les dossiers hi-res dans recalbox/share/system/.local/share/mupen64plus/hires_texture/

Donc pour résumer, pas besoin de Rice, tout roule avec Gliden64.

Merci !

@machuna leeme bien. Tenes que cambiar el emulador por defecto por uno de libretro (que tiene retroarch!). Presiona select sobre el juego, editar metadatos y y cambia las dos primeras opciones a libretro y glupen, lueho guarda.