Hi, firstly, the thing of DragonRise Controller is weird, I have agamepad and is also recognizable as a DragonRise, but I guess it happens when the controller s not officil. Second, arcade joysticks (The ones you bought) are not analog, they are 8-way sticks. Anyway, there are a few N64 games that work with the pad, like Kirby one.

@Heartless yeah that's what I figured. I suppose you could make changes to the mupen64plus.sh blacklist or one of the video plugin .ini files but that is a little above me.

@omen_peter oh yeah, you right. I thought he meant that it literally didn't work, despite typing in "raspberry" and hitting enter

@mitu Thanks for the reply

Thanks yes I'd already done that. :-) I also added lr-mupen64plus and made a couple of tweaks in the audio settings there, such as setting latency to 128 rather than 64, and setting the resampler to lowest rather than lower. Seems to take the edge off lag sometimes.

@quicksilver That's true, that's the video I watched and yes it's innacurate. Thanks for the link. Is there any way to stretch the screen with mupen64plus ? Any way to change the resolution ?

Well I feel like a right wally. I applied your code above and it works! However, I must have been mistaken as Yoshi runs awfully with gles2n64 as the emu. I imagine this is why the author blacklisted it. Most of the screen is black, and when you can see elements you only get bits here and there.

God only knows what I was thinking. Apologies to Mitu for taking up your valuable time with this. :-(

Ok, I found the problem : the rom I used was a .z64 one I grabbed from an emulation web site, and this rom was apparently patched for the z64 linux graphic plugin for mupen64 and this confused the controller setup. I got another one and this time it works...

@tr3v0r If you're just a beginner, then I suggest you use RGUI and the auto-configuration produced for RetroArch and don't edit any files.
Use the 'Core input remapping' (see docs) to change the RetroPad controls.

I think I worked it out. A year or so ago when I originally set up my retropie I was focussing on PSX emulation, and in the "autoconfig" controller mappings I must have force mapped this:

input_up_axis = "-1" input_down_axis = "+1" input_left_axis = "-0" input_right_axis = "+0"

Removing these seems to have done the trick

I mapped the C-Down button to A, the A button to B, and the B button to Y.

@Ranma Remember to turn off less accurate blending for this game as well. There are visual glitches if its turned on.

Thanks for you answer!

I didn't know about the different emulators but I was using Mupen64plus which has his own config...
I tried lr-mupen64plus but the cinematics appears black sometimes and the game crashed a few times...

So a (re)switch on Mupen64plus.

Just in case someone has the same issue I drop here the configuration issue I had:
In the config file (/opt/retropie/configs/from_retropie/configs/n64/mupen64plus.cfg) I had this line:

# Joystick event string for stopping the emulator Joy Mapping Stop = "J1B10/B9"

The combination B10 (hotkeys) and B9 (start) seems to be ok for me BUT my controller was J0 not J1. It fix the "stop emulator" command. Now I have to check for the load/save state commands.

Thanks again for you answer. It really helped me :-)

@Kentinator there are several threads concerning N64 Emulation with the Pi, but to say it with a few words: your experience nails it.
Mario64, MarioKart64 and a few others work well, a lot of other games do not.

@dankcushions thanks. Is there a way I can override the launch scripts?

@Steaz you'll need to choose the gliden64 plugin from the runcommand menu. Although on the pi gliden64 will crash your pi after about 10-20mins :/ cross your fingers the next pi has a better GPU.

@Oppo_Lock Thanks for sharing your solution.