n64 muppen64plus next began to slow down

dankcushions

@iga
i see the issue - you needed to reinstall lr-mupen64plus-next AFTER you deleted all the entries in that core options file.

for example:

mupen64plus-next-EnableNativeResFactor = "0"
mupen64plus-next-EnableOverscan = "Enabled"
mupen64plus-next-HybridFilter = "True"
mupen64plus-next-ThreadedRenderer = "False"

are not how retropie would configure these. please delete all the entries again, and immediately reinstall it.

sirhenrythe5th

Using composite out on a Pi4 does saddly reduce performance anyhow :(
I also love to use the Raspberry Pi with a CRT using the composite output and it worked perfect with Pi 1,2 and 3.
But with the Raspberry Pi4 it sucks soooo much, i hope it will be better again with the Pi5 (or 6,7,...)

IGA

@dankcushions Yeah! It is!! Bingo
Thanks alot and everybody thanks!!!

why is so hard reinstall it correct? And why it's happened at all?

IGA

@sirhenrythe5th

@sirhenrythe5th said in n64 muppen64plus next began to slow down:

Using composite out on a Pi4 does saddly reduce performance anyhow :(
I also love to use the Raspberry Pi with a CRT using the composite output and it worked perfect with Pi 1,2 and 3.
But with the Raspberry Pi4 it sucks soooo much, i hope it will be better again with the Pi5 (or 6,7,...)

Why do you think that? -on the contrary, to play old games on modern tv via hdmy, to achieve more good-looking picture your need to increase the resolution to x2, x3, .... or use shader, what takes more resources of pi, then you run at 320x240 (720x480) on crt and it's looks well as original. For example - dreamcast - your dont need increase resolution on composite, so most games work on the fullspeed without overclocking and looks well in native resolution on crt tv) ( ofcourse original dreamcast via vga was cooler, but suppose my meaning is clear)

Or maybe i dont know something....? ( cause i dont has p 1,2,3)

dankcushions

@iga said in n64 muppen64plus next began to slow down:

@dankcushions Yeah! It is!! Bingo
Thanks alot and everybody thanks!!!

why is so hard reinstall it correct? And why it's happened at all?

it's tricky - the emulator has its own defaults, and for most systems the defaults it chooses are correct, but for pi we have limited performance so need to curate the settings - we do this when installing emulators or updating them.

however, there was a widow when these settings existed in the emulator, but we hadn't set the correct defaults in retropie yet. that was when the initial retropie pi 4 image was built (i'm not sure about the current one), so the defaults would be the (bad) emulator ones. if you update after that, retropie won't overwrite your existing settings because we don't want to wipe out any personal configurations you have made.

so the long and short of it is, to get the settings correct, you need to manually adjust or wipe the settings and reinstall. i don't see a way around that as it wouldn't be write to force such optimization settings on users every time they update (there are reasons why you might want to change them)

mitu

@dankcushions said in n64 muppen64plus next began to slow down:

i don't see a way around that as it wouldn't be write to force such optimization settings on users every time they update (there are reasons why you might want to change them)

Or maybe just go into Core Options and change settings (which I assume this is how the issue got triggered) ?

dankcushions

@mitu said in n64 muppen64plus next began to slow down:

@dankcushions said in n64 muppen64plus next began to slow down:

i don't see a way around that as it wouldn't be write to force such optimization settings on users every time they update (there are reasons why you might want to change them)

Or maybe just go into Core Options and change settings (which I assume this is how the issue got triggered) ?

no i don't think they manually set the 'bad' settings - like i said, depending on what image was started from they could have been already set, and the script won't override settings that are already there, and if you delete them then you're not running the script so it will just go back to the retroarch defaults (which are the 'bad' settings as above, i believe).

but yes, you could manually fix them also :) -

you need to manually adjust or

IGA

@dankcushions said in n64 muppen64plus next began to slow down:

o the long and short of it is, to get the settings correct, you need to manually adjust or wipe the settings and reinstall. i don't see a way around that as it wouldn't be write to force such optimization settings on users every time they update (there are reasons why you might want to change them)

All right, as i understood, before next updates at first need delete all core settings in retroarch-core-options.cfg ? ( or not update at all)

dankcushions

@iga yes, or manually adjust the core options to the 'best' ones, via the RGUI or the file.

for the record the retropie default settings are:

mupen64plus-next-EnableNativeResFactor = "1"
mupen64plus-next-EnableOverscan = "Disabled"
mupen64plus-next-HybridFilter = "False"
mupen64plus-next-ThreadedRenderer = "True"

the latter 3 are set for rpi only (although i would guess they would be useful for most SBCs), and the native res factor of 1 is set for all platforms.

( or not update at all)

no, like i said:

however, there was a widow when these settings existed in the emulator, but we hadn't set the correct defaults in retropie yet. that was when the initial retropie pi 4 image was built (i'm not sure about the current one), so the defaults would be the (bad) emulator ones.

if you updated or had an image from before the defaults were setup, then you would get the 'bad' settings.

IGA

@dankcushions Ok, now i see, thanks