Search Results for 'n64'

[peter]

asbesto, this is what I did:
I opened my FTP client and connected to my PI. in /home/pi/RetroPie/roms I created a new directory called _unused * and then I moved all direcotries(=systems) that I don’t need into the _unused directory (e.g. atari, n64, msx, etc.). that’s it. there is no need to change any config files.

alternatively, I could have deleted all directories, but this solution seemed to be more appropriate since if I ever want to put up some N64 or Atari stuff onto my PI, I simply move back the belonging folder and don’t have to worry about how it was called.

* the _ prefix is simply to have this directory stay on top in the roms directory when I connect via SFTP to transfer stuff

[draik161]

So I can’t get any roms to run on the Nintendo 64 emulator… Though I can get playstation 1 ROMS to work? I know the Raspberry Pi is capable of running them I just think the N64 emulator is broken? Anybody know? Thanks for replying in advance.

[chrisdem]

I have been workin on settin up my system here and I have gotten to n64 and none of my roms will launch. I get the command line in two different screen resolutions and kicks back to menu. I have been reading the forums and apparently this is a common thing but I don’t see the solution.

IF someone could please tell me how to solve this issue I would be quite happy

[trimmtrabb]

I don’t think the gpu needs any more than 256 memory, the most demanding emulators (Playstation and N64) don’t need any more than 128 and ES requires 256. There’s a thread over at Raspberrypi.org that may be of interest: http://www.raspberrypi.org/forums/viewtopic.php?f=78&t=80674

[jassinlive]

The latest 2.3 pre-installed image white screens during boot when I have N64, PSX, GBA or MAME roms and BIOS installed. There is a whole thread on it for more detail.

RetroPie white screens during loadup with certain roms installed

[loomdog32]

Thanx for this awesome guide!!

I was able to get my controllers working with minimal effort (once I found this) in 2.2.

4 questions.
1 – When using the HDMI, after closing a game, I get “invalid format” on my TV and no video. I have to reboot the pi to get video again. When using the composite video, it works great!!
2 – I keep seeing talk about pressing F1 while inside a game to open a menu… Nothing on the keyboard works inside the game.

3 – The long shot, but I’m hoping someone has an answer. Tetrishpere on N64. This is the only N64 game I want to get up and running. The emulator never opens. Has anyone had any luck with this??

4 – I noticed after getting everything setup with 2.2 that 2.3 was released. I did a search and didn’t see a direct answer on doing on in-place update. Is this possible and if so, how?? Im hoping that I missed something and a simple link answers this question.

[retchron]

Im having the same issue. I have some nes, snes and n64 on there now. But when I try to add anything else it white screens on load. As soon as I delete those files it boots up just fine. I have expanded the filesystem, that was my first thought too though. It says I have 11G available.

[gizmo98]

Your swapfile is too small. Try this:

Mupen64plus (ricrpi branch)

[viralriver]

On the build I get the following error:

*****************Changing branch from master to ric_dev for mupen4plus-core
Branch ric_dev set up to track remote branch ric_dev from origin.
Switched to a new branch ‘ric_dev’
Not enough memory to build
Please set CONF_SWAPSIZE to >= 404 in /etc/dphys-swapfile and run ‘sudo dphys-swapfile setup; sudo reboot’

This is after a lot of ‘cloning’ it just stopped with the above message. I SCPed into the mupen64plus directory under home, but couldn’t find any directory called ‘etc’. Any advice?

[jassinlive]

Hello

I am still very new with the RetroPie game and have come into an issue. Whenever I try to install roms for specific emulators (MAME, Gameboy Advance, N64) the RetroPie boots into a white screen. As soon as I remove these roms and reboot the Pi it loads fine.

I am successfully running roms on a handful of emulators including the GBC, NES, SNES, Ataris 2600, Genesis and Megadrive. My sixasis controller also loads and plays fine over bluetooth.

Is there an obvious step I may have overlooked? Is this a common issue? I cannot find anything with whitescreen.

Cheers

Sam

[Anonymous]

Bump
I’m suprised that this issue has not been resolved and there are 3+ posts about it. From what i have read the guy who was forking the build from official repos has depreciated the project so it’s not as confusing.
The build process is the same, but I can’t test it on the RetroPie right now>

To setup, run the following commands:

sudo apt-get install git # to install git if you don’t have it.
git clone http://github.com/ricrpi/mupen64plus # to clone the repository
cd mupen64plus
./build.sh # to build the binaries and shared libraries
sudo ./install.sh # to install mupen64plus into /usr/local/bin

You can also try reading my post on the bottom of this page if it won’t compile. Like I stated I haven’t had a chance to test.

[gizmo98]

Mupen64plus is slow at the moment. In my opinion the only playable game is mario64 and the PI will never be fast enough to emulate n64 games at full speed.
zelda ocarina of time –> too slow, graphic corruption
paper mario –> slow, hangs

[mlegower]

Tried to install from source last night. Finished, but said mupen64plus could not install, see debug.log. I don’t know where to find debug.log, so I don’t know why it failed. Any suggestions?

[mlegower]

I will try to install mupen64 & ES from source on a fresh image of RetroPie tonight. I’m also going to temporarily make the memory split 16MB, just in case memory was the problem (I think I had it at 256 before). I’ll report back on the results.

[viralriver]

I managed to open a z64 rom running the following command:

mupen64plus /home/pi/RetroPie/roms/n64/poke.z64

(it’s Pokémon Stadium)

mupen plagued the terminal with audio errors and then I heard “Pika!” and the rom started playing. Some audio files were missing, a lot of the graphics were missing, and wow I have never seen something so slow, it’s pretty much unplayable. Also, as it’s not through ES, my gamepad wasn’t mapped so couldn’t do anything – anyone know how to fix this? If not, is there any news on ES using a ‘better’ 64 emu?

[gizmo98]

Mupen64plus takes approx. 1-2 hours
Emulationstation 30-45 min.

How much space is left on your sd card? mupen64plus needs 750MB memory for compilation. The pi has only 512MB ram. So the swap file is resized at runtime from 99MB to 512MB. If there is not enough space we cannot resize the swapfile.

[mlegower]

Trying a source based installation of mupen64 now, but it seems to be hanging on something. Last line logged is:
LD mupen64plus-video-rice.so
and it has been stuck there for at least an hour. Is that normal?

[gizmo98]

Press “F4” and type:

cd RetroPie-Setup
sudo git pull
sudo ./retropie_setup.sh

select “source based installation”
select mupen64 and emulationstation
build and install

[mlegower]

Please update retropie-setup and reinstall mupen64plus & emulationstation.

Can you indicate precisely how to do that?

[viralriver]

Hi, I have recently installed RetroPie using the latest image onto an 8gb micro sd (I’m using a B+ pi).

Initially I transferred over some GB roms, and they work perfectly. I then tried some GBA roms, and they didn’t work but after transferring over the gba_bios file, they worked.

Finally, I now want to run N64 files but I cannot get them to work. I have transferred over Pokemon Stadium, and on selecting it in the ES menu, the screen resolution changes and then I get the message:

/opt/retropie/supplementary/runcommand/runcommand.sh: line 23: 2335 Segmentation fault ./mupen64plus /home/pi/RetroPie/roms/n64/Pokemon\ Stadium.z64

I have seen someone else posted this problem on this blog but no resolution was found. I tried to reinstall the mugenplus emulator via the retropie_setup.sh file, but it gave me an error after about 30 minutes of execution.

If anyone knows how to fix this please let me know! Oh and I’m not too confident with the terminal, so please explain everything thoroughly :P .

[gizmo98]

Please update retropie-setup and reinstall mupen64plus & emulationstation.

[K-Project]

The only feedback I’d like to add currently would be a massive thanks for this amazing project. I’ve had a massively enjoyable couple of days trying to get my head around things and get it working how I’d like. I have used Retropie in the past (last year), and I’m really surprised by just how far it’s come on. Essentially, I’m only really after solid working 8 bit and 16 bit systems, so things like PSX and N64 are not really what I expect of this unit and I haven’t indulged that side of Retropie. I’ll perhaps try that later on when the emulators have been developed further.

But I’ve pretty much managed to get it working just how I wanted. :) It’s become quite a little entertainment system, and much better than the cheapo retro consoles you can buy. I’ve just ordered a sexy new case for the Pi, along with 2 matching retro USB controllers and a Sonic the Hedgehog sticker for the Pi. Yes I’m old enough to know better, and I don’t care!

So thanks again. Donation to follow, when I get paid. :)

[wgrymo]

I just got a game to start, but it starts slow and i there’s no sound.
I navigated to /opt/retropie/emulators/mupen64plus-rpi/test, then i typed ./mupen64plus /home/pi/RetroPie/roms/n64/SuperMario64.n64 (the last being the rom filename obviously) . It started, but i could see audio errors being generated before the game came on screen. But i think this means that the startupscript from emulationstation must be wrong at some point.
When i start the rom with es it gives a seg fault on line 60, there is says ‘eval $@’ . Does that mean anything to anyone?

[Arnaud]

There is no runcommand.sh but it does perform a cd it seems

DESCNAME=Nintendo 64
NAME=n64
PATH=/home/pi/RetroPie/roms/n64
EXTENSION=.z64 .Z64 .n64 .N64
COMMAND=cd /home/pi/RetroPie/emulators/mupen64plus-rpi/test/ && ./mupen64plus %ROM%
PLATFORMID=3

[mlegower]

well, in the 1.- series of RetroPie, in the es_system.cfg the N64 part has no runcommand.sh in the text, and it worked!! (well just about)i
f someone has an old back up of the es_system.cfg have a look, I’ve not had a chance to try it with it removed in the new one yet, so if someone can, that’ll be great!

Also, I don’t have an old version of retropie, so I can’t try this, but it’s a good suggestion.

[mlegower]

Last night I tried removing the change directory command by just giving a path to the emulator directly. That failed because the emulator seems to look in the current working directory for a core library (which obviously wasn’t there since I removed the cd command).

There is a –corelib option on mupen64plus which allows you to specify a path to the core library. I also tried that (with the path implied by the previous error). That also did not work, although I could not diagnose why because it had changed the display settings in the interim to make the console output tiny.

I hope this is all helping someone with more skills than me.

[InsecureSpike]

see my post,

here

N64: Segmentation fault

[InsecureSpike]

also, in the 1.- series of retropie, the mupen64plus needed no runcommand.sh! have a look at a back up if you have one,

[InsecureSpike]

well, in the 1.- series of RetroPie, in the es_system.cfg the N64 part has no runcommand.sh in the text, and it worked!! (well just about)i
f someone has an old back up of the es_system.cfg have a look, I’ve not had a chance to try it with it removed in the new one yet, so if someone can, that’ll be great!

[wgrymo]

Hello,

I have been trying to get N64 to work, and I also encountered the segmentationfault. I read mlegower’s post about the ‘cd’ command. Just to know if there is an error here, we could just put a rom in the same directory. And see if the seg fault still occurs. I will try that this evening when i get home.

[Xboxclassic]

mlegowe wrote
I don’t see anything immediately wrong with it (for instance, the path exists on my system and there is a file called mupen64plus there), but I’m not an expert. I do notice that none of the other commands in the es_systems.cfg file perform a cd first and THEN a separate run command. Maybe that is the source of the error?

I think you may be onto the error here.
Now if only we could edit the es config file to correct the issue.
Doe`s any one know how to access it ? for RPI v.2.2
whats float around is rumors and deception of where and what it is called .
If you Know Please help the community.

As for mr9v9 asking
Why would you want to use an old version on the latest build? Especially with an updated script and different folder relocation.
it was just a suggestion seeing as the old version was working previous to the updated script.

[mlegower]

This is the command in emulation station that starts mupen64 and generates the n64 seg fault everyone is encountering.
/opt/retropie/supplementary/runcommand/runcommand.sh 1 "cd /opt/retropie/emulators/mupen64plus-rpi/test/ && ./mupen64plus %ROM%"
I don’t see anything immediately wrong with it (for instance, the path exists on my system and there is a file called mupen64plus there), but I’m not an expert. I do notice that none of the other commands in the es_systems.cfg file perform a cd first and THEN a separate run command. Maybe that is the source of the error?

[mlegower]

This is the command in emulation station that starts mupen64 and generates the seg fault.
/opt/retropie/supplementary/runcommand/runcommand.sh 1 "cd /opt/retropie/emulators/mupen64plus-rpi/test/ && ./mupen64plus %ROM%"
I don’t see anything immediately wrong with it (for instance, the path exists on my system and there is a file called mupen64plus there), but I’m not an expert. I do notice that none of the other commands in the es_systems.cfg file perform a cd first and THEN a separate run command. Maybe that is the source of the error?

[mlegower]

This is the command in emulation station that starts mupen64 and generates the seg fault.
/opt/retropie/supplementary/runcommand/runcommand.sh 1 "cd /opt/retropie/emulators/mupen64plus-rpi/test/ && ./mupen64plus %ROM%"
I don’t see anything immediately wrong with it (for instance, the path exists on my system and there is a file called mupen64plus there), but I’m not an expert. I do notice that none of the other commands in the es_systems.cfg file perform a cd first and THEN a separate run command. Maybe that is the source of the error?

[mlegower]

This is the command in emulation station that starts mupen64 and generates the seg fault.
/opt/retropie/supplementary/runcommand/runcommand.sh 1 "cd /opt/retropie/emulators/mupen64plus-rpi/test/ && ./mupen64plus %ROM%"

I don’t see anything immediately wrong with it (for instance, the path exists on my system and there is a file called mupen64plus there), but I’m not an expert. I do notice that none of the other commands in the es_systems.cfg file perform a cd first and THEN a separate run command. Maybe that is the source of the error?