I run my Pi3s at stock clock speed and have no speed issues with SNES or NES games. I don't bother with N64. A Pi 3 can barely handle it. When you get into overclocking territory the whole system starts to become unstable.

I also get that error on Ubuntu 16.04 x64. The issue is described here:
https://github.com/libretro/parallel-n64/issues/441

After installing libclang-dev and adding /usr/lib/llvm-3.8/include to the include path I had this error:

In file included from /usr/lib/llvm-3.8/include/clang/Basic/DiagnosticOptions.h:13:0, from mupen64plus-rsp-paraLLEl/jit.cpp:3: /usr/lib/llvm-3.8/include/clang/Basic/LLVM.h:22:34: fatal error: llvm/Support/Casting.h: No such file or directory

So I installed llvm-dev and then I could compile fine.

Any chance to get this incorporated into RetroPie?

@rulfen First, a riddle.

What's black and blue, yet hardly ever read?

Hint: ˙ǝƃɐd ʎɹǝʌ sᴉɥʇ ɟo doʇ ǝɥʇ ʇɐ s,ʇI

[Riddle's credit goes to @mediamogul .]

We need more info about your setup to try to help you.

@the496rocket please, try to fill the form in the read this first post.

There must be something wrong in your setup. RetroPie on a raspi3 with decent peripherals can run smoothly any game from the 8/16-bit era without any tweak. Just install, config input, put your ROMs and play.

[Footnote: OK, maybe 3D games, like StarFox (SNES) and Virtua Racing (Mega Drive), can stutter a bit. But the games you mentioned should work just fine.]

@razinx if you really want to hide the bios files, you can open the zip and add the contents to the zip for the game that requires that bios.

So the contents of pgm.zip could be added into kov.zip, and you wouldn't have that bios showing up in ES. Now of course this will make your roms bigger and so your set will be bigger.

@RedBatman you should read this post: https://retropie.org.uk/forum/topic/2859/how-to-use-mame-with-retropie-help-guide

And, of course, the official docs too: https://retropie.org.uk/docs/Arcade/

hey guys!

so i managed to get this to work to some capacity but few things are a tad wrong and was hoping for your help.

when i power the NES on, the push button is OUT when the unit is on and when i push the POWER IN, it turns OFF.
is there something anyone can think of to reverse that? I've tried moving cables around and can't seem to get it.

how does one get the LED to work with the unit if its built in on the board? should it just not turn on and off if i ave properly tapped into the power?

thanks everyone

@kmickelow You could start by telling us a few things about where you DID get your image. Is it the RetroPie 4.2 image?

Then, tell us all about your setup by following the link at the top of every page here.

@jmperez

More information about your setup will probably be necessary. The required information can be found at https://retropie.org.uk/forum/topic/3/read-this-first. Also at that same link, take note of the part detailing how to format your posts for log entries.

@simonster I had totally forgotten that I used a USB to transfer the last time and not the SD card. This should fix the problem. Thank you!

Hi chipsnblip
Yes u possible can do it with that d3scription in ur link. I'm wondering if anyone has successfully burnt a big gig pi image with games and boxart tge lot onto an external drive and it worked.

I've been chatting around on forums for past few weeks and talking about this and alot of people have said no u can't boot the image off ex hdd u need a 64gb 128gb or 250gb sd card. As it's not possible to run it off external.

Just done it myself in about 5 simple steps. With help and info from Internet of course

Just wondering as I've made my own image with games art and stuff put it on external and plugged into pi and powered on and it booted up and works.

Has anyone else tried it instead of going the long way round and inputting lots of data into the pi terminal to format scan re partition and to auto mount the usb drive.

Okay folks, I've written up a script to handle this exactly the way I described before.

It runs from the autostart.sh and watches /dev/shm/screen_manager.cfg for updates.
That way any other system process can create/modify that file and this script will respond by either starting the rom, or starting the dashboard.

Cheers!

https://github.com/coderkevin/mini-nes/tree/master/screen

@BuZz can you recommend a browser? I tried this in google chrome and internet explorer and they both give they same results, they only hold the first group of threads in their memory. I think a work around would be to scroll through each grouping and do a print of that, Looks to be about 10-12 posts per grouping. Thanks