You could try setting up your wifi from the command line and reboot your RPi. https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md

@vincedj Could you edit your comment to add formatting?

@dankcushions thanks mate! that was the problem :)

now playing uridium on the tv. :)

@dankcushions said in No luck overclocking Retropie with Raspberry Pi 3:

@mrbwa1 n64 (HLE) emulation isn't CPU intensive really. look at top command when it's running. it's GPU - that's why lowering resolution helps.

it is certainly using hardware rendering, though

Looks like it's tome for me to look back at what's being used. Certainly, trying to render at 1080p is going to use a lot more GPU than 480p. And if someone doesn't like the look @ 480p, they should look at the original N64 hardware running through a flat screen! (S-video helps a lot: that or having the $$ and hardware to do the HDMI and RGB mods.)

To sum up my thoughts: N64 emulation is really hard and it's not the hardware itself that seems to be the limiting factor. The actual emulation is extremely difficult.

Awesome thanks. Ive got it all sorted and my screen is flipped, Love the raspberry Pi. Thanks for the help!

Figured it out! Dental Pick!

I'm on 3.8.1 and my PS3 controller is working via Bluetooth just fine. I should mention that it is a fresh install (I did not upgrade from a previous version).

Do you have a PS3? If you plug it in to that and turn it on with the PS button I think it resets itself. Then go to RetroPie setup and try to setup the controller again?

Hey,

I was looking for a way just a day or so ago. Here are some relevant topics:

https://github.com/Aloshi/EmulationStation/issues/371
https://www.reddit.com/r/emulationstation/comments/3gilif/hiding_roms/

I have not tried any of the solutions I've read, but if you try any of this, please report back.

Awesome Thanks !!! That worked.. :)

@mat03111984 Excellent news, glad you were able to resolve the problem

Which emulator(s) are you seeing this with?

I see lots of entries for the same game with the PlayStation emulator, as Emulation Station is displaying all the files which make up the game (at least, all those with extensions it 'recognises', as specified in the es_systems.cfg file for that emulator)

A long while ago I watched one of the excellent RetroPie videos on YouTube from forum user @Floob in which he covers using a tool to combine the elements of a PlayStation game into a single file (Iso, or similar, if I recall correctly), which cleans up the list in ES

In the Spectrum emulator I generally see a couple of entries if I've unpacked an archive file and left both the archive and the original in the Roms directory

Hi,

If you can place a copy of your broken .cfg somewhere, Pastebin, DropBox, etc, I'd be happy to run a diff against versions I have to see if I can find where the problem is.

I think, from looking at the forked github repo for EmulationStation used by RetroPie, and the original parent project, that es_systems.cfg is generated by code - I was hoping there was a full copy of the file in the repo which you could retrieve for any given version of RetroPie.

[edit}
As suspected, the es_systems.cfg is generated when the system is being set up

From the README.md file in the parent project:

"When first run, an example systems configuration file will be created at ~/.emulationstation/es_systems.cfg. ~ is $HOME on Linux, and %HOMEPATH% on Windows. "

@gandarez Hi,

Does the system display the temperature correctly if you issue the following command:

vcgencmd measure_temp

If so, you could run raspi-config, and use option 5 (or similar, depending on your specific version) to access Internationalisation Options, then configure your locale to see if this helps

sudo raspi-config

@Loxley I'm currently using it on my Gameboy zero build without an issue with my controls on version 3.8

Did you ever solve this problem in the end? I had the opposite problem. My splashscreen sound was going through the headphone jack and I had to force it through HDMI. I think you got the order of the line wrong. Try using this:

omxplayer -b -o local --layer 10000 "$line"

I updated to 3.8 and my 8bitdo SNES30 controllers which I set up and used the UDEV file as shown above still worked. I, however, purchased an NES Pro pad and cannot get it to pair. I downgraded the firmware on it to 1.68, but it still does the same thing. When I try and pair it, it is detected and identified correctly. When I select it, and it asks for the security mode and I select EITHER one, it crashes the system and displays the text pictured below. Any ideas?

screen shot