Search Results for 'n64'

[herbfargus]

I have a suggestion.

It will be easiest for you to wait for the next release of retropie which should hopefully be in the next month or so (I’m shooting for before Christmas)

Then configure your controllers as the diagrams suggest in the wiki

https://github.com/RetroPie/RetroPie-Setup/wiki/First-Installation#controller-configurations

And then to address your preference for the analog stick instead of the dpad there is a setting you can change from the retropie setup script for retroarch controller configs (the values are changed from 0 to 1) to make the controller use the analog stick instead of the dpad (I’ll make a wiki page with more info later when I have some time for more details)

Then as far as the n64 controls go those will be automatically configured for you with the next release of retropie as well.

[supersaiyancurry]

I know you guys have probably heard this a million times, but I’m new to Retropie. I have a general idea of what I’m doing though.

So, here’s the issue i’m faced with… I’ve been using a wired XBOX360 controller to play my games. When it asks me for manual configuration, I switch around the schemes for dpad and control stick. See, most of the games are programmed for me to use dpad instead of control stick. So, when I input the dpad controls like it asks me to, I have to rely entirely on the dpad for all these games. I WANT to use the control stick because it is much easier and more fun- so I disobey the instructions and switch them around.

Normally, this would be an easy work around to play the games the way I want to, but when I set the controls like this, NONE of the controls work for N64.

I have 2 choices.
1. switch the control pad scheme in setup with left analog so that all games except n64 use left analog (much more easy to play with than pad). N64 literally does not work for some reason if I do this.
2. setup control pad how it asks me to- which makes it so every console but N64 uses control pad. N64 now works, but every other console requires control pad which is difficult and not fun to control with.

I’m not sure why N64 stops working whenever I do this, but I shouldn’t have to choose between being able to play N64 and having fun playing every other console.

I want a configuration file specifically for N64 that overrides the original control scheme and makes it so the controller works how EmulationStation asked me to set it up. I’ve looked all over google for codes that would make this possible to no avail. It would be great if I could get a solution for this. Thanks!

[vwbuggsy]

How do I check the source of my roms? What do you mean by that? I think it’s against the rules to list exactly where I got them but it’s the same site I got all my NES and Sega ROMS that seem to work fine.

The rom files also worked fine when I had the version 3 beta 3 up and running. I know that’s not a sure thing but it indicates to me the ROMS can work.

I did NOT update the setup script before updating the n64 binaries. I’ll google instructions on how to do that, but please provide a link on how to do that if it’s not too much trouble.

I think it’s possible to configure more than one potential N64 emulator so I’ll also see if I can figure out how to switch between them and see if one or the other works better.

Thanks!

[herbfargus]

Check the source of your roms, did you update your setup script first before updating the n64 binaries?

[vwbuggsy]

Hey folks, I’m not too experienced with Linux or RetroPie.

I had a version of RetroPie up and running and working pretty well. You can see my PiTendo build in an original NES case on the “people’s projects” section. I had gotten the N64 emulator going and playing some Conker’s Bad Fur Day with a PS3 controller and life was good. That was on version 3.0 beta 3. Then I decide to do some updates (apt-get upgrade -y git and then apt-get install -y git dialog) and it hosed me up somehow and then nothing would work. I don’t think I’ll do that again :-)

Well, I was trying to get everything perfect so I could image that set-up and make several others to give to some of my buds for xmas… so I’m bummed. Me and the boys used to play multi-player on Conker’s all the time so I really wanted to get the N64 emulator working before presenting them, if I can.

So, today I’ve been trying to do a completely fresh build up using the 3.2.1 image. I thought it would be better to get a stable version. Things are going pretty well mostly. I’ve got my controllers working and NES/SEGA is running fine. When I try to run N64 now though, I get an error.

Sorry, I’m being long winded.

I’m using a Raspberry Pi 2 B
3.2.1 image
build from binary
using iBuffalo SNES style controller and Playstation 3 dual shock connected VIA wire
A basic generic USB keyboard
Guides and instructions mostly from Google and YouTube (a lot of stuff from floob who I’m not surprised to see is a frequent poster here).
Very little done at this point other than getting the controllers set up and adding some roms.

When attempting to run an N64 game I get a few lines of text telling me where errors are logged then it dumps be back to EmulationStation. In the log it tells me:
/opt/retropie/supplementary/runcommand/runcommand.sh: line 704: 2492 Segmentation fault /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/$

I have attempted to solve the problem by using the setup script to re-install the mupen64 and libreto mupen64 emulators VIA binary but that didn’t seem to do much.

Again, I’m a bit of a newb to linux but I’m actually a technical lead by profession so not a total idiot (just mostly LOL). I have started doing this stuff to try to get beyond the basics in Linux.

Here’s what happens if I try to start ANY n64 ROM (all of which worked for me in the beta version I was using earlier).

Press a key (or joypad button 0) to configure launch options for emulator/port (lr-mupen64plus). errors will be logged to [blah]
plugin_start_gfx_success
GfxRomOpen.
Init new dynarec
===========================================================

Then it dumps me back to EmulationStation.

Thanks for any help!

[candyluv]

I been trying to get the snes controller to work in n64 but can’t seem to get it working.I’ve tried playing around with the configs but always end up having to do over the image. It works in the main menu but not in the n64 games. Is there a way to rectify this problem, also I would like “start+select” as exit.
I would very much appreciate any assistance.
Thanks in advance.

[candyluv]

[quote=83136]I just got Mupen64plus to work on retropie(very laggy and lots of aufdio warnings and problems still come up, but it works). However, I now want to try and get my SNES controller to work on the Mupen64plus. I have tried making a SNES controller map for mupen in

/opt/retropie/emulators/mupen64plus-rpi/source/mupen64plus-input-sdl/data/InputAutoCfg.ini

also I found the same file in

/opt/retropie/emulators/mupen64plus-rpi/test

so I put it in there as well.I went and looked on how to make the profile for the controller but I have no idea if I did it wrong, or i put the profile in the wrong spot, or both. Does anyone know how to make the profile for the Snes controller?

[/quote]

Did you get it to work. i seem to be having the same problem?

[candyluv]

I been trying to get the snes controller to work in n64 but can’t seem to get it working.I’ve tried playing around with the configs but always end up having to do over the image. It works in the main menu but not in the n64 games. Is there a way to rectify this problem, also I would like “start+select” as exit.
I would very much appreciate any assistance.
Also, what are some CHEAP alternative that can play with all the emulators and easy to setup (auto if possible)?? Both USB and Wireless options.

Thanks in advance.

[sjo102784]

This resolved my issue for all emulators aside from the N64. Thank you so much!

[trust5]

Hi guys, just wondering if I’m able to set up some kinda of hierarchy for the controllers in each emulator? I’m wanting to leave my PS1, SNES and N64 controllers plugged in at all times and have the emulators prioritize the corresponding controller. Any info would be great!

Thanks
Sam

[dankcushions]

apparently this is now fixed (thanks to jools and stefan)! update retropie-setup, install individual emulators, and grab the latest mupen64plus binaries.

[retroresolution]

Hi Omninja,

Regarding temperatures, from my notes it seems that my Pi 2 would generally peak around 73 degrees Celsius when testing with mprime, with an ambient temperature somewhere between 20c and 25c. This is with the system overclocked with the settings I finally settled on (overvolt is +3, which increases the heat somewhat).

As long as the force_turbo option hasn’t been used (which at the time of writing will invalidate the warranty), the Pi’s governor will shut off the overclock if the temperature hits 85c, returning everything to the default values, until the temperature drops.

Running a real-world application, for example Rage Racer on the RetroPie Playstation emulator, it was around 50c. It seems that other emulators were also hitting about the same temp, including the megadrive 32x and Mupen64 N64 emulators. I believe all of these are single-core emulators, so they don’t drive the CPU as hard as the mprime test.

[dankcushions]

sorry – i’m probably off on threaded video – that’s a retroarch setting and this isn’t a retroarch emulator! however there does seem to be some sort of audio issue with mupen64plus – https://github.com/RetroPie/RetroPie-Setup/issues/1124

[scoularis]

[quote=111494]i have the same issue, so giving you a bump! seems to happen in mario kart 64 also.

i’ve not tried it, but you might want to try turning off video_threaded in retroarch.cfg – i think it’s bad news for performance but it might ensure the sound stays in sync??

[/quote]

Thanks for the reply. Now at least I don’t feel like I’m going crazy. I haven’t seen any mention of this anywhere else, and all videos of Mario 64 running on Mupen64 on the Pi2 on YouTube don’t seem to have the delay. Then again, some of them are using the rice plugin, which is immediately evident when you see the screwed up lighting on Mario’s face.

Not sure about turning off threaded video. I’ve tried turning on Hard GPU Sync, but it didn’t alleviate the sound delay.

[scoularis]

So I’ve been trying everything I can to get Mario 64 running properly on my overclocked Pi2, and I’m so very close. The game runs too poorly on the Libretro version of Mupen64 no matter what video renderer I use, so I scratched that option.

Everyone says that the standalone Mupen64 works better, so I tried that with gles, rice, and Glide64 plugins. Rice has lighting issues on Mario and the environment, and Glide64 slows to an unplayable crawl. Gles, on the other hand, runs beautifully… with one aggravating exception: all sounds are delayed about a full second behind every action.

I’ve tried setting the audio latency in the mupen64plus.cfg down to 100ms (from the 300ms default), but it made no difference. I see no mention of this problem anywhere else, so I’m at a loss. Any help would be greatly appreciated.

All other emulators/cores (NES/Gameboy/SNES/Genesis… etc.) run perfectly with no sound delay.

[Soullous]

[quote=90700]I have not gone through this for the N64, but I expect that to be something along similar lines (using linuxraw).[/quote]

Thanks for this! I was able to get the analog sticks working on PS1 games by more or less following your guide.

I have a few questions, though.

1. Have you figured out how to get them working in N64, MAME, etc.?
2. Can we use the linuxraw driver everywhere? I’m not exactly sure where it’s loading the driver for the controller.
3. Some PS1 games only support digital controllers, while some only support analog. Have you found a way to set the controllers to digital or analog on a per-game basis?

[g0nz0uk]

I’ve got my pi in my 2 player bartop which is all configured fine but also wanted to configure 2 wireless xbox controllers for n64 games and so I can take the pi out of my bartop and attach to my TV, should this be possible?

[dankcushions]

good work, thanks :) i do think the raspi-config default ‘pi2’ overclock is bad – SDRAM at 500 is very aggressive and caused instability on my system, whilst the cpu/core can run at 1000/500 without any voltage increase for me.

i’m interested in some more specific benchmarking. eg, with n64 performance i get sound and frame-rate issues on occasion, but i’ve not experimented enough to prove whether it’s GPU/CPU/core/memory/etc bound. i think mostly with emulation it’s likely to be CPU-bound, but when running shaders or 3d emulators at 1080p (how i run n64), that could change.

there’s a lot of GPU overclock options that i haven’t really looked at yet: http://elinux.org/RPiconfig#Overclocking_options

[Anonymous]

Hi all-

I got my Xo Min joysticks working great with emulationstation and using with the MAME and FBA emulators. I also use the N64./SNES/NES emulators and would prefer to use my xbox360 controllers with those roms. If my Xbox360 adapter isn’t plugged into the USB, the joysticks workgreat, if it is plugged in, the Xbox360 controllers take default as player 1 and 2 in MAME and FBA despite my Retroarch.cfg file (below) . Is there a way I can specify to just use the joysticks as player 1 and 2 for some emulators and have the Xbox360 be the default controllers for other emulators without having to plug and unplug them as I do now? i.e. leave the xbox360 adapter plugged in and still have my Joysticks as the controls for MAME and the xbox360 for all other emulators?

input_player1_joypad_index = “1”

input_player1_up_axis = “-1”
input_player1_down_axis = “+1”
input_player1_left_axis = “-0”
input_player1_right_axis = “+0”
input_player1_a_btn = “1”
input_player1_b_btn = “0”
input_player1_x_btn = “2”
input_player1_y_btn = “3”
input_player1_l_btn = “4”
input_player1_r_btn = “5”
input_player1_select_btn = “6”
input_player1_start_btn = “7”

input_player2_joypad_index = “0”

input_player2_up_axis = “-1”
input_player2_down_axis = “+1”
input_player2_left_axis = “-0”
input_player2_right_axis = “+0”
input_player2_a_btn = “1”
input_player2_b_btn = “0”
input_player2_x_btn = “2”
input_player2_y_btn = “3”
input_player2_l_btn = “4”
input_player2_r_btn = “5”
input_player2_select_btn = “6”
input_player2_start_btn = “7”

As always, much appreciation to everyone here for all the help!

[herbfargus]

BTW if you’re using snes controllers, the configs for mupen64plus are different than lr-mupen64. it might be easiest for you to make a backup of your image and do a full binary update to include the latest autoconfigs for the n64, so you don’t have to mess with manual configs.

https://github.com/RetroPie/RetroPie-Setup/wiki/Updating-RetroPie

Or you can wait a few weeks for the next release of retropie.

[tmfsd]

Is there a way two use two Retropie GPIO adapters or two Controlblocks (or something similar), one of them for two original SNES controllers and the other one for two original N64 controllers and to just switch them out depending on which games I want to play? Of course the RPi would be turned off while switching the adapters, but would it be possible that the RPi can recognize which adapter is connected and use the correct button layout for it?

[herbfargus]

https://github.com/RetroPie/RetroPie-Setup/wiki/runcommand

Use the gles2n64 plugin

https://github.com/RetroPie/RetroPie-Setup/wiki/Nintendo-64

[thezapper]

Hello all I’m having abit of trouble with my Pi playing some n64 games. So let me start off by giving some of the specifics. Raspberry Pi 2, retro Pi 3.1 image, it’s clocked to the second fastest speed, snes usb controllers. When I go into my Pi thru my home network I open the rom folder and only see 1 n64 emulator listed. I’ve read that there were 2 at one point? One played games better than others?lets specifically speak about Mario kart it loads with the Nintendo swinging fine, the cover screen works fine, but once I press the start button the picture is fuzzy top to bottom, the audio works, the game even though the screen is just fuzzy/scrambled still functions and can choose all choices to get to the race… Other games like f1 work ok minus some small details only being scrambled, like the shift lights etc… game works fine, I can live with that.

Can anyone explain to me how to get my n64 dialled in so it works nice. I am by no means a Linux programmer so a detailed step by step Is needed. I’m working on understanding certain functions and this site is certainly helping with that. Every other system works perfect, just this little setback. So I know I am new here and don’t have any neat things to contribute but I guess this post could help someone else.

Thanks

[petrockblog]

Take the card out and manually edit the config.txt on the first partition on another machine. The overlocking settings can be disabled there.

I doubt you will get usable n64 emulation on a rpi1.

[epe9686518]

Not 100% sure, but don’t think the cool_cv emulator is a retroarch emulator meaning it’s not using a retroarch core….If this is the case then it will not use nor load a retroarch.cfg file…Only emulators that have been coded to use a retroarch core will be able to use retroarch for config. Another example are some of the releases of MAME and Mupen64plus, which are not part of retroarch.

[dankcushions]

the none libretro mupen64plus emulator seems to be faster, and more compatible. like repuken2 says – the gles plugin for that is usually what you want.

games are very variable, but stuff like mario 64, mario kart, should run full speed (MK is a bit choppy in 4 player sometimes) and look correct.

[jezxlee]

Hi,

I am running current RetroPie on a Raspberry Pi 2.
I tried running some Nintendo N64 games but they are somewhat slow.
Would overclocking the RPi2’s CPU from 900MHz to 1GHz fix this speed issue?
Any other suggestions on how to improve N64 emulator speed on a RPi2?
Thanks!

Jesse

[herbfargus]

Just for reference this is a roadmap of what is left so far based off of everything on the default simple theme: feel free to use your discretion on which devices to include or not include (as some may be too obscure or specific to matter and probably aren’t worth your time, just thought I’d include the list based off of the theme I’m working from)

Missing Systems:

– Atari Falcon
– Atari Jaguar
– Atari Jaguar CD
– Atari ST
– Atari XE
– CoCo
– Dragon32
– Genesis
– Kodi
– Macintosh
– Megadrive
– N64
– Neo Geo CD
– Neo Geo Pocket
– Neo Geo Pocket Color
– PC
– PC Engine
– TurboGrafx 16
– Ports
– PS2
– Saturn
– Sega 32x
– Sega CD
– Super Famicom (wrong logo)
– Videopac
– Virtualboy
– Wii
– Wonderswan
– Wonderswan Color
– Xbox
– Zmachine

Missing Wireframes:

– Atari 800
– Atari Falcon
– Atari Jaguar
– Atari Jaguar CD
– Atari ST
– Atari XE
– CoCo
– Dragon32
– Genesis
– Intellivision
– Kodi
– Macintosh
– Mame
– Mastersystem
– Megadrive
– MSX
– N64
– Nintendo DS
– Neo Geo
– Neo Geo CD
– NES
– Neo Geo Pocket
– Neo Geo Pocket Color
– Odyssey 2
– PC
– PC Engine
– TurboGrafx 16
– Ports
– PS2
– PSP
– PSX
– RetroPie
– Saturn
– Scummvm
– Sega 32x
– Sega CD
– Super Famicom
– SG-1000
– Vectrex
– Videopac
– Virtualboy
– Wii
– Wonderswan
– Wonderswan Color
– Xbox
– Zmachine
– ZXspectrum

[zmokkie]

Solved! I now can exit the N64 games with select+start.

[herbfargus]

n64 is always hit and miss. the only thing I’ve gotten to run semi decent is mario kart on the gles2n64 plugin.

https://github.com/RetroPie/RetroPie-Setup/wiki/runcommand

[heckofagator]

The refresh didn’t seem to help. I still go straight into the config menu when selecting RP.

You know….I’ve tried to set up MAME several times on a PC and have always given up as I can never get any of the ROMS to actually work. I’m wondering if I’ve headed down the same path.

I’ve got several .n64 roms in the /home/pie/RetroPie/roms/n64 folder.

[ericahlers]

Well it looks like I need to keep exploring.
By switching to “sdl” from “udev”, I got the following systems to work:
Genesis/Masterdrive, NES, SNES, N64, FBA.
However, PSX and Mame (both using libretro/retroarch cores) don’t recognize the gamepad at all. Very strange to me..given if retroarch recognizes the gamepad in any system, i would assume it to work for all.

[rasmushauschild]

Hi retropie forum.
I’m running retropie 3.0 on a Pi 2. I’m using a controller which has one thumbstick and one d-pad. This works fine for all systems except n64, where I’m missing the c buttons. Is it possible to map the d-pad combined with another button to register as the c buttons in the retroarch version of muted 64?
If so, how?
Thanks in advance
Rasmus

[tekno911]

pi@retropie ~/RetroPie-Setup $ git log -1
commit 4142169a45e1b52920c673d6307e78c8e1e18e23
Merge: fc955ac 630d079
Author: Jools Wills <buzz@exotica.org.uk>
Date: Sun Nov 22 13:07:30 2015 +0000

Merge pull request #1093 from gizmo98/mupeninputscript

inputconfig: add mupen64plus script
pi@retropie ~/RetroPie-Setup $

Honestly, I am at a loss. Maybe the image was corrupted somehow since I did not do a hash check on in after I downloaded it. I will start from scratch, download a fresh copy, check checksum, place berryboot-20150916-pi2-only.zip on my sd card, bind my iscsi lun, install retrotpie 3.2.1, update the script and try to install lr-ppsspp. Hopefully this time it will work. I will keep you posted and by the way… Thank you so much for your help. You are a real trooper for helping out and this is what makes this community so great. Thanks a million once more.

I will post tonight the results so that if anyone runs into this issue, they will find a resolution to this problem as uncommon as it is.

TY Buzz..

TG..

[herbfargus]

Multi hotkey support was recently integrated, See this page:

https://github.com/RetroPie/RetroPie-Setup/wiki/Nintendo-64#example-mupen64pluscfg

You should be able to use notepad but not sure if that affects permissions or not. I usually use the editor within winscp or nano