RPI4: Kodi version update, N64 stuttering, no rumble pack

Cyber

@mitu thanks - with lr-mupen64plus it works without stuttering, but it looks much less nice. :-(
so is this a RPI4 performance issue or is this an emulator issue? If I try overclocking the PI4, what should I overclock to have the missing percent in performance? :-)

Thank you!

Best regards
Alois

mitu

@cyber said in RPI4: Kodi version update, N64 stuttering, no rumble pack:

If I try overclocking the PI4, what should I overclock to have the missing percent in performance? :-)

For N64, it's the GPU overclock that has an impact.

EDIT: another thing to check in the core options if it's set the framerate - if it's set to fullspeed (display refresh rate) or original (30 fps for Mario Kart).

Cyber

@mitu can you please point me where the core options are located?
as also overclocking gpu (with gpu_freq=750 and over_voltage=4) did not remove the stuttering I tried today:
-) complete new retropie-buster-4.6-rpi4.img on SD: in the default configuration of this image the stuttering is slightly better. I think on trying it in April I did not try all tracks. especially bigger tracks are affected.
-) other emulators. I am now with mupen64plus-GLideN64-highres which does the job currently best. I changed in /opt/retropie/configs/n64/mupen64plus.cfg to 1920x1080 and currently (with overclocked RPI4) I have perfect video and audio.

Also the black stripes which were visible in the menu disappeared now.

of course, the real test will be tomorrow where the kids are allowed to play again, maybe they can find a track which does not work.

nevertheless I would like to look for the refresh rate thing you mentioned. ;)

thanks for your help and time.

Best regards
Alois

dankcushions

@cyber i suspect it's the hybrid filter - disable it via https://retropie.org.uk/docs/RetroArch-Core-Options/#setting-core-options

It's a recent-ish addition to GLideN64 that allows better upscaling (less uneven pixels), but appears to be a major performance hit. if you set this to False the performance issues go away (even at 1080p).

It was later fixed in the RetroPie script, so a new image should be better, but previous installs and updates from older images will require this manual fix.

EDIT: note this fix is only for lr-mupen64plus-nx. i believe standalone should have it disabled, but you can always check by searching for 'hybrid' in mupen64plus.cfg

Cyber

@dankcushions thanks.
I tried to disable the hybrid filter, did not help, still stuttering.
on filesystem I found: /opt/retropie/configs/n64/mupen64plus.cfg : https://pastebin.com/DR6wNmt1
I think this is the one which is used for mupen64plus-GLideN64-highres ?

/opt/retropie/configs/n64/mupen64plus.cfg.rp-dist : https://pastebin.com/YTVkVDbB

/home/pi/RetroPie-Setup/scriptmodules/libretrocores/lr-mupen64plus-next.sh

I can see at the end of the script:

    if isPlatform "rpi"; then
        # Disable hybrid upscaling filter (needs better GPU)
        setRetroArchCoreOption "mupen64plus-next-HybridFilter" "False"
        # Disable overscan/VI emulation (slight performance drain)
        setRetroArchCoreOption "mupen64plus-next-EnableOverscan" "Disabled"
        # Enable Threaded GL calls
        setRetroArchCoreOption "mupen64plus-next-ThreadedRenderer" "True"
    fi
    setRetroArchCoreOption "mupen64plus-next-EnableNativeResFactor" "1"

The Threaded Renderer seems to be also enabled by default, which is also disabled in my case.
Where are those configparts written, and at which values should all of them be? So I can compare mine with them to get the latest state.

Thanks.

Best regards
Alois

dankcushions

@cyber so mupen64plus-GLideN64-highres will only perform same or worse to mupen64plus-GLideN64, as it's got double the resolution. you should first try with mupen64plus-GLideN64.

on filesystem I found: /opt/retropie/configs/n64/mupen64plus.cfg : https://pastebin.com/DR6wNmt1
I think this is the one which is used for mupen64plus-GLideN64-highres ?

yes, this configures both GLideN64 and GLideN64-highres. it looks ok to me but I can see that it has been modified. for example

# Screen aspect ratio (0=stretch, 1=force 4:3, 2=force 16:9, 3=adjust)
AspectRatio = 2

Is not the default, which makes me worry other things have changed...

EnableHybridFilter = True

You need to disable this, as I said.

you should also try updating mupen64plus from source.

/opt/retropie/configs/n64/mupen64plus.cfg.rp-dist : https://pastebin.com/YTVkVDbB

this is the backup of the default .cfg used by retropie, created on installation. it is not the one used by your install, which is your previous pastebin. don't worry about this for now.

/home/pi/RetroPie-Setup/scriptmodules/libretrocores/lr-mupen64plus-next.sh

this is the launch script for lr-mupen64plus-next.sh, not mupen64plus-GLideN64/-highres.

The Threaded Renderer seems to be also enabled by default, which is also disabled in my case.

where are you seeing that it's disabled?

Cyber

@dankcushions I changed the AspectRatio by hand to 2.

I can see the Threaded Render disabled in the RetroArch Core Options menu. The Hybrid Filter was there enabled, I disabled it. This did not change the Audio issue.

I will update mupen64plus from source now. I only used it "from binary".

Best regards
Alois

dankcushions

@cyber

@dankcushions I changed the AspectRatio by hand to 2.

I can see the Threaded Render disabled in the RetroArch Core Options menu. The Hybrid Filter was there enabled, I disabled it. This did not change the Audio issue.

but these are two seperate emulators - the mupen64plus.cfg controls the mupen64plus-* emulators. the lr-mupen64plus-* emulators are the ones with the Retroarch menu. one does not affect the other.

Please be specific which emulator you are testing - lets deal with one at a time. i would expect mupen64plus-gliden64 to be the fastest so lets test with that one. please show me your cfg from that when it has my suggested settings and still doesn't work.

Cyber

@dankcushions I am testing from this menu either the lr-mupen64plus-next and the mupen64plus-gliden64-highres: https://1drv.ms/u/s!AnFpCl7HpNVtg9szmP2o3-F5I2lTxQ

I have selected there now the first one (lr-mupen64plus-next).

I cannot find any config files "lr-mupen64plus*" - thats why I took now pictures of the settings which I can see with the retroarch core menu:
https://1drv.ms/u/s!AnFpCl7HpNVtg9s3sr_EwOEzchjJRw
https://1drv.ms/u/s!AnFpCl7HpNVtg9s2ejenqrrrORMhew
https://1drv.ms/u/s!AnFpCl7HpNVtg9s10tfvMXtuttTlPA
https://1drv.ms/u/s!AnFpCl7HpNVtg9s0Up0aFFn_PBBQ7A

I have installed specificly from source:
main -> mupen64plus (installed from source on 8th Dec. 2020)
main -> lr-mupen64plus-next (installed from source on 8th Dec. 2020)
main -> lr-mupen64plus (installed from source on 8th Dec. 2020)

graphical issues: compared with mupen64plus-gliden64-highres I have e.g. in the menus black lines: https://1drv.ms/u/s!AnFpCl7HpNVtg9s4IPgzfQ90i32wrQ

another graphical difference compared with mupen64plus-gliden64-highres: the "virtual screen" in the game.
https://1drv.ms/u/s!AnFpCl7HpNVtg9s6_uDDdldFcDGyJQ
vs.
https://1drv.ms/u/s!AnFpCl7HpNVtg9s551Xt1kDkeSYDDA
look at the in-screen game over the both "oo" from Mushroom. Once it is only black and white (lr-mupen64plus-next), once it is a screen-in-screen (mupen64plus-gliden64-highres)

is there a configuration issue in lr-mupen64plus-next ? hopefully I have now all options on the photos.

the RPI4 is running with over_voltage=4 and gpu_freq=750. Have now cooled it with an additional cooler, as I saw on playing it is reaching over 80 degrees and started throttling. it is now constand below 62°C.

sorry for beeing confusing. Hopefully you can help me.

Thanks
Best regards
Alois

dankcushions

@cyber said in RPI4: Kodi version update, N64 stuttering, no rumble pack:

I have selected there now the first one (lr-mupen64plus-next).

I cannot find any config files "lr-mupen64plus*" - thats why I took now pictures of the settings which I can see with the retroarch core menu:
https://1drv.ms/u/s!AnFpCl7HpNVtg9s3sr_EwOEzchjJRw
https://1drv.ms/u/s!AnFpCl7HpNVtg9s2ejenqrrrORMhew
https://1drv.ms/u/s!AnFpCl7HpNVtg9s10tfvMXtuttTlPA
https://1drv.ms/u/s!AnFpCl7HpNVtg9s0Up0aFFn_PBBQ7A

i don't think there's much point testing lr-mupen64plus-next as it's going to be slower than standalone, but there's a few settings you can change:

native resolution factor = 1x
Overscan = Disabled

be mindful to change only these, and exactly these. some others are named similarly.

graphical issues: compared with mupen64plus-gliden64-highres I have e.g. in the menus black lines: https://1drv.ms/u/s!AnFpCl7HpNVtg9s4IPgzfQ90i32wrQ

comparing what to what? please be specific. if it's to lr-mupen64plus-next, again this is not optimal. use mupen64plus-gliden64