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

@illmaticxking said in GLideN64 crashing back to EmulationStation for every n64 rom:

One other question that I've also searched but am not sure how to resolve. In non-Libretro cores, my hotkeys on my controller and keyboard do not work for opening the quick menu to adjust video, configs, etc.

That's because the Hotkey Enable button/functionality is specific to RetroArch/libretro. For each standalone emulator, you'll have to check what options for input are available and how/if they can be adapted to a 'hotkey' schema.

@llllllllllllll you can adjust the resolution factor in -next via https://retropie.org.uk/docs/RetroArch-Core-Options/#setting-core-options

If anyone else has this problem, it seems that InputAutoCfg.ini is what you are supposed to edit. Changing plugged to false just gave a no controller message. Since I didnt see any section for order, I changed the order of the controller configs but that didnt change anything. However just deleting the nes gamepad section worked and now my bluetooth controller is controller 1. It also stayed that way through restarting.

@hackedmacbook111 said in Mupen64plus-gliden64 from source is broken:

I used mupen64plus on pi3B+ and it freezes with glide 64 games have more lag than with impending 64 plus
I recently updated 4.5 to 4.6

Start a new topic, this issue has been solved and isn't the same as yours.

@Jste84 said in N64 (mupen64plus-GLideN64) performance fix:

My default emulator is lr-mupen64plus-next...

whoops, you're right. will update post

Should I change this? Or run the fix?

i think both. -next does not have a setting to reduce slowdown, so it will always be present.

@roxton looks like it's supported. I found a relevant post on the lr-mupen64plus GitHub.

https://github.com/libretro/mupen64plus-libretro/issues/16

There are instructions on there how to get it to work. Though whether it's still accurate or applies to a RPI setup I'm not sure.

@squishykoishi

am not using hires version and in fact locked the screen res for N64 games at 720x576

this can add lag as you’re forcing your tv to do an up scaling operation. see https://github.com/RetroPie/RetroPie-Setup/wiki/Input-Lag#use-hdtvs-native-display-resolution

retropie already runs (most) n64 games at 320x240 and then let’s SDL to a (fast) upscale using the GPU.

the rest of the input lag wiki may help you if there’s still an issue.

weird that gles2n64 etc fix the problem but they don’t have accurate emulation so may have incorrectly quick latency to start with? not sure

Sorry it took me a while to copy some roms over and check everything out but yeah they played normally.

@drrevan it's most likely an issue with the emulation then. Try it with a different emulator/plugin.

@dankcushions well there u go. So using glide is going to look pixelated. Using gles hi res will
Look much better but maybe under perform.

I’ve got banjo kazooie, Mario 64, Diddy kong racing, dk 64, Mario kart and star fox 64 running pretty decent on gles hi res now.

Waverace runs decent in rice hi res

Goldeneye barely passable on gles

Some overclocking done now. Guess I’m happy with where it’s at now then. Cheers.

@mankysteve I'm not sure where you read that but as an experiment I tried "Star Wars - Rogue Squadron (USA) (Rev A).n64" It runs with a lot of audio glitches and slowdown. I would not call it playable. I am using a Pi3 at stock settings and mupen64plus tested with all of the various plugins.
If you are determined to play it just mess around with the resolution and plug-ins using runcommand menu and see what feels best to you.

I've also noticed a problem with blending while I was helping to troubleshoot recent issues with missing textures, but I wasn't certain that the blending issue was an existing problem or something new, as I rarely test N64 emulation.

Legacy blending is disabled for certain games - including Zelda - here: https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/emulators/mupen64plus/mupen64plus.sh#L201

If you're familiar with editing files via SSH, you can edit /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh and try removing zelda from that blacklist to see if the problem is resolved. I'll take a look when I have some free time.

@mediamogul thank you, that answers my question

I've figured it out, after clean reinstalling Retropie all is working fine.
When I go to Retropie Setup and only update mupen64plus via core/main packages (didn't remeber the exactly one) the same issue comes back.

Anyone has an idea ?

Update: Ok i keep it up testing and there is one more thing.
If i did'nt update all works fine. After that i manual edited the mupen64plus.sh to that one which is used after updated mupen64plus package. From here the issue comes back again.
So it seems, there is a bug in the new mupen64plus.sh handeling the texture packages.