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

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

@neek said in lr-mupen64plus-next and N64 controller input issues:

I also just wanted to chime in and say I bumped into this exact issue, and after hunting around for a few days, I found this thread and had it fixed in a few seconds. I appreciate you posting a follow-up for the community.. it helped me a lot!

+1 here, this solution made my day. Thanks a lot!

@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 can confirm this process worked for me! Thank you. Running Retropie 4.7.1 on raspberry pi 4.

However one tip I would add is once you run the libretro core you need to enable hi res textures in the retro arch menu. Quick menu -> options I believe.

I do have a question though. I was able to get the new textures working but they are still fairly pixelated. I have the resolution set to 1920x1080 from the runcommand configuration for mupen64plus-next. I’ve run the same hi res texture pack with glide64 in the past and it looked much better. I feel like I need to update the resolution somewhere else... Any ideas?

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

@quicksilver said in lr- core save/load states:

I must have misunderstood, I thought it was the 360 controllers

I appreciate the help. You're right we were talking about controllers but I also use an IPAC. Basically for old school you can use the arcade panel or you can plug in a wireless dongle and use controllers. Since it's separate input types it's pretty easy to get both working. I've haven't had many issues in the past.

I just started with a new build on Tuesday from 4.3 and patched all the emulators and core items like RetroPie, ES and Retroarch up to snuff. I think it's something I patched but I am not sure if it's a bug or something I inadvertently did myself. Hopefully someone will have an idea where to look.

THe standered emulator works ok with slowdown and glitches. The other emulators ether back out or just get sound. IDK why. The guy reccemended one emulator but it doesn't work for me.

Hi,

I'm trying to do this but I can't, and just found this post with no answers.

I can use hi-res textures with mupen64plus-gles2rice-highres and mupen64plus-GLindeN64-highres only:
· For gles2rice and GLindeN64 you must put the images (.PNGs) in /home/pi/.local/share/mupen64plus/hires_texture
· For lr-mupen64plus I found somewhere that you must use the .htc file generated by some Windows emulator, but I found that file also in Retropie inside /home/pi/.cache/mupen64plus/cache which has been created by GLindeN64 (at least with Super Mario and Mario Kart because others not) but I don't know where to put it. I've read it should be in the "cache folder", but defining it with RGUI and putting /home/pi/.cache/mupen64plus/cache folder, doesn't work...
· For mupen64plus-gles2n64 some works but others not.
· For lr-parallel-n64 and mupen64plus-videocore I don't know if you can use hi-res textures.

Any ideas?