Search Results for 'n64'

[etho201]

I’m using the Xbox 360 wireless controller adapter with my Xbox 360 controllers. I can play 2 player games with no problem using both controllers for the SNES, but when I start up a N64 game only the “Player 2” controller works. The “Player 1” controller is unresponsive. Does anyone know how to fix this issue?

[ssimplemind]

He guys, I was about to post the same problem for my Retropie configuration.

My config is:
– Raspberry Pi 3, initially with RetroPie 3.4, now upgraded to 3.6
– VRAM split is 256MB
– Sony, 16GB SDHC Class 10 SD Card
– official rPi 3 power source, 2.5A if I remember correctly
– one or two Playstation 3 controllers, connected by bluetooth
– I´ve had ROMs directly on my SD Card and also on my network storage

My problem is that the raspberry pi freezes in the middle of games. It happened to me in SNES, as well as N64 and PSX games. I specifically tested the SD Card before I bought it and it only has about a month of use, but the problems appeared on the first day.

My rPi freezes less frequently than @nonorius ´s. It can sometimes work for about 2-3 hours of playtime, while other times it works just for 5-10 minutes. I also kept it on for almost two days without any game running and nothing happened.

I´ve tried keeping an eye out for RAM usage (I had 512MB VRAM at first, 256MB now), keeping the top command running in an ssh session, but I had more than 100MB of RAM to spare when it happened.

I´m pretty new to linux and I´m not sure where to look, so I´d be grateful if you could point me to some application logs. Maybe I can find the error there. I tried running emulationstation --debug from the ssh session but I think it doesn´t work that way, because I can´t start any game.

Could it be because of the bluetooth controllers? Did anybody else experience this problem with them?

[vretro]

The Wiki explains a Memory Split of up to 256 can be set and this is what I currently use on a Raspberry Pi 3. In the forum I see references to people using up to 320.

To get the most out of systems like PSX, PSP, N64 and Dreamcast, would setting a memory split of 320 improve performance for 3D systems and 2D systems?

My understanding is the CPU is used more in emulators, so is it really just EmulationStation that would benefit?

https://github.com/RetroPie/RetroPie-Setup/wiki/Memory-Split

[winnetouch]

I read online that N64 games run better if you put it the N64-muppen64plus folder. But I don’t have that folder on my retropie.

Is there something I have to set before I can access it?

[Anonymous]

I am trying to change the video plugin for mupen64plus-libretro. I have seen a location within retroarch-core-options.cfg where it currently lists the following line;

mupen64-gfxplugin = “rice”

Is that the proper location to make the adjustment? I tried typing in the names of the other 2 plugins but they didnt work. What are the proper names that would need to replace “rice” in order to tryout the other plugins?

Thanks

[Anonymous]

I am trying to display FPS while in the various version of Muppen. Is that possible? I can get the FPS overlay to work fine for libretro but haven’t figured out how to make it work with Muppen.

Thanks

[fistwielder]

It is fixed upstream. You just need to update Mupen64plus now and it will work:

1. Press F4 to get to console

2. Type cd RetroPie-Setup then press enter

3. Type git pull then press enter

4. Type sudo ./retropie_packages.sh mupen64plus then press enter

5. Then type emulationstation and press enter to get back into EmulationStation

[mallipa]

I was able to run it using the commands you posted in github and didn’t get any errors (game worked fine with GLiden64). I did chmod 777 the mupen64plus directory. However when I run it from emulation station it still doesn’t work. All the other plugins work fine. do you think it could be other settings that caused the problem?

Reading symbols from /opt/retropie/emulators/mupen64plus/bin/mupen64plus...(no debugging symbols found)...done.
(gdb) tty /dev/tty1
(gdb) run
Starting program: /opt/retropie/emulators/mupen64plus/bin/mupen64plus --noosd --fullscreen --gfx mupen64plus-video-GLideN64.so --configdir /opt/retropie/configs/n64 --datadir /opt/retropie/configs/n64 /home/pi/RetroPie/roms/n64/Mario\ Kart\ 64\ \(U\)\ \[\!\].z64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0x72699460 (LWP 1113)]
[New Thread 0x70697460 (LWP 1114)]
[New Thread 0x6fe97460 (LWP 1115)]
[New Thread 0x6f697460 (LWP 1116)]
[New Thread 0x6ee97460 (LWP 1117)]
[New Thread 0x6e697460 (LWP 1119)]
[New Thread 0x6de97460 (LWP 1120)]
[Thread 0x6de97460 (LWP 1120) exited]
[New Thread 0x6de97460 (LWP 1121)]
[Thread 0x6de97460 (LWP 1121) exited]
[Thread 0x6e697460 (LWP 1119) exited]
[Thread 0x72699460 (LWP 1113) exited]
[Thread 0x6ee97460 (LWP 1117) exited]
[Thread 0x6f697460 (LWP 1116) exited]
[Thread 0x6fe97460 (LWP 1115) exited]
[Thread 0x70697460 (LWP 1114) exited]
[Inferior 1 (process 1110) exited normally]

[Anonymous]

Hi, Last year I bought a raspberry Pi model 1 B, and put Retropie on it, Love it to death, My friends saw it and is jelly. I’m planning on building him one for his birthday, he is not tech savvy so i want to know what emulators and systems the Pi Zero can handle without studders, sound issues ect. I know N64 can only just barely run on the Pi 2 and 3, So I won’t even try it on the Pi Zero, PS1 is on the line though, Does anyone have any experience running a PS1 game on the PI Zero? I don’t think its possible. However SNES,NES,all sega systems (megadrive,32x,Genesis,CD) should work fine correct?

[Anonymous]

Im overclocking mine at 1350 sdram_freq=500 with little issue. N64 sees a big bump, not as good as ps1 but Majora’s mask is 99% there and shadow of the empire is a lot better, Dreamcast is pretty good too.

[mallipa]

I am kinda new so please bear with me.
when running the n64 emulator I am only able to run the rice and gles. When I try to run the GLiden64 it goes black then returns to emulation station. I am pretty good with command line so I can provide whatever if it helps. I checked my runcommand.log and I am getting a Segmentation Fault? Any help is appreciated.

/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh: line 215: 1912 Segmentation fault "$rootdir/emulators/mupen64plus/bin/mupen64plus" --noosd --fullscreen --gfx ${VIDEO_PLUGIN}.so --configdir "$configdir/n64" --datadir "$configdir/n64" "$ROM"

Also I ran sudo ./retropie_package.sh mupen64plus to get to this point. It worked on my pi2 but I have upgraded to a pi3 and downloaded from binary retropie 3.6

[Anonymous]

RetroPie 3.6
Raspberry Pi 3
Original power supply 2.5a
updated/upgraded via apt-get 18/3 (updating atm)
bluetooth-pi is newest version
original PS3 controller

Everything works great, until i go grab dinner or something that takes about the same amount of time. Now my controller is no longer working. Turning it off and then turning it on again does not help, it wont connect. It wont connect with usb cable plugged in either.

I havn’t tested any other game than Ocarina of Time on N64 (since it is awesome!)

The only solution I’ve come up with is sudo reboot and that sucks.

Anyone know what I can do to fix this?

[MRKane]

Am also keen to hear about this – my primary is N64 so call overclocking and performance a “special” interest ;)

[gizmo98]

Interesting. Please try a source based installation over retropie_setup.sh. Even though this should only happen if you run retropie_packages.sh as user root. You could also rename this line by hand:
wrong
<path>/root/RetroPie/roms/n64</path>
right
<path>/home/pi/RetroPie/roms/n64</path>

[pi-guy]

I tried overclocking to the settings you specified but the pi3 would start and stall at the RetroPie Splash screen (didn’t get to emulation station splash screen). Tried multiple times.

Would you mind uploading your config.txt so I can compare yours and mine – I’m running the latest 3.6 RetroPie image (no berryboot)?

I could have done something wrong. Plus I have no heatsinks or fan…yet…just got my pi3 today – that might be it.

Also, don’t know if you wrote the github article but I don’t see a 640 X 480 16:9 option in Glide and I love me some Killer Instinct.
Thanks for the help

I must say though that the RPI3 is awesome! I used to have issues with all my roms loaded (almost 6000 across 17 emulator sections) and the menu hanging or missing images – or it may have been all the scrapping and game images that were loaded – but that problem is no longer present. I don’t know if it’s the RPI3 or the latest retropie release that I’m running that fixed it – but I’m VERY happy now with my setup even if the wifi wants to constantly drop.

I did up arm_freq to 1100 (the only setting I’ve changed in the config.txt now) and killer instinct on n64 runs much better after one level but then screen remenants and trails are present heavily on battle 2.

[zerojay]

I followed the above and it causes emulationstation not to launch due to not having permissions to /root/RetroPie/roms/n64. Why? Well, because of this in es_systems.cfg:

<system>
<name>n64</name>
<fullname>Nintendo 64</fullname>
<path>/root/RetroPie/roms/n64</path> ************
<extension>.z64 .n64 .v64 .Z64 .N64 .V64</extension>
<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ n64 %ROM%</command>
<platform>n64</platform>
<theme>n64</theme>
<directlaunch/>
</system>

You probably want to fix that.

[Swampy]

I changed the gles2n64.conf and now it seems to work:

#gles2n64 Graphics Plugin for N64
#by Orkin / glN64 developers and Adventus.
config version=2

#Window Settings:
window width=702
window height=576
multisampling=0
auto resolution=0

#Framebuffer Settings:
framebuffer bilinear=0
framebuffer width=702
framebuffer height=576

#VI Settings:
video force=0
video width=702
video height=576
video stretch=0

#Render Settings:
enable fog=1
enable primitive z=1
enable lighting=1
enable alpha test=1
enable clipping=0
enable face culling=1
enable noise=0

#Texture Settings:
texture 2xSAI=0
texture force bilinear=0
texture max anisotropy=0
texture use IA=0
texture fast CRC=1
texture pow2=1

#Frame skip:
auto frameskip=1
target FPS=20
frame render rate=1
vertical sync=0

#Other Settings:
update mode=1
print FPS=0
ignore offscreen rendering=0
force screen clear=0
flip vertical=0
tribuffer opt=1

#Hack Settings:
hack banjo tooie=0
hack zelda=0
hack alpha=0
hack z=0

[gizmo98]

@zerojay
Try this:
Close emulationstation with F4 and type…

mkdir test
cd test
git clone --depth=1 -b mupen64plus-videocore https://github.com/gizmo98/RetroPie-Setup.git
cd RetroPie-Setup
sudo ./retropie_packages.sh mupen64plus
emulationstation

Limitations:
-Only runs good if output res is Full HD
-Kills console keyboard input. Only important if you close emulationstation or want to use launch menu.

[Swampy]

I still have the problem. I also thought it would be something with the resolution. I still have a CRT-TV. Sometimes it worked by changing mupen64plus.cfg, but the next time the error comes again. The mupen64plus.cfg will always be overwritten. Why?

[slayer612]

With some further research I found a “solution” to the problem described above in THIS THREAD (which I didn’t see earlier, unfortunately). So in case anyone encounters the same problem:

The cause for the hotkeys not working is indeed the “wrong” button IDs, which are being written into mupen64plus.cfg automatically.

I disabled this feature in the /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh by commenting out the following lines:

# write hotkey to mupen64plus.cfg
 # iniConfig " = " "\"" "$configdir/n64/mupen64plus.cfg"
 # iniSet "${hotkeys_m64p[$i]}" "$bind"

Then I manually made my settings in /opt/retropie/configs/n64/mupen64plus.cfg by adding the button IDs shown by jstest:

# Joystick event string for stopping the emulator
Joy Mapping Stop = "J0B10/B11"
# Joystick event string for switching between fullscreen/windowed modes
Joy Mapping Fullscreen = ""
# Joystick event string for saving the emulator state
Joy Mapping Save State = "J0B10/B7"
# Joystick event string for loading the emulator state
Joy Mapping Load State = "J0B10/B6"

This fixed my problem – the hotkeys are working now.

I still don’t understand where those other button IDs retroarch uses are coming from though…

[dankcushions]

[quote=120755]
Emulator tested lr-mupen64plus. Is this the best one to use?
[/quote]
no. use mupen64plus-X where X is whatever plugin is most suited to the game. seems to be gliden64 for the pi3, although I’ve not checked.

[Anonymous]

Hi all,

Having problems playing N64 roms on my new Rpi 3 setup. I am using a wireless Ps3 controller and latest build 3.6

All roms tested so far seems to work ok for 1-2 minutes then system completely freezing. Among others this has happened with Donkey Kong 64, Super Mario Kart 64.
Emulator tested lr-mupen64plus. Is this the best one to use?

I am starting to think there is a heat and/or stability issue. The rpi is not overclocked, and I have put a heatsink on soc/network controller. After playing around for some time with other emulator system reports temps in region 65-70 degrees. Is this normal?

Any ideas what could cause this issue?

[zerojay]

Gizmo, I tried building from your repo but it looks like you’ve changed things quite a bit from upstream such as the Makefile being moved and now it apparently requires the Mupen64plus api files to be somewhere? Can you give me a step by step on how to compile from your fork?

[fistwielder]

For N64 emulators, when I set the video mode to CEA1 (640×480), my TV says the video input is actually 720×480 and I get no video, only a black screen. I can still hear audio.
For N64, I would especially like to use video mode CEA1 for the performance gains, but I can’t seem to get around this.
Has anyone else had issues with only getting a black screen when using video mode CEA1?
I’ve been searching through the wiki and forums for a solution with no luck.

I’m using RetroPie v3.6 on a Raspberry Pi 3 connecting to an HD TV via HDMI. Other devices that output at 640×480 seem to work fine on my TV.

Any advice would be appreciated. Thanks.

[dsmcrzy]

Hey Everyone,

New to Pi and new to retropie. I have been able to find tons of information and fixes online to get my pi2 set up with retropie 3.6 and have the NES, SNES, N64 and PS1 emulators working great.

There is one last thing I have been battling that I can’t quite figure out nor can I find via google. In every emulator and every game the sound will work and then pause for a second and then continue working. The intervals seem random. The sound only pauses its not laggy at all. There is no set time between them. When I set up my pi I didn’t have sound on my TV so I had to alternate the /boot/congif.txt file to get my sound to work.

Is there another option I need to fix somewhere to help with the sound? Like I said it’s not one emulator or one game so I’m thinking it has something to do with pi overall like my original no sound issue.

Thank you

[musenwoody]

Hi.

I have the same problem.

After checking mupen64plus.sh, I found that every time when I run this file, it would regenerate mupen64plus.cfg.

You could find this :

# write hotkey to mupen64plus.cfg
 iniConfig " = " "\"" "$configdir/n64/mupen64plus.cfg"
 iniSet "${hotkeys_m64p[$i]}" "$bind"

To solve this problem, I just edit mupen64plus.sh,

# write hotkey to mupen64plus.cfg
# iniConfig " = " "\"" "$configdir/n64/mupen64plus.cfg"
# iniSet "${hotkeys_m64p[$i]}" "$bind"

[slayer612]

I just configured an 8Bitdo NES30 Pro on my RPi3 (RetroPie 3.6) using Floob’s video tutorial and am having troubles getting the hotkeys in mupen64plus (mostly for “exit emulator”) to work.

I suspect the problem has something to do with the fact, that the “Joy Mapping Stop” values are auto-generated when starting up the emulator. These values don’t work for me, since the mupen64plus.cfg – to my knowledge – uses the button numbers shown by jstest. This leads to problems in my case for the following reasons (or at least that’s what I think the problem is):

The button numbers in my controller specific config file (in the retroarch-joypads folder) are different from those shown when using jstest. E.g. in the controller specific config file “select” and “start” are 21 and 22 (matches up with the values in Floob’s video), but jstest shows 10 and 11 for the very same buttons… The controller config works whith all emulators I’ve tried so far (except for megadrive, where I had to enable the 6 button controller and remap the buttons a,b,x,y,l,r)…

The InputAutoCfg.ini entries for my controller in the n64 folder also got generated flawlessly (but use the low button numbers which are shown in jstest, not the ones from the retroarch-joypads config). Normal controls in mupen64plus work as they should. It’s just the hotkeys I can’t get to work.

I tried to set “Joy Mapping Stop” to “J0B10/B11” in the mupen64plus.cfg, but as soon as I start the emulator, it gets overwritten by “J0B21/B22” – which does not work to exit the emulator – so I suspect it actually needs the jstest values in order to work.

Does anybody know, why my controller.cfg in retroarch-joypads uses different button numbers than shown by jstest and/or how I can overwrite the values used in mupen64plus.cfg permanently?

Thank you in advance for the help!

In case this is relevant:
I used a different mode than the one shown in Floob’s video tutorial in order to pair my controller (“power + R” instead of “power”). This is a new mode added with a later 8bitdo firmware and lets me configure L2 and R2 in ES (which didn’t work with the other mode). However, apart from the additional entries for L2 and R2, the generated values in retroarch-joypads/controllername.cfg are the same.

[gizmo98]

Do you User HDMI or Composite?
Please update Mupen64plus:
Press F4. Emulationstation closes.
Type:’
cd RetroPie-Setup
git pull
sudo ./retropie_packages.sh mupen64plus
emulationstation ‘

[gizmo98]

It is a little bit faster but has more glitches as any other plugin. It has more compatibility issues as glesn64. But it dös Notaz Crash your Pi of you run Zelda games. ( But colors are wrong)

[Anonymous]

Is there an easy way to add this plugin to the mupen64 installed with Retropie to test it out?

[fistwielder]

I just saw that someone posted about a new plugin. Maybe it will help with this.

[dankcushions]

https://github.com/tachiweasel/mupen64plus-video-videocore

Not had a chance to check this out, but sounds very promising. i know the existing semi-optimised gles2n64 plugin works great, but has limited compatibility. This seems to share the compatibility problems (at least, so far), but should be even faster. Very interesting!

[Anonymous]

I have a RP3 with 4 controllers running RetroPie 3.6 with EmulationStation 2.0.1.

2 SNES iBuffalo USB Controllers that work FLAWLESSLY!!!

However, when I plug the MayFlash N64 adapter in, reboot RP3, it detects the 3rd and 4th N64 controllers. All buttons work, but it will NOT detect the analog stick. It won’t even register any direction when configuring the UI within ES.

If I plug the USB adapter and controllers into a Windows PC it detects everything just fine.

When I run jstest /dev/input/js2 I can see the analog stick registering on both axis0 and axis1 but it’s not being detected in EmulationStation or games.

Is there a configuration file that I need to update/change for EmulationStation to detect the analog.

[trixster]

Update on this – running at 720p was the issue. Changing up to 1080p (50 or 60hz) or down to 640×480 stopped the crashing in both Quake 3 and mupen64plus. Bizarre.

Any ideas why 720p might cause these lock-ups?

[storyhobbit]

Hey guys!

I only have a small amount of technical expertise, but I’ve looked all over and can’t find an answer to this question (it may just be something simple that I just don’t know). I installed Emulation Station on my Raspberry Pi 2 (Model B), and it all works great, but I’m trying to change the resolution for the N64 emulator because it’s far too sharp and all of the games have a lot of lag as a result. I don’t need it to be more than 640×480, but for some reason the emulator renders it in HD. I’ve tested Playstation games too (since they require similar processing power), and they work fine at the appropriate resolution. Anyone know how to fix this?