@quicksilver that's strange as it now gives out High Res graphics on games whereas it never did before I'm sure of it. It was because of this that I tended to go for the Mupen64plus - GlideHighRes options as on some games it just looked great (No Mercy, Super Mario 64) I'll have a look around for the post and update on this thread. I'm probably just getting confused as they're all called Mupen something or other. Thanks!

@dankcushions what is the best way to do the intial config? Set it up for LR-MUPEN, then customize the mupen64plus config file?

@cyber said in RPI4: Kodi version update, N64 stuttering, no rumble pack:

I have selected there now the first one (lr-mupen64plus-next).

I cannot find any config files "lr-mupen64plus*" - thats why I took now pictures of the settings which I can see with the retroarch core menu:
https://1drv.ms/u/s!AnFpCl7HpNVtg9s3sr_EwOEzchjJRw
https://1drv.ms/u/s!AnFpCl7HpNVtg9s2ejenqrrrORMhew
https://1drv.ms/u/s!AnFpCl7HpNVtg9s10tfvMXtuttTlPA
https://1drv.ms/u/s!AnFpCl7HpNVtg9s0Up0aFFn_PBBQ7A

i don't think there's much point testing lr-mupen64plus-next as it's going to be slower than standalone, but there's a few settings you can change:

native resolution factor = 1x Overscan = Disabled

be mindful to change only these, and exactly these. some others are named similarly.

graphical issues: compared with mupen64plus-gliden64-highres I have e.g. in the menus black lines: https://1drv.ms/u/s!AnFpCl7HpNVtg9s4IPgzfQ90i32wrQ

comparing what to what? please be specific. if it's to lr-mupen64plus-next, again this is not optimal. use mupen64plus-gliden64

@rip I had the very same issue and could not find any good solution posted already so I will post mine here (Z button was never an issue for me , Z button is also my hotkey)

Once configured as screenshot above and after first launch with n64 emu the following configuration was generated into /opt/retropie/configs/n64/InputAutoCfg.ini

; SWITCH CO.,LTD. Controller (Dinput)_START [SWITCH CO.,LTD. Controller (Dinput)] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = C Button U = button(9) L Trig = button(4) C Button D = button(1) button(0) #C Down gets mapped to button(1) which is really B Button and button(0) is the actual C Down button DPad U = hat(0 Up) DPad L = hat(0 Left) C Button L = button(3) Y Axis = axis(1-,1+) X Axis = axis(0-,0+) DPad R = hat(0 Right) Z Trig = button(6) C Button R = button(8) R Trig = button(5) DPad D = hat(0 Down) Start = button(12) A Button = button(2) # Lack of mapping for button B at all ; SWITCH CO.,LTD. Controller (Dinput)_END

I then used jtest to actually view which button was what hence my conclusions above with jstest /dev/input/js0 then I edited the file nano /opt/retropie/configs/n64/InputAutoCfg.ini with the following

; SWITCH CO.,LTD. Controller (Dinput)_START [SWITCH CO.,LTD. Controller (Dinput)] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = C Button U = button(9) L Trig = button(4) C Button D = button(0) DPad U = hat(0 Up) DPad L = hat(0 Left) C Button L = button(3) Y Axis = axis(1-,1+) X Axis = axis(0-,0+) DPad R = hat(0 Right) Z Trig = button(6) C Button R = button(8) R Trig = button(5) DPad D = hat(0 Down) Start = button(12) A Button = button(1) B Button = button(2) ; SWITCH CO.,LTD. Controller (Dinput)_END

Hope this might help someone else with same setup, cheers

/a

@UberLumby Look at least my version of raspberry:)

@retropieuser555 legend oz Zelda starts but can’t get past name screen, Wayne Gretzky 3D hockey won’t run, wwf no mercy runs and Gats stuck in menu, super mario 64 runs a + b work but MARIO won’t move

@gmesmer no it's not.

Thank you for the quick reply.

Sorry, I pulled the logs from a VM I was running to reproduce the issue.
I attempted to run it again on the Ubuntu box and it finally took.

Not sure what the issue was, but it appears to be working now (of course after I post a question about it :)

Thank you!!

Followed both of your guys' advice. Works perfectly now, thanks!

Same question - where is game data folder situated now?
According this manual https://retropie.org.uk/docs/Optimization-for-Nintendo-64/ the folder must be /home/pi/.local/share/mupen64plus/ but share folder is empty and game saves are located in roms folder....
So, where need to put hires_texture to apply it now?

i think the 2030 pi will support it lol

What is the better performance n64 emulator for pi3B+

@jordanvs read the replies carefully

I think that's because the 1 PS4 controller appears to generate 2 input devices, so the numbering is skewed. Try the workaround proposed here.

@mitu ok I think I know what to do. Should I edit the file to the keycodes?

@pegasus1130
I am dealing with a similar issue and I am now very, very close to getting it working. I found a post from a year or so ago which suggested that opening the retroarch GUI from within the emulator, then remapping from the "control" menu therein. For me, this involved hitting f1 on a keyboard to bring up the retroarch gui and then switching each button around according to the results of jstest, and finally saving a "core remap file". This let me fix everything but a few buttons. The issue that remains is that there is no listing in that controls menu for buttons 0 and 1, which are my C up and C right.

@hhromic
Amazing ! will give it a try
haha funny , i cant change it to lower .
maybe upper .