Verified. It is not possible to configure a usb connected ps3 controller. But it is possible to use one if it is already configured. Strange. I will take a look.

Same issue. I am new to retropie and have a Pi3 on the latest version of retropie.
bluetooth firmware is updated.

If I connect the controller for the initial setup via a usb cable it reports “1 gamepad connected” holding down a button says “PS 3 controller detected” and starts setup.
I can start mapping the buttons but after a few seconds the controller stops responding.

If you are really quick you can get down to the “OK” but can’t select it.

Removing the usb cable and it will not work over bluetooth.

Any help appreciated.

First thing to make absolutely sure it that your Pi is not under powered. Very strange things happen if the peripherals that are connected to your Pi do not get enough power. Use a powered USB hub and make sure your Pi is connected w/ a 5 Volt 2 Ampère adapter.

Then check if Linux “sees” the USB disk w/ the command:

df -h
(meaning: disk free in human readable format, i.e. GB, MB instead of just bytes). Linux can read almost any file system format: ntfs, ext2/3/4, hfs, fat, fat32, etc. etc. So the Pi is probably able to “handle” it.

Succes!

[quote=119820]Usb connected? If you use ps3 controller without bluetooth remove sixad driver. The linux kernel has an builtin driver. Your PSU could be to weak.

[/quote]

Good idea. I’ll try a different power supply, and see if that’s the problem.

Usb connected? If you use ps3 controller without bluetooth remove sixad driver. The linux kernel has an builtin driver. Your PSU could be to weak.

Just thought I’d add some observations here as well. I notice input lag in RetroPie as well. It’s not a big issue when I use it on a computer monitor, but it is an issue for some types of games when I use it on my Samsung plasma.

I used a very crude method of getting an idea of the input lag. I only had a 30 fps camera available and I used that to film while I performed quick taps on the controller and mouse I used for testing. I’ve taken the liberty of multiplying the number of frames I counted in my recorded material by two, since that better corresponds to the actual number of frames rendered by the source (since it runs at 60 FPS).

The PCs were tested at the Windows desktop, recording the response from the built-in game controller configuration program and from double-clicking to select text in Notepad. [Granted, that’s a bit apples and oranges, so I’ve added some actual RetroArch measurements in an edit further down.]

[b]Hardware & software[/b]

– Raspberry Pi 3 with RetroPie 3.6 and Super Mario World 2: Yoshi’s Island
– Core i7-6700K with Windows 10
– Core i5-5300U with Windows 7
– Samsung plasma TV
– HP Z24i desktop monitor (24″, 1920×1200, IPS)

[b]Results[/b]

RetroPie + Samsung plasma TV: [b]12 frames (200 ms)[/b]

RetroPie + HP Z24i: [b]8 frames (133 ms)[/b]

Windows 10 + HP Z24i: [b]4 frames (67 ms)[/b]

Windows 7 + HP Z24i: [b]2 frames (33 ms)[/b]

I know of one test that has measured the HP monitor’s input lag and found it to be almost non-existent (less than 1 ms). That would put the plasma at around 60-70 ms, which sounds plausible. I tested many times and these results were quite consistent.

So, RetroPie on the HP monitor responds approximately 100 ms slower than the Windows 7 laptop using the same HP monitor. That’s a very significant difference, but the Windows 7 laptop also wasn’t running an emulator.

I love RetroPie, but this issue (which, granted, may have nothing to do with RetroPie itself) kind of kills it for me. A lot of the games I play/want to play on it are fast paced and rely on exact timing to succeed. And I have definitely noticed that they’re harder because of this.

Is there any work being done on attempting to profile this and come up with a solution?

[b]EDIT:[/b]

Did some more testing with the Windows 7 machine, using RetroArch and Yoshi’s Island:

[b]8 frames (133 ms)[/b] with Snes9x Next and video_hard_sync = false
[b]6 frames (100 ms)[/b] with Snes9x Next and video_hard_sync = true
[b]4-6 frames (67-100 ms)[/b] with bsnes (balanced) and video_hard_sync = true

video_hard_sync did not seem to have any effect on RetroPie, but it did seem to shave off a couple of frames in the Windows case.

What’s interesting here is that I could not come close to reproduce the input reponse from the Windows desktop (2 frames). Input response time (with video_hard_sync disabled) was actually the same as using RetroPie. Does the emulator really need that much time to output to the screen?

[b]EDIT2:[/b]

I just tested the input lag when typing at the command line in RetroPie. A typed character shows up in the next recorded frame, which means that input lag is 33 ms at the most.

So, the Raspberry Pi and the PCs have similar low latency input when just reacting on USB input (such as writing on a keyboard). All devices also seem similarly slow to react on input when running the SNES emulator, although video_hard_sync = true seems to help the PCs slightly.

This shipped for under $3.00 (been using them for years, they are solid)

http://www.ebay.com/itm/2-Ports-PS2-to-PC-USB-Game-Controller-Converter-Adapter-Adaptor-New-/131741244812?hash=item1eac63dd8c:g:PB0AAOSwYlJW1tcb

Along with PS1 or PS 2 dual analog controllers.

Configure intially with analogs turned on, and you are set.

Depends on the games you want to play. Some reproduction classic controllers (w/ an USB plug) do not have all the buttons you’d like to have on, for instance, the Playstation 1. But the one Apocolips18 probably refers to (the iBuffalo repro USB SNES controller) is very nice. But any USB PC controller should do.

i have done exactly the same thing and that works without a problem.. my picade (usb keyboard encoder) is set to player 1 and player 2 i using my gamepad it works fine for all retroarch emulators. For mame4all you have to set it up manually using tab config.

I think although not certain withouth looking at my config (can’t check at work atm) is that you need to change / play with input_player1_joypad_index = “0” input_player2_joypad_index = “1” in retroarch.cfg i manually edited that file and it works fine. I can post my file if i come home if you like or you can try and have a look at those joypad indexes but i’m not certain it was that setting

Also in the tab config pressing Select ui button (default enter i think or a certain gamepad button) and the cancel button (default escape) sets the input to none so you can start cleanly to assign a button / direction i think i did that as well for every button where the joypad was also mapped to player 1 i just deleted those (set those to none) and then reassigned the keyboard (only) controls for player 1 for player 2 (gamepad) i did the same also

Typo, I meant 1050Mhz.

Why not install the img to usb, then take the boot partition and copy that to an sd, then change the cmdline.txt to point to sda2 instead?

My problem is that I want to set the player 1 keys to keyboard and the player 2 to a USB pad, but when I try to configure player 1 with tab, if I press up, it gets up keypad 1 up, so my player 1 and player 2 controls, control player one both.

I don’t know if I’ve expressed well…

yeah i still have to test more but i already noticed once of the hacks (which said speedup) actually decreased performance when i last tested before going to work. Didn’t had time to test other games yet, cause i seem to be having an input problem as well before i left. for some reason one of my button presses on my picade doesn’t register constantly making acceleration in games like ridge racer and toca race driver 2 not work. Don’t know why though but it did work with my joypad hooked up to the pi. I’m not that concerned about it.

1500mhz on a pi 2 isn’t that like a huge overclock ? i have a pi2 as well did not try yet to boot my sd card in the pi2 to see what the diffrence is like.

I might start with a clean config again when i get home and test each setting individually using savestates on for example star ocean 2 in the town after the 1st (little) fight cause that game out of all the ones i tested had the worst performance. Not sure if it’s a good way to go though settings that work for one game might not work for others and certain games have problems with certain hacks like mediëval resurrect with the timing hack as far as i can remember without testing. It locked up on the main menu well just before the main menu appears if i had that enabled. But would need to check again to be sure if that was actually the setting. It was one of the 1st games, besides tekken that i tested.

Also i’m not certain if this could have an impact on performance but i removed the roms/psp folder and made a symblic link for roms/psp to /media/usb0 i’m not certain but i do not think symbolic links could have a performance impact can it ?

i’ll try y’s series as well to see if there’s a diffrence, i noticed ridge racer 2 was running already a lot better then any other game i tried although could not really test due to the input problem and possibly bugs due to hacks / speedups checked (the road / surroundings was all black).

I’ll post again when i tested more games / played more with the settings

If you install Retropie to USB and only boot off the SD, you’ll get less pauses. The rest you pretty much have to go in comparison with the compatibility chart.

I can say for sure that a lot of the PSP minis work just fine, as do the RPG’s like the Y’s series, and that only at 1050Mhz on the Pi 2 for me.

EDIT: Typo on Mhz

Still waiting on my Pi 3s to arrive, so I tinkered with over clocking again and settled with this:

arm_freq=1050
core_freq=525
sdram_freq=450
over_voltage=3

Using a standard USB stick I don’t need extra voltage to the USB, which seems to conflict with over clocking, so it’s either that or a hard drive that can power itself.

i can reproduce the same problem with my ps3 controller when using the 3.6 Image (tested on PI2 & 3 and two different original ps3 controllers )
It works on bluetooth on the pi3 but i doesn’t work using only usb

On another SD Card i have an upgraded 3.6 Version (using since 2.4 or something) on that one everything works fine.

The iBuffalo USB controllers have worked great for me thus far (I am pretty new to RetroPie and Raspberry Pie) and I have not had any issues with them up to this point. Also good price range which was a plus.

[quote=119398]No the controller is good it works fine on my Mac and it works fine with PiPlay so can’t see why retropie it fails.
[/quote]
Me neither… Did you connect this controller directly to an USB port of the Pi? Not via an USB-hub? And is the power adapter of your Pi “strong enough”? That is, 5 Volt and at least 2 Ampère? This really puzzels me.

How RetroPie, Emulationstation and Retroarch work to register the controller is vague and still a mystery to me. So I don’t know which of their scripts to use best. But if you escape to the command line of your Pi by pressing F4 on your keyboard and pressing Enter after that you should end up on the command line.

On the command line run (press TAB each time to complete the command):
jstest /dev/input/js0
(you might need to install this command first by running sudo apt-get install joystick.)

That should present you w/ screen full of axes and button status info from your controller (press CTRL + C to exit from it). If the above command leaves you w/ the following error message then Linux (i.e. your Pi itself) does not see a controller:
jstest: No such file or directory
That means that the file /dev/input/js0 does not exist and therefore that the controller was not “seen” by Linux.

Return to Emulationstation by typing emulationstation (again, use TAB to complete the command ) on the command line and press Enter.

Need update under 3.6

3.1 allowed for this to work: https://www.petrockblock.com/wp-content/uploads/2015/07/Getting-strated-with-Retropie.pdf

However it isn’t working under 3.6

Have all my roms on USB HDD, just want to be able to play them again, from the HDD.

Does the cmdline.txt method still work in the latest version of retropie? This one:

usbhid.quirks=0x16c0:0x05e1:0x040

Cheeers