Aha good! Sounds like you’re making progress.
Did you manage to change the permissions, and run that script? It will take a very VERY long time. Like half an hour maybe?
Ah unfortunately, the version number of the launcher hasn’t been updated or changed in a long time. Even if you do update it via the launcher’s settings menu, the launcher version doesn’t change. It’s kind of useless right now, unless you’re using my custom image, which does contain the build number.
What would be the most useful to know is what the kernel version is. That should be enough information to go by in order to tell you of mupen64plus will be able to run well. You should be able to find it on the same screen that you saw the version number. Either that or potentially the OS IMAGE version could be useful, although I haven’t really paid much attention in the past.
Im not sure which file you’re talking about re: the mupen Zip file, but you won’t need that. A lot of the time, we can get precompiled binaries, and just run them from wherever. This isn’t the case with mupen64plus. You need dependencies.
Are you talking about the mupen.sh file that I linked? That’s the one that you put in ‘/home/cpi/‘ and what you need to run in order to install the dependencies. It also installs the mupen binaries to ‘/usr/local/binaries/‘ which is reportedly makes it run faster for some games.
There is one that the Gameshell automatically tries to install to ‘/home/apps/emulators/‘
This is the one that downloads when you put a rom into the ‘/home/cpi/games/n64/‘ directory and try to run it. It downloads a zip file and then decompressed it, leaving the zip file behind.
This is determined by the action.config file. It also tries to reference the mupen64plus file in the ‘/home/apps/emulators/‘ directory.
We aren’t using that one anymore, if you want it to run well, so we should should delete both the mupen64plus binary in the ‘/home/apps/emulators/‘ , the zip file that you mentioned, and overwrite the old action.config file with the one provided. In fact, you shouldn’t even need the mupen64plus binary that I have provided, since it’s now installed to ‘/usr/local/bin/‘, just like Retroarch.
I think you have the action.config file sorted, if you have overwritten the existing one with mine.
Very close! This config file will need to be placed in ‘/home/cpi/.config/mupen64plus/‘ making a note of capitalisation.
I probably could write up an entire script to automate the entire process. In fact I was going to once upon a time, but ended up just making up an entire custom OS with it pre-installed. I guess the problem was, I was having so much difficulty trying to convey how to get mupen64plus set up with a couple of users in particular, that I just gave up on trying to make a mupen specific script.
Let me know if you would like me to, and I can give it a bash.