Mupen64 Plus Next 2.1 Incoming

[quicksilver]

Awesome! I have been keeping an eye on the progress for a while now, glad to see it's available. I can't quite figure out how to get the native res factor option to work though. I'm still getting terrible scaling artifacts.

[saccublenda]

I updated lr-mupen64plus-next from source in retropie, and it shows 2.1 version, along with the new options.

[George Spiggott]

@quicksilver said in Mupen64 Plus Next 2.1 Incoming:

I can't quite figure out how to get the native res factor option to work though. I'm still getting terrible scaling artifacts.

Same here. I'm a little confused as to how this relates to the other resolution options. I'm also not seeing any benefit from the threaded renderer.

[quicksilver]

@George-Spiggott said in Mupen64 Plus Next 2.1 Incoming:

@quicksilver said in Mupen64 Plus Next 2.1 Incoming:

I can't quite figure out how to get the native res factor option to work though. I'm still getting terrible scaling artifacts.

Same here. I'm a little confused as to how this relates to the other resolution options. I'm also not seeing any benefit from the threaded renderer.

Yea I feel like the threaded renderer made a big difference with standalone mupen64plus but I'm not feeling the difference in this case (to be fair I haven't done extensive testing yet, so this is just my initial impression). I think the native res factor option is working, but for some reason it still looks really bad compared to standalone mupen64plus.

[Brunnis]

@quicksilver I’ve tested the threaded renderer with Shadows of the Empire and it provides a major improvement. Went from a total stutter fest, to running very well.

[George Spiggott]

@Brunnis That was my go to game to try. Could you elaborate on your setup please?

[Brunnis]

@George-Spiggott Pi 4 with no overclock in a Flirc case, running on a 1080p TV. GlideN64 render resolution set to 320x240. Before threaded rendering, even the scrolling text intro sequence would have some pretty major audio stuttering.

Edit: I should add that I’m running kernel 5.4 and the full KMS driver. I also tested the threading before release, by building from the dev branch. Will test again with the stable version.

[saccublenda]

I didn’t notice major differences too, although I tested only Super Mario 64 and Ocarine of Time. Also enabling and disabling the hybrid filter doesn’t seem to change much.

[quicksilver]

@Brunnis said in Mupen64 Plus Next 2.1 Incoming:

I should add that I’m running kernel 5.4 and the full KMS driver.

Any drawbacks to using that setup?

[saccublenda]

@quicksilver Kodi won’t work until version 19 is out.

[George Spiggott]

That sounds like a big jump. Even my overclocked GPU stutters a little with SotE in 240p. It sounds like it may be possible to run SotE in 480p and will certainly extend the number of games that run well in 480p.

[dankcushions]

native res doesn’t work properly on this core. the dev is aware, but i might formally log.

because of that, i still recommend mupen64plus-gliden64 standalone.

[George Spiggott]

What is it supposed to do that increasing the resolution doesn't do already?

[Brunnis]

@quicksilver said in Mupen64 Plus Next 2.1 Incoming:

Any drawbacks to using that setup?

I hadn't really found one previously, but after updating everything yesterday (kernel 5.4.49, apt update/dist-upgrade, RetroPie), I ran into two problems:

• Low framerate (30 FPS) in ES again. Hadn't seen that even once since switching to 5.4. No idea why it would show up again now...
• No audio. Tried enabling the new ARM side HDMI driver. This resulted in getting audio in ES but not in RetroArch.

Didn't really have time to look more into it (and will probably just wait out stable releases of this stuff).

[dankcushions]

@George-Spiggott said in Mupen64 Plus Next 2.1 Incoming:

What is it supposed to do that increasing the resolution doesn't do already?

the preset resolutions don’t pair up with all n64 games, which have all sorts of resolutions, often multiple resolutions per game. so if you set it to 320x240 it looks horrible in games like goldeneye that are above that, but if you raise it to 640x480 you force games that are below that to render above, causing graphical issues, or at least worse frame rate. and then for any game that is not a factor of the preset resolutions (many): ugly scaling.

it’s a really silly way of choosing rendering res for n64 and an in an ideal world it wouldn’t exist, tbh.

[akamming]

Hi,

just tried the new mupen64plus next. The good news is I was (very) positively surprised by the speed when switching on threaded video. Good work developers!

The bad news is, the screen is not ok, the emulator is not filling the full screen, and there is garbage on the lower part of the screen:

i tried a lot of things

• set config back to retroarch.cfg.rp-dist
• trying several resolutions
• switch 4:3 to 16:9 and vice versa
• switch shaders on and off
• switching overlays on and off

but all games remain having this issue. Does anyone know how i can fix this? I would really like to use this new version!

some additional info

• issue doe not occur in the regular mupen64plus or lr-mupen64plus or any other libretro core
• I am running on a rpi 4b using official retropie build (with this emulator compiled from source)

[Ric]

@George-Spiggott Hello George I have a security question: I have added the line pi ALL=(ALL) PASSWD: ALL editing the sudoers "sudo nano /etc/sudoers". It is ok for me but, I would like to know how to avoid the sudo password request at shutdown. Thanks!

[quicksilver]

@Ric how is this relevant?

[Ric]

@quicksilver I would like to keep the password request for any sudo command after F4 (on terminal mode) but, I would like to don't ask for password when I was just playing on emulation station mode and I shutdown using the menu quit option with my gamepad.

[quicksilver]

@Ric what I mean is how is your problem relevant to the topic in this thread? You should start a new topic instead of hijacking an existing one.