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

@adamg thanks for sharing this. I just updated to Buster and my old fix for mapping the generic n64 didn't work. Mapping a hotkey for the menu did the trick. Weird though, I only had to map my A and Z buttons, everything worked fine.

@ancapgamer said in How do N64 Hi-Res Textures work now?:

Also, they seem to be written primarily for the "mupen64plus" core - which as of the most recent time that I updated my pi4 is no longer available, having been replaced by the "lr-mupen64plus" and "lr-mupen64plus-next" cores.

lr-mupen64plus is the mupen64pus core (now superseded by lr-mupen64plus-next, I think you're confusing it with standalone emulator (which is named mupen64plus).

Multiple google searches have actually yielded a truly distressing lack of documentation. I haven't found anything remotely resembling a set of useful instructions. Does anyone know how you're supposed to get Hi-Res Texture Packs working now?

Standalone instructions https://github.com/mupen64plus/mupen64plus-video-rice or the docs page, libretro core(s) https://docs.libretro.com/library/mupen64plus/#hires-textures. The N64 opt page (here) has even a video linked with instructions for standalone Mupen64Plus (not the libretro core).

I agree that documentation could be more explicit, but should get you started. Maybe give more details on what have you tried so far and it's not working?

@zodiark12 that's right. the retroarch menu could definitely be more intuitive in this regard but yes there's unobvious demarcation between options for the emulator core itself, and those of wider retroarch.

So it doesn't appear to do this for lr-parallel-n64 or lr-mupen64plus oddly, so at a guess it seems there's something specific to those 2 cores.

@achillespilot Hey- I did get it worked out. What worked for me was lr-mupen64plus-next and video at 1920x1080 @ 60 Hz. The N64 logo when the rom launches looks like garbage but the intro and the game itself look great. Good luck!

David

@BuZz Just a heads up that libretro-uae accepted the fix and merged it to master.

It has worked!

In a bit more detail:

I didn't add entries for P3 and P4 on retroarch.cfg because, what would I set them to if I only have two controllers? 4 and 5, assuming that I could be plugging in additional ones?

Anyway, I tried to re-add the two physical Logitech controllers to EmulationStation; it detect 4 controllers, but it would keep detecting the button presses as coming from the emulated Xbox controllers.

I then reset the controller settings for EmulationStation on the Retropie menu and again, it would detect 4 controllers, but it also would keep detecting the button presses as coming from the emulated Xbox controllers.

I had to disable xboxdrv and then it would only detect 2 controllers and the button presses a coming from the physical Logitech controllers. The conclusion here is for EmulationStation the physical and emulated controllers don't clash; the emulated ones take priority and the button presses are understood to be coming from them.

I then checked that on the Retroarch menu the emulated controllers were assigned to P1 and P2 and removed the physical controllers that were assigned to P3 and P4. And then everything was fine. The crux here appears to be that I had a clash, as both the emulated and physical controllers were assigned to players and probably registering button presses. Something that support this hypothesis is that on games where you have a grid to select your character (e.g. Mario Kart) it was fairly obvious that when I was pressing once to move one cell to the right, for instance, the selection box was moving two cells.

Thanks again for all your time helping me figure this out.

oh hang on, you're using lr-mupen64plus, so that input file is redundant, as it uses retroarch configs.

in which case, you can have a look at the core options to see if there's anything relevant: https://retropie.org.uk/docs/RetroArch-Core-Options/

or core input remapping to rebind it completely: https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping

however for pi4, i wouldn't recommend using lr-mupen64plus at all - it has a lot of issues and is out of date. instead use mupen64plus-gliden64 with this fix: https://www.reddit.com/r/RetroPie/comments/gc83sc/n64_mupen64plusgliden64_performance_fix/

@badviper Would you please advise what steps I need to take to make my retrolink usb controller work with n64?

Do I need to use lr-mupen64plus-next? I selected lr-mupen64*-something*

Do I need to modify /opt/retropie/configs/n64/InputAutoCfg.ini?

Do I need to reboot or only restart emulation station?

I don't understand the GUI option for selecting a Select button since my controller doesn't have one but games need that, right?

Any other steps?

Thank you!

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

@felifel We don't support 3rd party images - is clearly outlined in the https://retropie.org.uk/forum/topic/3/read-this-first topic.
Use the image from retropie.org.uk/download to install, update your RetroPie installation and try again installing the emulator.

@chriso205 said in OOT + lr-mupen64plus n64 controller config:

Not sure how to access this retroarch menu?

Hotkey+x will open the retroarch menu while youre in game. Then go to controls and remap as you like and then you can save it as a core remap. Remapping here won't influence your mappings in the standalone emulator because it doesn't use the retroarch controls.

@spentboy I'm not seeing that I have mupen64plus-GlideN64-hires as an emulator option, nor is it anywhere in the optional packages. Am I missing something? (I do have mupen64plus-GlideN64, but it doesn't load the rom. And none create the htc file.

RetroPie on Ubuntu on an NUC8.

@mitu oh well, mupen64plus performance is very poor on my pi zero (even overclocked) so I suspect lr-mupen64plus will be even worse so its probably not worth my time to dig to much deeper with it :)

@snock said in small screen lr-mupen64plus-next:

I tried to delete retroarch.cfg in configs.

Why ? Open the RetroArch menu and check the resolution in the Video options - maybe use the one provided by the core and make sure scaling is enabled.

Ah. Figures it would be the one core I'm most interested in testing on the ODroid too. :) Oh well, at least it's a known issue and it'll get resolved eventually. Thanks!

I think I worked it out. A year or so ago when I originally set up my retropie I was focussing on PSX emulation, and in the "autoconfig" controller mappings I must have force mapped this:

input_up_axis = "-1" input_down_axis = "+1" input_left_axis = "-0" input_right_axis = "+0"

Removing these seems to have done the trick

@sl89 the repo moved a few years ago so maybe you installed before that.