Search Results for 'n64'

[joyrider3774]

if your still on wheezy not sure what to do if you are on jessie normally you normally also need to da a sudo apt-get update sudo apt-get upgrade to update your firmware and update retropie using the retropie-setup script. I believe update retroie pie script and then install from binaries.

however i was still on wheezy and using retropie 1.6 !! so i just downloaded the new retropie 3.6 image and copied over al of my roms en setted up everything from beginning again since i wasn’t sure config’s could be copied without changes.

About save games you’ll have to find out where they are saved (psp / psx / n64 etc think like actually saving ingame not save states) and probably will work again

About save states you’ll also have to find out where they are saved (other emulators) and copy those over.

If for some reason you were using old emulator versions and in the newer versions being used now there have been changes to savestates or save games it is possible if they are not backwards compatible that it won’t work. I have no info on that though and did not try to do this.

My guess is that save states might break quicker then save games (memory card files etc) but not sure if there are changes. if you only have save states it might be a good idea to also make sure you have save games also depening if the system / emulator used these (again think like memory cards used).

i think retroarch emulators show you the location of the save state when you save a save state on the screen, at least it does so with me so for those you can quickly find out where they are saved. Other might be saved in the roms directory or config directory in certain directories all depends on the emulator used though.

you can also install the new retropie 3.6 on a new card already with some of the games where you have save states / save games from and copy everything over and test it before actually doing the upgrade(s) on your old retropie card.

maybe someone else already did this ? but for me i started from scratch to be save

[efraimsangil]

Hi!

When I manually edit this file and run Nintendo64 emulator, lose all changes.

Why?

One of this change is:

# Joystick event string for stopping the emulator
Joy Mapping Stop = "J0B7/B6,J1B7/B6"

[joyrider3774]

you have to watch out with overclocking and the pi3 not because of the usual precautions but because the PI starts throtteling the cpu speed (down) when it reaches 80°C if it reaches 85°C or above it will throttle cpu speed to 600mhz (half of the speed) and i know they are going to let it throttle even lower (in a test firmware they did this already)

the pi3 reaches these tempratues fairly easy with some benchmark tools / cpu stressing tools and i noticed when i was running tekken 3 (actually playing) for a while i had tempratues near 75-80°C this is while the pi3 just sits in my picade so it has more air then in normal closed enclosure.

if you overlock you will reach 80-85°C and you will have lower speed then when you would not reach those temps. It happend with me with ppsspp, did not test other emulators but i guess it could happen with N64 depending on the game as well. this was wit a bit of overlocking as well as turbo mode etc, but it depends on the game and if the pi struggles with the game or not.

Using heatsinks probably doesn’t help much (it will make it go slower to those tempratrues and might give you 0-2°C diffrence, but if you are stressing the cpu it will reach those temps eventually) unless your also using a fan to blow cool air through the heatsink that probably helps a lot at least a lot more than just using a heatsink.

I created a simple script to show me the tempratures as well as the cpu speed in a loop. It’s based on code i found in retropie’s (login details info) script.

basically you put this in a file and chmod the file with for exmaple chmod 777 filename

then you can execute it.

The way you should execute it is by opening an ssh connection and let it run there and then start testing playing games / overlocking etc. you can then easilly see the cpu throttling if it eaches those temps, you exit the script by pressing ctrl+c

edit: if you want to see it reach those tempratures and throtteling sudo apt-get install stress (i think it was stress) and then run it with stress -c 4 that will use 4 threads to keep the cpu busy and with my pi3 i can easily reach those temps then

    #!/bin/bash
    function cputemp() {
    local cpuTempC
    local cpuTempF
    local gpuTempC
    local gpuTempF
    if [[ -f "/sys/class/thermal/thermal_zone0/temp" ]]; then
            cpuTempC=$(($(cat /sys/class/thermal/thermal_zone0/temp)/1000)) && cpuTempF=$((cpuTempC*9/5+32))
    fi
    if [[ -f "/opt/vc/bin/vcgencmd" ]]; then
            if gpuTempC=$(/opt/vc/bin/vcgencmd measure_temp); then
                 gpuTempC=${gpuTempC:5:2}
                 gpuTempF=$((gpuTempC*9/5+32))
            else
                 gpuTempC=""
            fi
            cpuFreq=$(/opt/vc/bin/vcgencmd measure_clock arm)
    fi

    echo "cpu temp=$cpuTempC°C gpu temp=$gpuTempC°C $cpuFreq"
    }

    while true; do cputemp; sleep 2; done;

[fistwielder]

I installed RetroPie 3.6 on a Raspberry Pi 3. Everything I’ve installed is working extremely well except for one thing.

When I run Nintendo 64 roms using mupen64plus-gles2rice, ones that should be best compatible using it according to the compatibility chart in the wiki, I get audio but only a black screen. Has anyone else encountered this or found a solution?

When I run roms using mupen64plus-gles2n64 that are compatible according to the list, they play great and I get video and audio.

[jomach]

Hey!

I have a Pi3 running RetroPie 3.6, with a PS3-controller connected via bluetooth. I have made it work with Snes, but I can’t seem to get ANY controller/input to work with N64, not even keyboard. Any ideas what might be wrong?

Btw, I’m totally new to Raspberry, linux and all of this, so… please be patient with me ;)

[jiwan]

I am currently trying to use a xbox controller for player 1 and a keyboard for player 2, both for retroarch and mupen64plus.

The xbox controller is recognized by emulationstation and correctly bound. It would be convenient to be able to use the keyboard there too.

For retroarch, I tried to dive into /opt/retropie/configs/all/retroarch.cfg to setup my keyboard as player 2 by setting:

input_libretro_device_p1 = 1
input_libretro_device_p2 = 3

The xbox controller is correctly setup with: joypad_autoconfig_dir = /opt/retropie/configs/all/retroarch-joypads/

With /opt/retropie/configs/all/retroarch-joypads containing MicrosoftX-Box360pad.cfg:

input_device = "Microsoft X-Box 360 pad"
input_driver = "udev"
input_r_y_plus_axis = "+4"
input_r_x_minus_axis = "-3"
input_r_btn = "5"
input_save_state_btn = "5"
...

And for the keyboard within retroarch.cfg:

input_player2_a = x
input_player2_b = z
...

So far, no success! Only my xbox controller is recognized as player 1 when I try to play donkey kong country 2 for instance.

As for mupen64plus, if I check /opt/retropie/configs/n64/InputAutoCfg.ini I see both of my keyboard and my xbox controller, but within mupen64plus.cfg [Input-SDL-Control2] is set to default values.

I would appreciate any help or hint to setup this weird keyboard + controller architecture!

Thanks,
Jiwan

[johndoe0336]

I am also having a problem with n64 with the wireless Xbox controllers. I am using two controllor but the only one that works is player two.

[sjo102784]

Hi guys:

I have a RPi 2 running Emulation Station. Everything works great aside from the N64 emulator, which has a number of issues.

My question is – those of you running EmulationStation on a Raspberry Pi 3 – is the N64 emulator performance good with the new board?

I’m looking to upgrade to a RPi 3, but only if the N64 emulator is functional with the updated board specs. If you have tested it successfully, what games did you run and how much trouble was changing the emulator settings to get games to run functionally?

Thanks!

[trixster]

Hi all,

Is anyone else getting problems with quake3 on the rpi3? And with mupen64plus

With Quake3 it will often freeze when loading levels (getting as far as ‘awaiting snapshot’ on the level loading screen). Sometimes it will get into a level and then freeze after a few seconds.

I’ve tried the binary and I’ve tried rebuilding from source. I’m using the latest 3.6 retropie and gpu men is set at 320mb.

Mupen64 is similar – goldeneye freezes at the intro, mariokart 64 will sometimes load, sometimes it will hang on loading with a white screen.

This freezing behaviour happens regardless of overclock settings. That is to say, it will still freeze whether I’m using stock rpi3 clock settings or whether I’m overclocking. I have a heatsink on my soc.

Any ideas?

[meneerjansen]

[quote=120084]
nice vid of n64 compatibility on the pi3:
[cut]
[/quote]
Okay, the N64 certainly had its moments if I watch that video. :)

I generally do not dig the first gen. 3D consoles. The games are not that original and combined w/ very bad graphics it’s a real torture to play them. But ‘Perfect Dark’ and ‘Goldeneye’ are gems. The game that got me really addicted at the time (the PC version of it, that is) is ‘Shadowman’. The level design (later in the game you had to go back to earlier levels to finish them because you gained more powers) and the sheer wideness of the levels was groundbreaking! It was non-linear: something that I dearly miss in modern games.

B.t.w.: ‘Shadowman’ is one of the fes games that always works in almost any N64 emulator and on very “weak” machines (like your Android mobile phone or a tablet).

[dankcushions]

for me, mk1 is fine on pi2 with lr-imame4all, but on pi3 it’s also fine on lr-mame2003.

mk2 and 3 are decent on 2003 on both pi2 & 3.

nice vid of n64 compatibility on the pi3:

[Anonymous]

So I just recently bought the RP2 and installed RetroPie on it. The first time I installed Retropie on my RP1 I had some issues with the controller. I use a third party xbox 360 wireless adapter off from ebay with my wireless controllers. The adapter was plug and play and I set up the controllers with the gui setting in RetroPie. I did however have to change the joypad driver to sdl in the cfg file in Retro to get it working.

This time, I have done everything the same way, except it doesn’t work for the N64 emulator. Before when I launched a game I got a message saying “Xbox 360 accessory wireless controller configured on port 0(sdl)” or something like that. Now when I launch a game, I get the same message, except it says (userdriver) instead of sdl. But everything seems to work fine though, all my hotkeys and things work. Except when it comes to the N64 emulator. The controller works just fine except the hotkeys, so I cannot save or load any game. I’ve tried setting the controller explicity in the emulators cfg file but it won’t make a difference. All the other emulators has set the joypad driver to “unused”.I do not get any message saying my controller is configured in the N64 emulator like I do for all the other emulators, so there is clearly some issue with setting the controller. I might add that pressing “select”+”start” seem to work though to exit the emulator.

TLDR;
On all the emulators I get a message saying my 360 controller has been configured with userdriver except on the N64 emulator. I can play the N64 games with no problems, it’s just my hotkeys for save and load that doesn’t work, exit the emulator works just fine. How do I fix this?

EDIT:
I tried all the emulators available and discovered something odd. When I use the IR-mupen64plus emulator, I can save and load and I do get the message saying the controller is configured. But if I try any other emulator, let’s say mupen64plus-gles2rice, I don’t get any message that it has been configred. So U could go with only using the IR-mupen64plus, but it dosn’t always work that good.

Weird, I’ve never had this issue on the RP1 before.

[joyrider3774]

Hi,

I’ve got my system for my picade completely set up my 32gb sd card is as good as full. But i noticed something today my emulationstation is taking up 100+MB of system ram since the PI only has 1 GB hmm seems actually about 768 MB of ram when looking with htop 100MB is a lot. Also whenever an emulator is started emulation station is still running hogging that 100MB+ ram.

Of course this is probably due to emulation station loading everything up in memory (gamelists / skins etc).

I’m using the pixel skin and have not tried changing to another skin to see if the memory goes down, but i actually suspect it to be due to the gamelists.

On other (older) systems (with less ram) i used in the past. The menu proces was replaced with the emulator being ran so all memory was availible and the menu was not running anymore. I understand this is not really possible with retropie / emulation station as well since yeah it takes a really long time to load up emulation station when you got lots of systems / roms / big gamelists.

One idea is to not load all gamelist immediatly but only a default one and load the next gamelist whenever you go to a new system. This probably isn’t optimal as well since you’ll have to wait for the gamelist of the next choosen system to be loaded.

Not sure if there is a really good way to go about this but if anything could be done for it it would be great since 100 MB out of 768 is 1/7th of my actual total ram availible.

also i’m only using 64MB for the gpu memory i’m sure other people are using more ram for the gpu for perhaps N64 emulation if they have about the same amount of roms as i have they have even less ram availble to use with the emulators.

I’m just posting it here as a reference though not a complaint just to start a discusion about it, figure out where the memory is begin used etc

[meneerjansen]

@twitch0815: Have you tried ‘Star Wars Rogue Squadron’ for the N64? Apart from the first level of ‘Star Wars – Shadows of the Empire’ is one of the few N64 games I’d still like to play.

[twitch0815]

Not to take the unpopular position but I have had my Pi 3 for sometime now and with a slight overclock, and taking the time to configure the roms for the correct emulator (There are 4 options and certain ones suit certain games better)
And downscaling the video to 640×480 The Nintendo 64 emulation is just absolutely amazing. I get that people have just put default settings in tested it and been unhappy but man is that unfair to what the Pi 3 can actually do.
Don’t take my word for it https://www.youtube.com/watch?v=dsrxdCtNzLg this was a video I made a few hours of just messing with some N64 settings. I can play Super Mario 64 and Mario Kart at 1080 P in perfect condition. And most every other game at 640×480 and the right emulator is as good or better then the N64 version. 4 Player goldeneye playing like a dream.
Look at the Pi3 tab of the compatibility sheet I have spearheaded and others have begun to work on https://docs.google.com/spreadsheets/d/1Sn3Ks3Xv8cIx3-LGCozVFF7wGLagpVG0csWybnwFHXk/edit?usp=sharing

74/78 games I have tested have been playable assuming you get the right emulator/video mode overclock mix.

And that is just the gains in N64 I have found numerous games that will play in mame that would not play on a 2 or were listed unplayable in the old compat lists.

We have also had 1 and I mean 1 release that works on a pi3.
The dev’s have not even begun to optimize code to take advantage of the emulators all they did was enable 3.6 to boot on a pi 3 and released it this is the most beta version of the 3.6 software we will ever have. We have had a few people spitball overclock settings and gpumem splits but far from the knowledge and tuning we will have in a few weeks. Just needs time but even just what I have seen out of mine in a few days I am amazed and excited.

[rompelstilchen]

hello,

I could manage to have sound for the n64 emu via the regular audio out
but I was wondering how to set it up for an usb sound card ?

I tried many alsa setups to force audio through device 1 instead of zero, so retropie outputs audio through the usb card
but the n64 emulator still does not want to

so I tried modifying the config file
but there only seem to have options for audio jack or hdmi

can someoone help ?

thanks

[Anonymous]

So I just boguth an RP2 and installed Retropie on it. Now, I wanted to move my old save states that I had on my RP1 to the RP2. I though it would be as easy as copying the state files to the new installation and I should be good to go, but whenever I try to load them, it says it failed to load.

Are there some other file I need aswell? I used the same roms too.

Also, I don’t seem to be able to save or load anything on the N64 roms. It does not show the message saying my controller have been configured either. Any advice here what could be the problem? The message saying my controller has been configured shows on all emulators except the N64.

[meneerjansen]

[quote=119721]
You can buy a “MadCatz Mojo” Android TV device for £60 which has a Tegra 4 Graphics chip and a free X-Box 360 style bluetooth joypad ! That’s cheaper than buying a Pi 3 package (with the new case and power supply etc.) and you’d have to use your own joypad. The Pi 3 is nowhere near as powerful. When you hear people trying to run PSP, Dreamcast and N64 on a seriously overclocked Pi and still get choppy framerates it makes you laugh a bit. Someone even asked for a PS2 emulator ! Don’t get me wrong, I still use my Pi (mainly for the Amiga, Atari ST and KODI etc.) because Android runs everything at 60Hz which is crap for PAL computer emulators and watching movies. At the end of the day, the Pi is a great device for the less demanding systems, so far.

Also, I thought EmulationStation was also on Android ? (Don’t quote me on that though).
[/quote]
Didn’t even know such devices existed! But like someone said on Amazon.com: since those gadgets are Android (4.2 Jelly Bean) based one might even consider buying a (second hand) Chromecast Dongle instaed and streaming to TV using your smartphone. Kodi and game console emulators enough on Google Play. But the reduced price of EUR 77 is a steal for such a device plus controller.

Like Qui Gon Jinn said in ‘Star Wars – The Phantom Menace’: “There’s always a bigger fish.”. ;) There’s always something cheaper and better. The Pi has its pros though: it runs not on Android but a real operating system (I hate Android), if you’re a nerd like me and you’ve got a lot of peripherals lying around (controllers, SD cards, adapters, etc.) there’s no beating its price and it’s great fun to tinker w/ Linux (Android is not).

[windale]

[quote=119697]

windale wrote:

However powerful Raspberry Pi’s get, most people are never satisfied anyway and end up frying it by overclocking to the max ?!? I like to use mine at the stock speed (or retropie safe defaults) the way it was intended when it was built. Any Android TV device, which are very cheap now, can wipe the floor with the Pi on every emulator. For example, ePSXe on Android has almost 100% compatibility. They even ported some of the code to the PC version of ePSXe because it is so good.

I’m not sure why they added a 64-bit compatible processor, there isn’t even a 64-bit operating system yet. I suppose it’s just for future proofing. The Pi wasn’t actually made for emulation, it’s just possible to do.

I have an Nvidia Shield TV, which is pretty impressive at emulating more modern consoles. I can get stable framerates in various GameCube (Wind Waker, Twilight Princess) and Wii (New Super Mario Bros) titles with the latest Dolphin emulator, which I never would have guessed considering the PC hardware requirements for those titles.

But I’d still rather use my pi for nes/mastersystem/snes/genesis/tg16/etc emulation. As good as the individual emulators are for Android, I have yet to find a frontend that comes even close to Emulation Station. GameSome is quite lame in comparison. Once you get RetroPie setup it’s a far more satisfying experience, and the community surrounding it is great too.

I haven’t gotten my hands on a pi 3 yet, but I’m looking forward to it, even if the performance improvements are relatively small.

[/quote]

You can buy a “MadCatz Mojo” Android TV device for £60 which has a Tegra 4 Graphics chip and a free X-Box 360 style bluetooth joypad ! That’s cheaper than buying a Pi 3 package (with the new case and power supply etc.) and you’d have to use your own joypad. The Pi 3 is nowhere near as powerful. When you hear people trying to run PSP, Dreamcast and N64 on a seriously overclocked Pi and still get choppy framerates it makes you laugh a bit. Someone even asked for a PS2 emulator ! Don’t get me wrong, I still use my Pi (mainly for the Amiga, Atari ST and KODI etc.) because Android runs everything at 60Hz which is crap for PAL computer emulators and watching movies. At the end of the day, the Pi is a great device for the less demanding systems, so far.

Also, I thought EmulationStation was also on Android ? (Don’t quote me on that though).

[Anonymous]

[quote=119607]

alucard63 wrote:

dankcushions wrote:

sorry, yeah, true, daft as it is

Yeah but that also means that the pi 2 doesn’t struggle for most emulators.

I only had a few emulators/games that where able to make the pi 2 use 100% of one core.

Here are some cases I checked:
lr-snes-9x with super FX games (but easily solved with lr-pocketsnes…)
mame4all with dodonpachi reached 100% but solved with lr-fba-next who never reaches more than 50% without fba overclocking setting* (around 95% with 200 for fba overclocking setting*)
lr-pcsx-reamred doesn’t move from 50% except with few games like some specific magic spells in FF9 or specific parts of Broken Sword 2(but it is emulation glitches IMHO)

For those we are interested in (N64, DC and PPSSPP) I didn’t check actually… would be interesting to verify later today.

*It’s a setting that allows to emulate the original plateforme but overclocked (max 200 wich is 200%). It’s usefull to remove some slowdowns on games that where lagging on the original machine (like the metal slug serie on neogeo for exemple).

my findings were different – I do understand how top works I was just miss typing. I doubt any emus run at 25% cpu.

pcsx maxes the pi2 cpu at 2x resolution (it renders everything in software) and I’m sure it spikes to 100% at some games like tekken 3 that have brief hitches at regular resolution. I don’t use fba over mame for various reasons, so mame improvements are important to me.it also maxes with 32x games.

mileage may vary …

[/quote]

Indeed, it’s true that you can find games on lr-mame-2003 that are lagging on pi 2.

I remembered trying gunbird 2 on it and it was not good at all. I checked again on my Pi2 today and it was indeed struggling at 100% cpu load.

Still I solved the problem with lr-fba…but I guess you can find some other games that are not compatible with fba and struggle on Pi2…

[Anonymous]

I just got my pi 3 yesterday and N64 runs slightly better, Dreamcast runs a lot better (I can play games like UFC that were unplayable on pi2) but still not perfect like psx. The most improved is the psp. I’m using the ppsspp emulator which gives you more options to bust down the graphics than lr-ppsspp. The graphics aren’t quite as sharp as the standard settings but games run perfectly smooth (better than N64).

So considering the performance bump already, and eventual safe overclocking, retropie being made to better suite 64bit, and the build in bluetooth/wifi it was totally worth it for me.

[meneerjansen]

For more emulators to be compatible w/ a Pi it needs a video card/video chip w/ 3D support (openGL?) first. More RAM and CPU would be overkill. My mobile phone runs PSX and N64 games better than my Pi. And my phone is really cheap!

[dankcushions]

[quote=119602]

dankcushions wrote:

sorry, yeah, true, daft as it is

Yeah but that also means that the pi 2 doesn’t struggle for most emulators.

I only had a few emulators/games that where able to make the pi 2 use 100% of one core.

Here are some cases I checked:
lr-snes-9x with super FX games (but easily solved with lr-pocketsnes…)
mame4all with dodonpachi reached 100% but solved with lr-fba-next who never reaches more than 50% without fba overclocking setting* (around 95% with 200 for fba overclocking setting*)
lr-pcsx-reamred doesn’t move from 50% except with few games like some specific magic spells in FF9 or specific parts of Broken Sword 2(but it is emulation glitches IMHO)

For those we are interested in (N64, DC and PPSSPP) I didn’t check actually… would be interesting to verify later today.

*It’s a setting that allows to emulate the original plateforme but overclocked (max 200 wich is 200%). It’s usefull to remove some slowdowns on games that where lagging on the original machine (like the metal slug serie on neogeo for exemple).

[/quote]my findings were different – I do understand how top works I was just miss typing. I doubt any emus run at 25% cpu.

pcsx maxes the pi2 cpu at 2x resolution (it renders everything in software) and I’m sure it spikes to 100% at some games like tekken 3 that have brief hitches at regular resolution. I don’t use fba over mame for various reasons, so mame improvements are important to me.it also maxes with 32x games.

mileage may vary …

[Anonymous]

[quote=119597]sorry, yeah, true, daft as it is

[/quote]
Yeah but that also means that the pi 2 doesn’t struggle for most emulators.

I only had a few emulators/games that where able to make the pi 2 use 100% of one core.

Here are some cases I checked:
lr-snes-9x with super FX games (but easily solved with lr-pocketsnes…)
mame4all with dodonpachi reached 100% but solved with lr-fba-next who never reaches more than 50% without fba overclocking setting* (around 95% with 200 for fba overclocking setting*)
lr-pcsx-reamred doesn’t move from 50% except with few games like some specific magic spells in FF9 or specific parts of Broken Sword 2(but it is emulation glitches IMHO)

For those we are interested in (N64, DC and PPSSPP) I didn’t check actually… would be interesting to verify later today.

*It’s a setting that allows to emulate the original plateforme but overclocked (max 200 wich is 200%). It’s usefull to remove some slowdowns on games that where lagging on the original machine (like the metal slug serie on neogeo for exemple).

[Anonymous]

I’m wondering if the current problem for DC, PSP and N64 really comes from the CPU.

From Pi2 to Pi3 CPU has really been improved but the GPU is still the VC IV (overclocked that’s it) with the same drivers…

My bet is the VC IV doesn’t have enough horsepower and/or the drivers are shit.

If you take a look at what a simple Odroid C1 can do…you realize that it can run DC full speed:

https://www.youtube.com/watch?v=bPpihqiDWHM

Neither the Pi2 nor the Pi3 can do that…

The Odroid C1 has a quad core A5 at 1.4 Ghz wich is < Pi3 CPU…but the Odroid C1 also has a dual core Mali 450…wich is significantly faster than the Pi VC IV.

N.B.: Hope I didn’t make to much mistakes, English is not my native language (French is…)…

[darkjoy2k2]

if you want to know how “mature” these emulators are, look for a mupen or reicast emulation on NVIDIA SHIELD with tegra processorat youtube . really smooth gameplay!

psx higher resolution is smooth now!
Dreamcast is a “near playable”, but still too slow to enjoy on Rpi3.
N64 is still messy/bad on Rpi3… i bought pi3 causei wanted to play goldeneye but its still too bad to play…

We have to wait till we have 64bit to hit the real performance…

(my Rpi3 is OC to 1400mhz)

[dankcushions]

a few things:
– we don’t have a 64-bit kernel yet. if/when that arrives, there may be some further gains.
– for almost-there cases it’s good. eg, on the pi2 PS1 in enhanced mode (2x resolution), had just enough slowdown to make it not worth it, but is now perfect on the 3. there are a number of mame games that i’ve tried that are now perfect, and weren’t before. 32x, and certain snes games – all perfect now. mario kart 64 and f-zero 64 had small amounts of slowdown in 4 player on the pi2, so i hope that they’re perfect/near perfect on the 3 (with the right plugin).
– n64, dreamcast, etc – i’m not sure these emulators are mature enough to be perfect on any amount of power – all have graphical glitches on the cores we use, and huge system demands for the more accurate ones available on PC.
– i don’t know if i’d say it’s ‘worth it’ – i think these things are so cheap and i like tinkering with them as much as playing games on them, so it’s a new thing to play with :)

[proxycell]

I’m sitting here looking at a bunch of charts, tables and most importantly: some YouTube videos to see if getting the new RPi3 is worth it

So far I am of the mind that it is not yet worth it, at least in terms of what we are all here for: gaming

I know some people will throw out some numbers (along with the above mentioned tables and charts!) but so far I see no real improvements over the previous RPi2 with perhaps the exception of the built-in WiFi which will be of great use for Kodi/streaming/SSH purposes.

The “problem” consoles still retain their title. N64/PSP/Dreamcast – so far they appear to be a bit better but not yet fully playable across a wide selection of games. I am NOT blaming anybody for this. I realize that this stuff is extremely hard to get right and its all provided for free. All I am suggesting is that perhaps people just take their RPi2 and overclock it, save a few bucks. I am not inferring anything else at all.

Some users have been posting questions regarding PSX/32X/SNES/etc performance and I do not believe there were any issues regarding these on the old RPi2 (overclocked at least). Please correct me if I am wrong.

[tboheeren]

I tested today with glideN64 instead of the standard emulator for N64. Big improvement especially for Goldeneye. You can check it out here

[retroresolution]

I’ve just set up RetroPie 3 on a new Pi 3.

I’ve overclocked the Arm to 1300, and the sdram to 500. Whilst it is stable, in a stress test running all four cores it hits 82 degrees c and throttles back (I’ve been reading that the SoC heat output varies wildly on the Pu 3, with one report that fully and overclocked to 1500 it is only hitting 60c…)

As the emulators all appear to be single-threaded the heat-thrittling isn’t an issue, so far

PlayStation emulation is excellent even with enhanced resolution output.

N64 emulation is a different matter; using mupen64plus (non-libretro) on an overclocked Pi 2, on RetroPie 2.6, Mario 64 is flawless, Mario Kart is 95‰, although most other titles are very rough.

On RetroPie 3.6 on Pi 3, Mario 64 is fine, Mario Kart seems worse. I hoped GoldenEye would be playable, but it seems worse if any thing.

It appears that the renderers are outputting much higher resolution visuals than before, even when the resolution is set to 320×200, and the framebuffer set accordingly.
I’ve tried various all three plugins, but don’t seem able to match the performance of the older, slower, system on the new setup.

Any hints on how to configure n64 on RetroPie 3, on a Pi 3 will be gratefully received – I’m new to Retropie 3.x, having stuck with 2.6 since last May, and perhaps I’ve missed some fundamentals.

In case it’s significant, I installed RetroPie on top of Noobs Raspbian (updated and upgraded), as I intended to multi-boot with Osmc.

[dankcushions]

playstation and n64 use more than 6 main buttons, depending on the game.

neogeo/snk had a 4-in-a-row layout so it makes slightly more sense playing those on an 8 button layout (using top row), but that’s being a little picky :)

if you’re mainly playing arcade stuff i think you’ll be ok with 6 action buttons.

[Soullous]

I just swapped out my Pi 2 for my Pi 3. I haven’t tried too much yet, but I ran a few N64 games and they run a bit smoother than they did on my overclocked Pi 2. Nothing earth shattering, though. Still have to fiddle with the rendering engines to find the one that works best for each game, and there are still certain spots in certain games with major slowdowns (mainly cutscenes). I’ve also set the resolution to 320×240 for all N64 games. I have yet to mess with any overclock settings on the Pi 3.

I also played through World 1-1 of Yoshi’s Island, and it appeared to run flawlessly.

I never had issues with PSX games on the Pi 2, (granted, I haven’t played many of them) so haven’t bothered testing them on the Pi 3, since I’m assuming they’ll run just as well.

[liquidream]

Hi all,

Is anyone else experiencing “freezing” with the N64 emulator (mupen64plus) on the Raspberry Pi 3 (RetroPie v3.6)?

I can play a game (like Mario64) for a few minutes, then the whole Pi locks up (can’t SSH in to do anything) and have to pull the power. As far as I can tell, it’s not overheating (doesn’t seem to get much above 61°C) and I’m using the official Pi power lead with no additional items plugged into USB.

I found what seemed like a similar issue here, but I’ve tried switching the AudioDriver and still crashes. I’ve also tried building the Emulator from source, in case it’s a fixed bug, but still occurs.

Any ideas?

Thanks in advance! :o)

[drakaen391]

It didn’t look like to many control issues with the N64… I will be trying it out myself as it looks mostly playable…

Was this with the modified resolution or standard?

[drakaen391]

Hello All…

I am currently running RetroPi on A Raspberry B…

Currently awaiting my new Raspberry 3 to arrive any day now and am wondering if 32X works for it… Also, with the Emulator issues on N64 with sound… is it possibly to disable to sound in it or would changing the resolution down help bring the sound closer to normal?