@mitu

FYI, solved with help from the moonlight team.

https://github.com/moonlight-stream/moonlight-qt/issues/1563#issuecomment-2774382989

@MinivanDriver i noticed a ; too many in front of the name [USB Gamepad] in the /opt/retropie/configs/n64/InputAutoCfg.ini file

Example:

; InputAutoCfg.ini for Mupen64Plus SDL Input plugin

; USB gamepad_START
[USB gamepad]
[SWITCH CO.,LTD. Controller (Dinput)]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
Mempak switch =
Rumblepak switch =
R Trig = button(5)

Etc.

Remove it, and try it. I think it prevents the .ini to start the pad configuration

I first thought, can we use function copyDefaultConfig here when placing the file? Except, when I updated this last time it also added a couple new entries, which I suppose we would not want to miss out on.

You can't use copyDefaultConfig because the file is updated upstream and updates will not copy when a new version is added.

So could we use sed or something, then, to add the fix automatically? Or, why do we even have to do this manually, why is this just not the default already; is the glitch specific to a certain hardware/platform?

The default is the opposite (copyDepthToRDRAM=1), so it's clearly a platform (RaspberryPi / GLES3) glitch

[DONKEY%20KONG%2064] Good_Name=Donkey Kong 64 (E)(J)(U) frameBufferEmulation\copyDepthToRDRAM=1 frameBufferEmulation\N64DepthCompare=0

The launch script has some overrides for games, but copyDepthToRDRAM is not among the settings considered. Maybe it would be useful to have a GLideN64.local.conf and merge the settings from it in GLideN64.custom.conf, during installation/configuration.

@TPR Hey @TPR I am experiencing the same problem with my N64 roms. Did you end up fixing it? Thank you

@grazzii said in Trouble installing Mupen64 core:

Would installing the 32Bit system give better performance results in your opinion?

No, but it will consume less memory for the same tasks. You can stick with 64bit, but if you intend to use it also as a desktop computer then memory size may become an issue (regardless of the 32bit/64bit choice).

@dankcushions Thank you so much for the support. I thought it must be a video problem but if it is emulating like this (the way it is supposed to be) then it is no problem. I am pretty sure Mario Kart 64 was intended for CRTs as well so that is why there are those lines. I also run PSX and N64 at a low res so that they perform well. I will probably dump some PSX Bios and configure some settings so that I get access to all the benefits of the system.

Once again thank you to everyone's support.

@mitu

Thanks.

Such a pitty because vulkan works great on the Android images for this board.

I installed the blob drivers and indeed it looks like there is still no vulkan.

PS: Installing the libvulkan-dev package made mupen64plus compile 😊

@retropieuser555 @LLD correct in that audio cannot easily be addressed. I added the note about ScreenUpdateSetting = 7 in the sheet. Note there is also a comment in there for Perfect Dark from @George-Spiggott

Could also try Next/640x360 16:9 with MSAA Level 2 (recommended by @George-Spiggott RetroPie forums)

Forgive that my pi is offline (building lr-mess) at the moment, but I recall Perfect Dark could not be perfectly emulated with any system and there were some sacrifices with any proposed solution.

looks like this has been fixed upstream: https://github.com/mupen64plus/mupen64plus-core/pull/1027

source compiles should now work :)

thanks all for reporting! @mitu, thanks for reporting upstream, and @BuZz thanks for that, hopefully you can use later binaries, once fix is confirmed :)

@mitu

To circumvent the problem, I've just installed RetroPie via RPI's imager for now, as that will have to do.

Thank you for taking the time to look into the issue. :)

PS. Mega Man rules.

@DominicSD when you select the game it gives you a grey box asking you to press A if you wish change any resolution or emulator settings. If you press A then it should bring you to a menu and a list of emulators to choose from. If you're saying you've already tried Gliden and the others then that's the best the Rp4 can do for now for n64

@sleve_mcdichael mupen64plus-gles2rice = "49-36"

@retropieuser555 I got noticeably reduced framerate and frequent audio drop-outs with lr-next on a stock Pi4 w/ no overclock.

You may have more success asking in the RetroArch forums, this is a RetroPie dedicated forum, there's probably very few users using an Nvidia Shield here.

@mitu Thanks for the reply. I apologize, I'm rather new to using RetroPie on Ubuntu. I was just going by what the default value was on the emulator selection screen when you press a button while the ROM is launching.

9247c15c-3e81-4c7c-bd79-bea1c6087614-image.png

I ended up installing lr-mupen64plus-next as you suggested, and the difference is amazing :) This is what I was hoping for. Thanks!

Ah okay, so then what I tried is simply not possible then for this game in that emulator like that. Fully explained and understood now. Thanks! 👍

@mitu Ok i will try that and get back if I face the same problems. This is what I will do, I will install a debian 32 bit(somehow my tablet only support 32 bit uefi and can only detect 32 bit bootable linux distros). Then I just install retropi again through RetroPie-Setup.

@Drdave79 said in Mupen64plus-GlideN64 Control help:

It was just an observation that the non-next version, which apparently is no longer supported seems to work better.

No offence taken, and it's normal that is runs better, since the performance requirements are lower. This is why it's still available in RetroPie.