Search Results for 'n64'

[waddupbeazt]

Hi,

I have an issue setting up my wired xbox 360 controller to work.

It works in the menus without problems.
The Xbox 360 driver is installed and checked with lsusb.
I have tried editing the controller to use input-up-btn = “h0up” etc.
Have tried to go through the setup in console.

When trying out some games only the ABXY buttons work and sometimes start and select.

I have also tried to reinstall everything.

Important notes; I am somewhat new to linux commands and raspberry pi.
I have followed several guides to perform this controller installation but it does not work.

My goal is to have it working on N64, SNES and GBA emulators. Can this be done with 1 single config file?

Thanks in advance!

[nemo93]

Hi NF3RNO,

here is the link (http://www.raspberrypi.org/forums/viewtopic.php?f=78&t=58395) :) and the link to the Git Repo (HERE).

Could you please share your config files and perhaps the pre-compiled binaries? Do you know if it’s possible to quit the emulator by pressing a controller button (or a combination)? Finally do you have a compatibility list or some thoughts as I’m curious to know what you meant by “mupen64plus-rpi works pretty well” :)

Thanks a lot!
cheers,

[NF3RN0]

In addition, I would like to point out that the newest build of the mupen64plus-rpi works pretty well. I am testing roms ATM and adding them to the compatablilty list, some need configuration to work.

[NF3RN0]

Not sure why but it did not let me post the link. Just search for wip mupen64plus-rpi and you will find the topic on the raspberry pi forums.

[NF3RN0]

Hello. I can help you out there. All you have to do is cd into the mupen64plus directory and then: sudo ./build.sh

After that completes then: sudo ./install.sh

Thats it, make is already in the build and install scripts.

More info on the emulator progress can be found here:

[ranem123]

anyone found the solution for n64 . The Games not starting !

[zsprawl]

[quote=12925]When I run the command above, everything is great, but it is asking me to configure more buttons than my controller has. I am using an SNES style controller, but the button values look like something for an n64 controller or similar. Am I ok to just pick any old button to get through the buttons I don’t have on the controller, or is this an indication that controller isn’t being recognized properly?[/quote]

I have the same issue. I just pick a button like left paddle for all of these buttons/controls that I do not have.

Then open up the file, and delete those lines.

sudo nano /opt/retropie/configs/all/retroarch.cfg

[ryan]

When I run the command above, everything is great, but it is asking me to configure more buttons than my controller has. I am using an SNES style controller, but the button values look like something for an n64 controller or similar. Am I ok to just pick any old button to get through the buttons I don’t have on the controller, or is this an indication that controller isn’t being recognized properly?

[Anonymous]

I don’t think anyone is having much luck with N64 recently:

N64 problems

All recent versions that I have tried that have worked have been very choppy and are generally unplayable.
Some promising progress is being made however in Mupen64plus as detailed here:

Mupen64plus (ricrpi branch)

…so watch this space…

[donbandito]

Good evening,

i really like this project, and respect the time you spent working and optimizing it. I Built my own case and had some fun playing some SNES games with Friends. Well N64 would be even more fun.

my Raspberry Pi (Model B, with 512mb RAM) using the retropie image 2.2. Wont boot any n64 roms.

unfortunatelly the log doesnt told much about the problem (just rom closed):
Image of the log

hope you guys can help me find a solution! :)

Greetings, and sorry for the grammar

[ribenickel]

i would like to try but i am new with unix so all this build, make, install… stuff is a little confunsing. So i just write down the my steps please tell me if i do sth wrong:

$ sudo su //i am lazy
 $ cd /opt/retropie/emulators/
 $ git clone (https://github.com/ricrpi/mupen64plus) //without brackets
 $ cd ./mupen64plus
 $ ./build.sh
 $ make && install ./ 

when i do build.sh it starts but then throws an error 403 while accesing github.com/ricrpi/mupen64plus/info/refs ????

Did anybody here encounter the same?

[gizmo98]

Mupen64plus-rpi is deprecated. Mupen64plus (https://github.com/ricrpi/mupen64plus) is the successor. If this emulator runs better we should replace the current one.

[smatticus]

no luck with n64 since 2.1. they barely worked on 1.9 so i’m giving up. i was floored with how well castlevania: sotn runs considering how choppy some snes games can run. must just be the emulators.

[Langy]

I can confirm n64 does not launch roms from within ES. Launching the emulator direct from command line does work however. I’ve poked around with how es_systems.cfg launches n64 but can’t get it to work.

Also on the retropie image SegaCD is looking in the /home/pi/RetroPie/ directory for the retro arch core. Editing the Segacd entry within es_systems.cfg to point to opt/retropie/….. fixes this.

[zsprawl]

I have had zero luck playing N64 games. The ones that load are slow, choppy, and otherwise not worth it.

[Sam]

I’m running the latest version of RetroPie (2.1) and the N64 emulator doesn’t even boot. The files are all .v64 and .z64, which work fine everywhere else but none of my N64 roms even start up. I’ve tried Banjo-Kazooie/Tooie, Legend of Zelda OoT/MM, Mario Golf/Tennis, Star Fox, and Conker’s Bad Fur Day and have gotten nothing.

Is Mupen really just that buggy on the RPi that it won’t run most games at all?

[ribenickel]

hi i just copied the 2.2 Image on my rasbi(rev2). The Menu is just awesome. But i cant get N64 Emulation working. It seems to start the display is blurring but then i fall back to emulationstation. After reading the error it says sth like:
Stopping Emulation at 3286
Core status Rom closed
I already tried different versions of roms z64, n64, v64 but always the same ist there an additiaonal config or bios necessary for n64 Emulation or what can help?

[DingDong]

bumping this as I am having the same problem with the N64 emulator. Also cannot seem to get the menu and save slot functions working in psx after editing the config file.

[hulkhaugen]

Ok, i had the 1.9.1 version up and running a while back, but hit quite a few problems, got busy doing other stuff and forgot most about it. So yesterday i installed the new 2.1 version, and what an improvement. I’m impressed ;) NES, SNES, SMS and SMD working great. Mame4all, got MK1 running, but not joystick only keyboard works, but not start, and analog stick instead of d-pad. N64 not working at all. So to list the challenges:

1. N64 games doesn’t start. I can see the roms start to load, and everything seems ok, the resolution changes, but then it quits and goes back to ES2. If i quit right after, i can still read the loading sequence.

Core: Starting emulation 1945
Core: Starting R3400 emulator: Dynamic Recompiler
Core: Init new dynarec
Core Status: Stopping emulation.
Core: R4300 emulator finished.
Core: Stopping emulation at 3200
Core Status: Rom closed.
Powering on HDMI with preferred settings

2. /opt/retropie/configs/all/retroarch.cfg, this seems to be set up only for keyboard, but it does work with joystick also. Well, except for Mame4all. And i want to configure a hotkey combination to exit games. Is there another config file i’m missing?

3. The Mame roms (this is thin ice for me) have several versions. MK1 only has one version and does work. But MK2 has a r14 and a r32 zip-file in addition to the mk2.zip, and also three listings in ES-Mame. None of them work. Same with MK3. EDIT: I’ve now tried several other games that work, and i usually keep the main version, even though there usually are another us and japan version. Is tat correct? Seems like some games needs more than one rom file. They are 0.37b5.

4. Minor issue, but the scrapper seems to have issues with dashes. for instance pac-man can’t be located, but i do find it when i check online.

[matt1980]

after finally getting everything up and running i added roms to various folders to see if this wuold show the other emulators in emulationstation. However, the 5 emulators showing genesis,ports,macintosh eyc remain the same and n64/snes etc are still not showing. Would anyone be able to assist? im very nw to pi and its been a struggle to get this far to be honest so any help would be greatly aor appreciated. sorry for spelling mistakes…..my delete keys not working. Ha!

[zantos]

i dont think it will work on pii
even the n64 emulator dont work properly

[Anonymous]

Hi there, welcome to the forums!

Firstly here is a compatibility list for the emulator.
https://code.google.com/p/mupen64plus/wiki/GameCompatibility

This is for the original emulator and does not show compatibility for the emulator running on raspberry pi.

I would suggest trying a a few games if you have them, then you could determine if it is just that game or if its a configuration problem.

[njisage]

ok I have been going threw my network to add roms but I need to getusing filezilla or think its called cyberduck this way I can see all the files and add the themes and also the bios that are holding me up from plying neo geo and GBA I even made the gpSP folder but cant get to it to add bios I know their is a way to do it command line but i am about a week or two into Unix and this is a whole new world for me right now.Let me know… oh yeah also cant get my MAME to run or my N64 the N64 will start to load then all the script getsreally small and blurry and then well it boots back to the main screen.

[zSprawl]

I had to change the accepted extensions in the ~\.emulationstation\es_system.log to allow for v64, but it really doesn’t matter since n64 emulation on a Pi is horrible……

[Job]

Changing the file extensions to N64 works

[kitchuk]

Try using it on your PC. If it still works there then it’s something to do with the pi.

Sent from my GT-I9300 using Tapatalk

[kitchuk]

Is it connected? If it’s plug and play then it should just work. Might be dead?!

Sent from my GT-I9300 using Tapatalk

[evoion44]

Okay, so here’s what happened.

So, I start up my retropie for the first time, and the n64 usb controller works fine, it’s mappable, it’s configurable. Then, I rebooted it, in hopes of putting my roms onto it. My controller would no longer responding. Why is this happening?

[chris102994]

Okay so iv had the raspberry pi for about a month and iv been fooling with this retro-pie arcade project on and off for the whole time. It absolutely will not work. Iv looked through forums, others problems and everything. I have installed via image burner on my PC and iv installed via Raspbian. The biggest problem I face is that the keyboard stops working for some reason (its not the keyboard, iv tried 5 different keyboards and all the same problem). Ok so I reset the pi until I somehow manage to log in and get to coding. I can finally expand and download drivers for controllers and keyboard works fine (for a few keystrokes after reboot) so I get it to controller config and it finally recognizes my PS3 controller. I set it up and there’s an error. After a few quick searches I find out why (that I cant use it on certain emulators well certain keys). Anyway I get it done and I go to install a ROM via flash drive. And SURPRISE it doesnt create a ROM directory in the flash drive. Ok so I do some reading and I figure out about how the folders supposed to be so I create a rom folder and within it I put a n64 folder with 3 different games in it. (rom’s work, iv tried it on my pc’s emulator). Only 1 actually copy’s over (the pi still hasn’t made other folders on the directory). I load into the game and I get a script page… I wait about 5 minutes and it keeps glitching every 2ish minutes to a different frozen screen. Ok so I decide to try a new rom installment method via WinSCP. Now when I boot my retro-pie the keyboard doesn’t even respond to anything. The Pi works fine with any other OS. But it will not work with retropie. I cannot find anyone else with this problem. Is there anything I can do or anyone that has had the same problem that can help me? Thank you.

[helistorm]

Hey guys,

I´m running a RetroPie Raspberry Pi Rev. B with the Retropie GPIO Adapter and a SNES controller. Everything works just fine. Now I want to connect a PS3 controller via Bluetooth for PS and N64 games etc.. As Bluetooth dongle I´m using the ASUS BT 211 model and it is connected via powered a USB-HUB. I followed the installation guide, but I get an error while compiling Sixaxis:

pi@raspberrypi ~ $ cd QtSixA-1.5.1/sixad
pi@raspberrypi ~/QtSixA-1.5.1/sixad $ sudo make
mkdir -p bins
g++ -O2 -Wall -Wl,-Bsymbolic-functions sixad-bin.cpp bluetooth.cpp shared.cpp textfile.cpp -o bins/sixad-bin pkg-config --cflags --libs bluez -lpthread -fpermissive
sixad-bin.cpp: In function ‘int main(int, char**)’:
sixad-bin.cpp:84:20: warning: taking address of temporary [-fpermissive]
sixad-bin.cpp:89:18: error: ‘close’ was not declared in this scope
sixad-bin.cpp:100:20: error: ‘sleep’ was not declared in this scope
sixad-bin.cpp:109:22: error: ‘close’ was not declared in this scope
sixad-bin.cpp:117:22: error: ‘close’ was not declared in this scope
sixad-bin.cpp:140:18: error: ‘close’ was not declared in this scope
sixad-bin.cpp:144:14: error: ‘close’ was not declared in this scope
bluetooth.cpp: In function ‘void do_connect(int, bdaddr_t*, bdaddr_t*, int)’:
bluetooth.cpp:104:30: error: ‘close’ was not declared in this scope
bluetooth.cpp:110:24: error: ‘dup2’ was not declared in this scope
bluetooth.cpp:111:22: error: ‘close’ was not declared in this scope
bluetooth.cpp: In function ‘int l2cap_listen(const bdaddr_t*, short unsigned int, int, int)’:
bluetooth.cpp:148:17: error: ‘close’ was not declared in this scope
bluetooth.cpp:162:17: error: ‘close’ was not declared in this scope
bluetooth.cpp: In function ‘void l2cap_accept(int, int, int, int, int)’:
bluetooth.cpp:195:26: error: ‘close’ was not declared in this scope
bluetooth.cpp:201:26: error: ‘close’ was not declared in this scope
bluetooth.cpp:221:26: error: ‘fork’ was not declared in this scope
bluetooth.cpp:228:32: error: ‘dup2’ was not declared in this scope
bluetooth.cpp:229:30: error: ‘close’ was not declared in this scope
bluetooth.cpp:242:57: error: ‘execve’ was not declared in this scope
bluetooth.cpp:254:26: error: ‘close’ was not declared in this scope
bluetooth.cpp: In function ‘int l2cap_connect(bdaddr_t*, bdaddr_t*, short unsigned int)’:
bluetooth.cpp:274:25: error: ‘close’ was not declared in this scope
bluetooth.cpp:291:25: error: ‘close’ was not declared in this scope
make: *** [sixad_bins] Error 1

Any ideas how to fix this error ?
The PS3 controller was also connected via the powered USB-HUB the whole time.

[mookystank]

I’m building a RetroPie for my brother’s graduation present, and I’m running into issues with the N64 emulator. Now, I’ve read that N64 emulation is pretty difficult for the pi, but what’s throwing me off is how effortlessly it seems to be running PSX games. I’ve tried various different suggestions from the internet, including reducing the memory split to the GPU (which, annoyingly, also resulted in failure to properly load themes) and overclocking with various specs, but nothing seems to improve much of anything. I either get a frame every 3 or 4 seconds, or I am treated to glitchiness, with half-rendered objects and flashing black frames. At this point, I’ve got everything back to default to keep from creating new problems.

Is there anything to be done about this? Has anyone successfully run this emulator through EmulationStation?

[trimmtrabb]

Cool, glad you got it working :-) A lot of the emulators are Libretro cores which can be configured through the Retroarch frontend with retroarch.cfg

You may want to create custom controls for each emulator, place a modified retroarch.cfg in the respective emulator folder, e.g. for Megadrive/Genesis place in /home/pi/RetroPie/configs/Megadrive/ this will override the default retroarch.cfg in /home/pi/RetroPie/configs/all/

To determine buttons you can run jtest which should be installed already, if not:

sudo apt-get install joystick

Then run:

jstest /dev/input/js*

(replace * with the index your pad is assigned)

Other emulators have their own config files.

As for Duke Nukem and Game Gear emulators I don’t use either, so you’ll have to search that one. I’m sure you can run Game Gear roms through the Megadrive emulator though?

The N64 emulator requires the Pi to be overclocked and will only run a few roms at a decent speed.

[venkatrl]

Hello,

Thank you so much – that was very helpful. Nearly all of my emulators now recognize the 360 pad.

The only remaining issues are with the Duke Nukem Emulator (which starts but only allows joystick control for menus but not gameplay). I will search the forums to see if this is a known issue.

Additionally, there are a few remaining issues that may or may not be related to joypad conflicts (Game Gear works flawlessly for a few games but then later fails to open those same games… Additionally, the only N64 games that boot only make it to the opening screen). Again, I will look for the appropriate forum to search / post these issues (unless you can direct me off the top of your head).

I appreciate your help!

Best,

Venkat

The Game Gear emulator (which used to work) now produces a black screen

[gizmo98]

I’m not sure if RetroPie works out of the box. You need at least a hard float distribution. It should be a debian derivate like ubuntu or raspbian. There should also be gpu support. Banana pi uses an armv7 soc. So some files should be updated:

https://github.com/retropie/RetroPie-Setup/blob/master/retropie_setup.sh
current:
__default_cflags=”-O2 -pipe -mfpu=vfp -march=armv6j -mfloat-abi=hard”
armv7:
__default_cflags=”-O2 -pipe -mfpu=neon -march=armv7 -mfloat-abi=hard”

Emulationstation requires gcc-4.7, SDL2 and /usr/lib/libEGL.so.

Many emulators are optimized for armv6 or the videocore of the raspberry pi soc. With a fast armv7 soc you could use common libretro cores like bsnes-libreto or mupen64plus-libretro:
https://github.com/libretro

[phipix01]

If you guys don’t allready know, there is a Banana Pi coming soon. which has significantly more performance:

Dual Core

1GB DDR3 RAM (RPi has 512MB DDR2)

SATA Port

Android OS Support (tons of games :D)

…

Imagine yourself running the OS and all of your ROMS on a SATA Drive, which has higher Data Transfer Rate while Overclocking that little baby’s dual core to 1.4GHz.
N64 and PSX ROM’s shouldn’t be a problem anymore i guess.

My question now: what has to be adapted on the retroPie Image to use it?