Mupen64 crashes, PLEASE HELP

[2000brix]

I downloaded a Pokemon Stadium rom for the n64, but when I run it on my GameShell using mupen64 the screen goes black and the game crashes. I tried downloading an updated version of mupen64, but for some stupid reason I cannot find it using RetroArch. Is there a way to actually run n64 games on the GameShell?

[javelinface]

Hello there! Welcome to the forums.
Seems like you’re not alone with trying to get mupen64plus to work.
It needs a whole bunch of dependencies that don’t come included.
It doesn’t use Retroarch. From what I’ve gathered, they aren’t maintaining the Retroarch core anymore for arm7hf. I’ve looked into downloading an older version and running, but haven’t had much luck. I’ll keep trying regardless!
I’ve made a post here with a script that should make everything work.

GameShell OS image files (v0.5)

Welcome to the forums. Re: mupen running, It needs some dependencies. Unfortunately, mupen never really worked out of the box. The auto config doesn’t work, unless you have the dependencies already installed. If it’s a new installation, then chances are they won’t be. It’s also not the most user friendly interface, re: setting things up. You’ll need to do most of it manually. Think of it being included as an easter egg for testing purposes. Try running this script; wget -O /home/cpi/mupen.sh…

If you have trouble with that, I’ve got a custom image that I’m maintaining with mupen64plus pre installed, along with a bunch of other things.

Custom D.E.O.T. V2.0+/Clockwork OS v0.5 image - With customised DEOT interface, Kernel 5.7, Optional 1400MHz OC, Debian 10 Buster, Retroarch 1.9.0, Mupen64+ plus more! (Current build: 200903)

Similar to my previous DEOT custom build based on 0.4, I have put together a new image, based on the ClockWork OS 0.5. This is the same as the official 0.5 image, just with a lot of updates, and quality of experience optimisations. You don’t need the DEOT edition Gameshell to use this. The official DEOT image is much older, and behind the official 0.5 image. This custom image is the bridge to get the best of both worlds. [b7d679edaee7a55ad42147c9085b5e919824296a_2_462x500] Here is a google dr…

Of course, this will unfortunately mean wiping everything. So definitely try doing it all manually first.

Re: pokemon stadium in particular, I’m guessing you’re using the western release, which is actually the Japanese Pokemon stadium 2.
Pokémon stadium (2) has some texture problems where menu items, and trainee faces appear as garbled text; kind of like MissingNo. This is something I remember happening years ago when trying to emulate it on a PC. I think I was using Project 64 back then. Anyway, menus and trainers aside, the game will run. I haven’t thoroughly tested how all the mini games work etc, so do post your findings.

[2000brix]

Hmmm. ok. I will see if I can back up the previous image and my Pokémon saves, and download your image

[2000brix]

So, firstly I attempted running your script, through my Mac’s terminal (after I had sshed into the GameShell, of course ( ͡° ͜ʖ ͡°) ), BUT IT STILL CRASHES LIKE BEFORE. Is there a special way you need to execute the program? I feel slightly uneasy reformatting the SD card with your image, especially with my 7 hour Pokémon Yellow saves on there.
Heres what was outputted in my Terminial:

output.txt

[javelinface]

Try typing this into your ssh session:

mupen64plus --resolution 320x240 --fullscreen /home/cpi/games/mupen64/pokemon.n64

(Rename your rom to something simple without spaces for now, otherwise you’ll need to type “Pokemon\ Stadium\ (USA)\ 1.12.n64” if it’s called “Pokemon Stadium (USA) 1.12.n64”)

It sounds like you ran the script to install the dependencies to completion. Did you try the rest of the script to modify the action.config and config file?

Also check this thread. This person had a similar problem.

Mupen64 - N64 Emulator running

Ah, well! That’s what I call very playable. I think it’s just the shadows that are in Kokiri forest that are graphically stupid. Once you’re out of there, it’s all good. Eg, the first dungeon basically plays flawlessly. So yes! That’s how it is basically is my response! As for making the icon, mupen64plus isn’t actually in the cores folder, since it’s not a core that’s used with retroarch. Here’s what you can use though: (change the name to your rom file name obviously) mupen64plus --resoluti…

[2000brix]

Hmmm. I ran the script, and this is what was outputted:
Linux clockworkpi 5.2.0-rc4-clockworkpi-cpi3-00001-gac0d4e8 #1 SMP Mon Jun 17 18:02:55 CST 2019 armv7l

/////_/////_////_
//_//_//_//__
//_/////_//_
//_//_//_
/////_//______////_

---

Welcome to clockworkPi

For more information please visit:
(had to cut out link, new user)

HAPPY HACKING

Last login: Fri Apr 3 18:41:43 2020
cpi@clockworkpi:~$ mupen64plus --resolution 320x240 --fullscreen /home/cpi/games/mupen64/pokemon.n64

---

| / |_ _ _ __ ___ _ __ / /_ | || | | _ | |_ _ ___
| |/| | | | | '_ \ / _ \ '_ | '_ | || || |) | | | | / |
| | | | || | |) | / | | | (_) | | __/| | || __ \
|| ||_,| ./ _|| ||_/ || || ||_,|_/
|| https://mupen64plus.org/
Mupen64Plus Console User-Interface Version 2.5.9

UI-Console: attached to core library ‘Mupen64Plus Core’ version 2.5.9
UI-Console: Includes support for Dynamic Recompiler.
Core: Using full mem base
UI-Console Error: couldn’t open ROM file ‘/home/cpi/games/mupen64/pokemon.n64’ for reading.
cpi@clockworkpi:~$ mupen64plus --resolution 320x240 --fullscreen /home/cpi/games/mupen64/pokemon.z64

---

| / |_ _ _ __ ___ _ __ / /_ | || | | _ | |_ _ ___
| |/| | | | | '_ \ / _ \ '_ | '_ | || || |) | | | | / |
| | | | || | |) | / | | | (_) | | __/| | || __ \
|| ||_,| ./ _|| ||_/ || || ||_,|_/
|| https://mupen64plus.org/
Mupen64Plus Console User-Interface Version 2.5.9

UI-Console: attached to core library ‘Mupen64Plus Core’ version 2.5.9
UI-Console: Includes support for Dynamic Recompiler.
Core: Using full mem base
Core: Goodname: Pokemon Stadium (E) (V1.1) [!]
Core: Name: POKEMON STADIUM
Core: MD5: 31EE2DE8E65E30F5934C450DBAA924F0
Core: CRC: 91C9E05D AD3AAFB9
Core: Imagetype: .z64 (native)
Core: Rom size: 33554432 bytes (or 32 Mb or 256 Megabits)
Core: Version: 1449
Core: Manufacturer: Nintendo
Core: Country: Unknown (0x150)
UI-Console Status: Cheat codes disabled.
UI-Console: using Video plugin: ‘Mupen64Plus OpenGL Video Plugin by Rice’ v2.5.9
UI-Console: using Audio plugin: ‘Mupen64Plus SDL Audio Plugin’ v2.5.9
UI-Console: using Input plugin: ‘Mupen64Plus SDL Input Plugin’ v2.5.9
UI-Console: using RSP plugin: ‘Hacktarux/Azimer High-Level Emulation RSP Plugin’ v2.5.9
Core: input plugin did not specify a render callback; there will be no on screen display by the input plugin.
Input: 0 SDL joysticks were found.
Input: N64 Controller #1: Using manual config with no SDL joystick (keyboard/mouse only)
Input: 1 controller(s) found, 1 plugged in and usable in the emulator
Input Warning: Couldn’t open rumble support for joystick #1
Input Warning: Couldn’t open rumble support for joystick #2
Input Warning: Couldn’t open rumble support for joystick #3
Input Warning: Couldn’t open rumble support for joystick #4
Input: Mupen64Plus SDL Input Plugin version 2.5.9 initialized.
RSP: RSP Fallback disabled !
Core: Using video capture backend: dummy
Core: Game controller 0 (Standard controller) has a Memory pak plugged in
Core: Game controller 1 (Standard controller) has a Memory pak plugged in
Core: Game controller 2 (Standard controller) has a Memory pak plugged in
Core: Game controller 3 (Standard controller) has a Memory pak plugged in
Core: Using CIC type X103
Video: Disabled SSE processing.
Video: ROM (CRC 5de0c991b9af3aad-50) not found in INI file
Video: Initializing OpenGL Device Context.
Core Error: SDL video subsystem init failed: No available video device
Core Status: Rom closed.
cpi@clockworkpi:~$

[2000brix]

I will also run the installation script again

[javelinface]

Ah!! This was was an assumption, but are you using clockwork OS 0.5? I’m not sure what new gameshells ship with, but if you didn’t flash a new image, there’s a chance you’re not using 0.5. That resign of the OS introduced some fixes allowing the Lima drivers to work better.

It will still run on 0.4. It just will be ridiculously slow.

[2000brix]

Hm. ill try to update it

[2000brix]

Ok. so there was an update I will try again…

[2000brix]

Also, is it possible to run DS/2DS/3DS games on the GameShell?

[2000brix]

So, I updated the OS to the latest version, ran the “mupen64plus --resolution 320x240 --fullscreen /home/cpi/games/mupen64/pokemon.n64” script but it still crashes.
At this point I am willing to wipe the SD card and burn your custom launcher into it.

[javelinface]

Don’t forget there’s an edit button.
Do you know what Kernel you’re using? You need to be using at least 5.3.6. If you have Clockwork OS 0.5, then you’ll have it. I wasn’t quite sure what you meant in your post re “So there was an update” - But keep in mind, a lot of people seem to have trouble with the update from 0.4 - 0.5

Okay. So the updating of the OS to the latest version. That ALSO doesn’t include mupen installed correctly. You’ll still need to install the scripts I mentioned before. The command line I gave you was assuming that the script installed it to the /usr/local space. The mupen included with the stock image is not stored there, so it won’t work. It didn’t crash per se; rather, just returned to the launcher, since it couldn’t find the file you were referencing.

You can definitely save your saves etc from all your other games, for when you write a new image. You can also just go and buy a spare SD micro card for fairly cheap. They even sell them at my local post office.

Yes you can play DS games. Just keep in mind, you’ll need to reconfigure a lot of it yourself, potentially connecting it to an HDMI display in order to read the UI font, because it’s so small.
It won’t be able to play any 3DS or 2DS games. Heck, my MacBook pro can barely keep up with emulating 3DS/2DS, so I doubt the gameshell would fare any better.

At this stage, judging by the number of problems that are plaguing you, it might just be easier to try my custom image. It also has a DS emulator pre installed.

Hopefully you’ll get it working.

[2000brix]

Thanks for all of your help. Oh, and by “there was a update”, I meant there was an update to the Launcher. The version I am running now is stable 1.25. I have a few micro SDs lying around, so I will probably burn the custom launcher into one of them.
TYSM

[2000brix]

Ok. so two hours ago, I have been trying to install your custom OS on the GameShell, BUT for some reason I cannot burn the actually image into the SD card. I can’t find a software that can actually flash the image into the card, probably bc I am on Mac and when I wipe the card it is still in FAT16. Any recommendations?

[javelinface]

One that lots of people here use is Balena Etcher.

balenaEtcher - Flash OS images to SD cards & USB drives

You will also need to decompress the .gz file to have an .img file ready to write.

I personally use either Apple pi baker, or a command prompt. But use what everyone else uses first.

I think I know what you’re trying to do. Are you just copying files to the SD card? This image doesn’t do that, although seeing as some other distributions for other devices can, it could be something to look into! Eg NOOBS on raspberry pi. You shouldn’t have to format your card. The image will overwrite everything, sector by sector on the card, including partition tables.

[2000brix]

Ok. So what the problem was was that when I went into Balena Etcher, I thought the SD card that I had plugged in was my computers hard drive. But now that I looked up the SD card and saw that it was disk3, I finally realized that the disk in Balena Etcher was my SD. Besides, by default the program does not allow you to flash to your HDD unless dangerous mode is enabled. I was so stupid