@Unknown I have checked that and it says I've used 88% of my 64GB SD card. Does that seem to full to save an N64 rom? Thanks for the suggestion!

@dankcushions I see, makes sense then for my measurements as I do have the PAL version. But I'll stick to that. If there's a way to uncap the fps it won't matter anymore anyway. Thanks for the info though.

@mitu Thank you!!

@IceChes1 said in What will RetroPi run on a Zero W?: If SNES runs at 10 FPS on a Zero, I wouldn't be surprised if N64 emulation set it on fire. You can run SNES using the older snes9x cores and performance is acceptable as long as you aren't trying to run superfx games. Even psx performance on the pi zero is not bad using the standalone emulator.

@spacepilot7132 are you using an official RetroPie image? Anytime you have odd behavior you should turn off your overclocking and retest.

@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.

It appears that in /opt/retropie/configs/n64/InputsAutoCfg.ini that under the relevant controller there was no entry for B button, and A button was incorrect. I edited this manually to correct for this, but I still get the same problem when i run the emulator - e.g., my attempted fix makes no difference to how it actually performs!

@AlphaBetaPie said in N64 Not Cooperating on my Pie: I'm using a default official image. But I removed the default N64 emulator and switched over to Lr-mupen64plus-next (because for my set up, I absolute have to have the Retroarch interface). But I made backups. Could I fish those plugins out of the default mupen64plus folder? If so, do I just drop them in the current n64 folder to make them accessible to Lr-mupen64plus-next? how did you remove it? assuming you removed it via retropie_setup, just reinstall it via the same. it's in main > mupen64plus.

kodi addon is not maintained, no activity on github and no answer on github issue. so i want to find solution manually :)

@Kvitekvist if your display supports lower resolutions change the window size in the gles2n64.conf file to 640x480. Then when you launch a game, enter the runcommand menu before the game boots and change the default video mode for gles2n64 to 640x480.

@XaniXxable said in Rasp4 N64 window screen very small: So now to my porblem... If i run the n64 emulator called "mupen64plus-gles2n64" I have a very small picutre in the left corner of my screen. I set my retoarch settings to use 16:9. Also if i select a specific resoloution it wont apply it. known issue. see https://retropie.org.uk/forum/topic/25671/mupen64plus-gles2n64-small-screen-in-the-down-left With the other emulators like "mupen64plus-gles2rice", "mupen64plus-GLideN64-highres" and "mupen64plus-GLideN64" i get a bigger screen but only 4:3 ratiation and it's not play able. mupen64plus-GLideN64 should be playable. see https://www.reddit.com/r/RetroPie/comments/gc83sc/n64_mupen64plusgliden64_performance_fix/

Ok. Cannot be done :) Thanks for your reply.

@Brunnis he actually just added the option: https://github.com/libretro/mupen64plus-libretro-nx/issues/72 (not sure which branch, but i'm sure you'll figure it out)

Yes, the default image has the Megadrive/Genesis emulator installed and configured.

@henryjfry said in Certain systems dont work from NFS share: Would adding async to my fstab improve things do you think? The async option would be ok, but I don't know if it would solve anything. You can just try different mount options - the less mount options you have, the easier it would be to test different combinations.

@retropieuser555 the long and short of it is that framebuffer emulation is required for many games to function properly. There is a performance hit for having it on, but the alternative is that you'll have issues such as yours.

@KN4THX I had issues when converting with the specific folder name png files, Instead I installed retroarch on my android Ised the same core Next and then I just uploaded the generated HTC file the cache folder, ensure that you have the HighRes options enabled on the options

@BuZz That did it, thanks. Now I can unlock the framerate to fullspeed (60). I'll have to double check with mupen, but this might be able to run goldeneye at better speeds. F-Zero and other games are still crashing but that might just be the emulator.