Thanks for exploring this one - I assumed that my RetroPie upgrade had overwritten my retroarch.cfg files. The advice here has fixed my missing shaders in my install (a 64-bit Raspberry Pi OS install).
Running and updating the setup script, navigating
P Manage packages
U Re-install (from source)
has fixed the problem for me.
Hello, just curious about something I have never done until I have to with a new Pi model or mandatory change, which is start over again with a fresh install. How often do you do this?
Like others here, I also don't do it without good reason, e.g. when I switched from my Pi 3b to my new Pi 4 last spring. I also have customised my installation pretty much, so a new installation would require a good amount of re-configuration, even if most configurations can just be copied over from the old system.
I often wonder if so many updates through a package update eventually cause regressions.
RetroPie is built on Linux which in my long lasting experience doesn't "litter" the system over time as much as Windows does. You usually don't have to clean up or re-install a standard Linux system at all. As far as I can tell as a mere (power) user, RetroPie itself is also pretty neatly designed in the same way, so you shouldn't fear any regressions by just updating it via the RetroPie setup.
All that said, one important thing for any system is to back it up on a regular basis. Apart from failed updates or operating errors, every hardware can break any day for a number of reasons. See the Docs about Making a Backup.
Looking at the backup methods on https://retropie.org.uk/docs/Updating-RetroPie/ I think the best one for me in this situation is to backup the bios, configs, and roms directories via the samba shares. However, assuming the update works perfectly, which of these directories should I copy back over to preserve my roms, save states/files, and configurations (like controller configs and core-level configs). I'm assuming just the roms and configs directory and that I should not copy bios back over to the new image, but I wanted to check and be sure.
@shavecat To elaborate a bit (because I'm a little bored this evening): You pretty much don't ever need to be acting as the actual root user. Especially if you are new to Linux. There is a high chance of messing things up if you start working directly as the root user.
Instead, as we've mentioned, you should use sudo. But only when you need to! sudo stands for super user do. The super user is the root user. In other words: When you run a command with sudo in front of it, you are running it as the root user for just that one command. It's a nice way to elevate your rights temporarily when needed.
But I can't stress this enough: Don't run commands as sudo unless you absolutely have to! Any file or path that is created while sudo'ing, will be owned by root. And if that was not the intention, you will have issues later on, when the ordinary pi user tries to access those files or paths.
Ah ok, is there anyway I can reinstall the version that comes with 4.7 to see if it makes a difference?
Since PPSSPP isn't installed on the 4.7 image by default, even if you download the 4.7 image, installing from binary will still get you the current/last version. So, no - you can't reinstall the old version from RetroPie-Setup.
Ah, I never realised that. Sounds like I’m out of luck then.
The reason that Retropie isn't visible in the Win10 Network folder is due to the fact that netbios discovery isn't supported by windows anymore.
But it is possible to make samba shares again visible by the Web Services Dynamic Discovery Method.
I am currently using a little python3 script from Steffen Christgau on my Debian Buster NAS Server which makes WSD available und thus browsing Samba Shares much more conveniant.