My PPSSPP version on the RPi4 is older than on my Batocera laptop.

There's a new option "Render duplicate frames to 60Hz" that improved smoothness significantly on my laptop, but I cannot test it on my Rpi4 at the moment.

@dankcushions I just played through the entire first mission without it crashing. This definitely fixed the problem. Thanks a lot!

@retropieuser555 I don’t have that camera bug. I remember reading a couple threads about that either here or on reddit. I can’t remember if there was a fix or not.

Aside from the buzzing noise, the only “problem” I have is the resetting. After about 20-30 minutes of playing it gets laggy and then crashes.

It only works when the 'launch harpoon' message appears. Press left on the right analogue stick to trigger it.

So I just wiped InputAutoConfig.ini and started again.

When it's this:

; Keyboard_START [Keyboard] plugged = True plugin = 2 mouse = False DPad R = key(100) DPad L = key(97) DPad D = key(115) DPad U = key(119) Start = key(13) Z Trig = key(122) B Button = key(306) A Button = key(304) C Button R = key(108) C Button L = key(106) C Button D = key(107) C Button U = key(105) R Trig = key(99) L Trig = key(120) Mempak switch = key(44) Rumblepak switch = key(46) X Axis = key(276,275) Y Axis = key(273,274) ; Keyboard_END

the game works perfectly, but keyboard only - WASD and cursors and a few others.

When I add this:

; usb gamepad _START [usb gamepad ] plugged = True Start = button(6) A Button = button(1) B Button = button(2) X Axis = "hat(0 Left Right)" Y Axis = "hat(0 Up Down)" ; usb gamepad _END

the keyboard stops working and the Start, A and B buttons all map to the proper buttons on the arcade joystick, (and button 5 quits back to EmulationStation) but the stick itself does absolutely nothing.

Those X and Y axis lines are taken from some semi-gibberish here:

https://retropie.org.uk/docs/Nintendo-64/

where it says *"Note for configuring Arcade Joystick or non analogue controller to use N64 correctly.
Changing the below inside /opt/retropie/configs/n64/InputAutoCfg.ini

From X Axis = "hat(0 Left, 0 Right)" Y Axis = "hat(0 Up, 0 Down)"

To X Axis = "hat(0 Left Right)" Y Axis = "hat(0 Up Down)""*

But none of those lines, with or without quote marks, make the joystick do anything at all.

If I change it to:

; usb gamepad _START [usb gamepad ] plugged = True Start = button(6) A Button = button(1) B Button = button(2) DPad D = hat(0 Down) DPad U = hat(0 Up) DPad L = hat(0 Left) DPad R = hat(0 Right) ; usb gamepad _END

nothing changes. The stick still does nothing, whether I put quotes round the hat commands or not.

What in blazes do I need to do to make the dumb emulator recognise the stick?

@mitu got it. sounds like I need to upgrade my GPU then

here's what your looking for https://www.reddit.com/r/RetroArch/comments/syi2ae/i_f_you_need_help_with_dk64_emulation_on_glide64/

This has been accepted and merged on GlideN64 master branch, so the game should be fixed when updating from source on RetroPie setup.

@retropieuser555 Superb - hopefully I've got a good one then!

@quicksilver thank you so much, that's all I needed to know

@george-spiggott funnily enough, this week I started using my old GameCube controller for n64 games on Retropie. Using an 8bitdo gbros adapter, have to say am very happy with the setup

Having gone back to my old pre 5.4 build Retropie I found I needed to downgrade my Kernel due to glitching graphics. Since I have done this I am convinced that Retropie, especially N64 is still running slightly smoother than it did before.

The quick menu does not let me remap the controls, but the retroarch menu does. There is one problem with that, though: it uses the right analog as the c-pad for the n64, and there is nothing that the d-pad in retroarch does.

@mitu said in N64 emulator doesn't save any settings:

you need to save a game or core override after you've changed the parameters

Can you please tell me where I can find the Overrides-menu? Or which solution would be the best?
When I switch the "Use Global Core Options File" to OFF, then I still the the same problem.

@dankcushions @mitu Nevermind, I figured out the problem. I didn't configure it right. My apologies for bumping posts.