Can I just jump in here and ask what you have to do to get the Roms to copy and save to the stick? I use a usb drive to copy Roms to the Pie, but I was unaware that you could launch them off of it.

I’ve only used rPi3’s internal bluetooth module with pi-bluetooth installed. I’ll try and get an usb module tomorrow to check again.

Hallo guys,

i have the same problem:
Retropie freezes after 5-10 min while I’m playing Mario Kart 64 with my PS3-Controller connected via Bluetooth (same with other games).

When using another Controller connected via USB I haven’t had any problems playing for hours.

I thing it’s definitly a Bluetooth problem

[quote=121907]That almost worked, but when I get to the wizard it does not register the controller button as keyboard key
[/quote]
Try to test on the command line (press F4 and Enter) if the controller indeed behaves like a keyboard. Letters etc. should appear on the command line when you move the stick or press buttons. Return to Emulationstation by typing “emulationstation” on the command line and press Enter.

If you’re absolutely definitely super duper sure the controller/keyboard actually does send output to the Pi then disconnect everything but the Neo Geo controller/keyboard (and a temporary USB controller to navigate through the Wizard). At first it didn’t work for the person either in the other topic because the Pi only reacted to the input of the “real” keyboard that was connected.

If need be: reboot your Pi and make sure NO other keyboard is connected to the Pi.

After setting up the Neo Geo X Arcade joysick make sure no other joysticks, controllers and what have you not are connected to play games.

Good luck :)

personally i’d never use such a large gb card, as if the card fails, you’ll have lost lots of your project, if you have lots of roms, please consider using a 4-8gb card with a large gb usb drive or hdd/ssd

if your smaller one works no issues grab yourself a usb drive

Controller 1 works for me and buttons on player 2. I am using the Xin-mo Usb controller board and can play on player 1. So I should have the 25a7:0701 in the code then? Should I update the kernel as well? If so how do I do that? One additional question how to I give myself perms to those directories to use winscp to update files from my pc?
Thank you

Read the documentation again. The zip file is the berryboot software – you extract that first to a sdcard. Then you install the im256 from a USB stick when booted into berryboot.

The berryboot images are provided as is, due to them being requested. They are installed in the same way as any other berryboot image (see the berryboot project documentation) – you put them on a fat32 USB as a file and install them from the berryboot menu.

I am unable to offer support for them though, as I don’t use them.

http://www.berryterminal.com/doku.php/berryboot

Has anyone thought of getting – or has gotten already – one of the 314GB PiDrive hard drives.

Been looking into these over the last couple of days and been thinking it might be a good option. Faster than a USB drive, and ooodles of storage.

also, what are you wanting to do?
run roms from usb?
transfer roms from usb to pi-SD card?

Okay guys, I’ve done a lot of testing since I last wrote. I’ve focused on performing a slightly more in-depth comparison of RetroPie on the Raspberry Pi 3 compared to running RetroArch on the PC, to sort of compare to the best case scenario.

First off, the hardware specs:

[b]Windows PC:[/b]

Core i7-6700K (Skylake)
Radeon R9 390 8GB
Windows 10 64-bit

[b]Linux PC:[/b]

Dell Latitude E5450
Core i5-5300U (Broadwell)
Integrated HD Graphics 5500
Ubuntu 15.10 64-bit

[b]Monitor (used for all tests):[/b] HP Z24i LCD monitor with 1920×1200 resolution. This monitor supposedly has almost no input lag (~1 ms), but I’ve only seen one test and I haven’t been able to verify this myself.

[b]Gamepad (used for all tests):[/b] CIRKA USB SNES replica

I tested input lag in NES and SNES emulators and used the following two games:
[ul]
[li]Mega Man 2[/li]
[li]Super Mario World 2: Yoshi’s Island[/li]
[/ul]
[b]Test methodology:[/b]

I filmed the monitor and gamepad with a Canon EOS 70D in 1280×720 mode at 60 FPS. I filmed while jumping repeatedly (approximately 30 times for each test) and then analyzed the film clips frame by frame to get the average input lag.

[b]Results:[/b]

[b]Raspberry Pi 3 + RetroPie 3.6[/b]

FCEUmm: 7 frames
Nestopia: 6 frames
snes9x-next: 8 frames

[b]Comments:[/b] Nestopia was pretty consistently 1 frame quicker than FCEUmm.

[b]Windows 10 + RetroArch 1.3.2[/b]

video_hard_sync off:

Nestopia: 7 (often 8) frames
snes9x-next: 9 (often 10) frames

video_hard_sync on:

Nestopia: 4 frames
snes9x-next: 6 (often 7) frames
bsnes-mercury-balanced: 6 (often 5) frames

[b]Comments:[/b] Xbox Game DVR feature was disabled in Windows’ Xbox application. Having this feature enabled has been reported to add input lag, but I didn’t really investigate it.

[b]Ubuntu 15.10 + RetroArch 1.3.3 in KMS mode[/b]

Nestopia: 5 frames
bsnes-mercury-balanced: 7 frames

[b]Comments:[/b] video_hard_sync was left off. Enabling it had no effect on performance.

[b]Conclusions:[/b] There are a few conclusions we can draw from these tests. First of all, Nestopia was pretty consistently 1 frame quicker than FCEUmm. SNES emulation seems to be approximately 2 frames slower than NES emulation with Nestopia (at least for the tested games). However, testing on Windows suggests that bsnes-mercury-balanced is quicker than snes9x-next. Where snes9x-next is around 2-3 frames slower than Nestopia, bsnes-mercury-balanced is around 1-2 frames slower. Unfortunately bsnes-mercury is not available on RetroPie (and probably wouldn’t run very well due to its higher requirements).

Regarding platform differences: RetroPie is 1-2 frames faster than Windows 10 without video_hard_sync enabled. Once video_hard_sync is enabled, Windows 10 shaves off at least 3 frames of input lag for both NES and SNES emulation, providing the quickest response of all three tested platforms. The biggest surprise is perhaps that running RetroArch in Linux under KMS still doesn’t beat Windows in terms of input lag.

So, to summarize, the final standings are:

1. RetroArch under Windows 10: 4-6 frames (67-100 ms) of input lag
2. RetroArch under Linux KMS: 5-7 frames (83-117 ms) of input lag
3. RetroPie: 6-8 frames (100-133 ms) of input lag

Although Windows is the quickest, I still wouldn’t call it lightning fast, especially not in the SNES case. Adding a couple of frames for the average TV and you’re already at 133 ms input lag. That may be perfectly fine for modern shooters, but it’s not ideal for super-fast platformers. My Samsung plasma TV appears to have around 4 frames of input lag, which combined with RetroPie results in a total of 200 ms for SNES emulation. That is definitely noticeable and makes, for example, Super Mario World a lot harder than it used to be.

One interesting development that may change things slightly for the Raspberry Pi is the ongoing development of a fully open source OpenGL graphics stack. Maybe someone more knowledgeable than me can chime in on that and shed some light on any possible ramifications? Given the fact that a PC running Linux under KMS can’t shave off more than 1 frame of input lag compared to the current version of RetroPie, I’m not overly optimistic.

[b]Disclaimer:[/b]

– There’s of course some uncertainty in the measurements due to recording at just 60 FPS. However, with around 30 attempts for each test, a pretty clear trend could be seen.
– It would have been interesting to test with more NES and SNES games, but I didn’t have time for that.
– I can’t guarantee that the HP Z24i doesn’t add some measurable latency.
– Different display hardware (AMD, Intel, Nvidia) could very well affect the outcome.

Also try enabling usbromservice from the RetroPie setup script

what is the output of “tail /var/log/syslog” after plugging in the usb stick ?

Please double check you formatted as fat32, and not exFAT. Also please make sure the folder name is all lowercase.

Hi guys, I second the opinion that the pi-bluetooth service or ps3 service are at fault. I connected one of the controllers through the USB cable and the emulators have run for 4 hours straight with no problems. I tested Mario Kart for n64, TOCA2, Final Fantasy VII, Tekken 3 and Carmageddon for PSX and there was no problem, even though in the past my system froze in each and every one of those games.

To finish the test I exited the emulators and tried to connect the second controller via Bluetooth. The controller didn´t even have time to pair and emulatorstation froze. I guess I´m stuck with wired controllers for now, but I´d still try to get to the root of the problem.

Could there be a communication problem between the PS3 wireless service and the bluetooth service? I have yet to find other posts on the internet complaining that bluetooth on the rPi froze the system.

you can use a usb keyboard if you have one common keys should be
A = X
B = Z
Y = A
X = S
Start = ENTER
Select = R-SHIFT
Shoulder left = Q
Sjoulder right = W
D-pad left = left
D-pad right = right
D-pad up = up
D-pad down = down

Just to be sure (and apologies if been asked before) but does this solution also works for the THT ARCADE CONSOLE 2P USB controller (similar to Xin Mo but distributed by Time Harvest).

thanks..

Just to be sure (and apologies if been asked before) but does this solution also works for the THT ARCADE CONSOLE 2P USB controller (similar to Xin Mo but distributed by Time Harvest).

thanks..

in emulation station you need to configure the input in the menu screen. When i configured my ps3 controller i had to have a usb controller plugged in first and then after pairing i needed to press start and go to configure input. It should say 2 joy pads detected. I held the A button down on my ps3 controller and it found the controller and then I setup all the buttons. After that I was able to use it.

Thanks for the info, Bengus. For what it’s worth the workaround mentioned on that page to disable the built in bluetooth didn’t work for me, the pi could not detect the Dualshock over the usb bluetooth.

But at least we know what might be the problem so it can be fixed by those skilled in the mystic arts ^^.

I’m still worried though that the problem for me seemed to occur far more often in ‘demanding’ emulators. I certainly can say I had no problems with my bluetooth PS3 controller using Retropie versions 2.6 – 3.2 on my Pi2, aside from the odd disconnection (easily solved ingame by unplugging and replugging the usb bluetooth dongle).