@ckswenson Third Party images with custom configs and pre-loaded ROMs are not supported here. Go ask Mr .Death for tech support.

@sik i thought this was just me. The only emulator it works in is n64 for some reason

@silverbullet
So I did a little detective work.
It looks like in RetroPie 4.4/Stretch the /var/log/sixad file was removed and the logs for sixad are sent to journald ("/run/log/journal/44377289e4ad47738189eab7cbdb463a/system.journal" on my Pi) and i'm not sure if the script can read from that file as it contains a bunch of different logs.

to test this you can try changing batCheck.py from
"logPath='/var/log/sixad'" to "logPath='/run/log/journal/44377289e4ad47738189eab7cbdb463a/system.journal'" (note the big string of characters in the file path is probably different on your Pi!) and then running the script

@G2bb

While there are a few good ways to make a standard controller be seen as a keyboard, I don't know of anything that would do the reverse. There's a proposed way to do it with xboxdrv, but the project hasn't been touched since late 2015. However, seeing as how all these emulators and ports are first and foremost computer software, they all have keyboard support that can even be a bit more versatile in many cases.

Using RetroArch as a jumping off point, if you can determine which keys are assigned to which buttons, the controls can be added manually to /opt/retropie/configs/all/retroarch.cfg. Below is an example of my setup that you can use as a reference.

input_player1_a = "a" input_player1_b = "b" input_player1_y = "y" input_player1_x = "x" input_player1_start = "t" input_player1_select = "e" input_player1_l = "l" input_player1_r = "r" input_player1_left = "left" input_player1_right = "right" input_player1_up = "up" input_player1_down = "down" input_player1_l2 = "d" input_player1_r2 = "f" input_player1_l3 = "c" input_player1_r3 = "v" input_player2_a = "k" input_player2_b = "m" input_player2_y = "o" input_player2_x = "n" input_player2_start = "num9" input_player2_select = "num0" input_player2_l = "p" input_player2_r = "q" input_player2_left = "g" input_player2_right = "h" input_player2_up = "i" input_player2_down = "j" input_player2_l2 = "s" input_player2_r2 = "u" input_player2_l3 = "w" input_player2_r3 = "z"

@TMNTturtlguy yup. But if i need a bulk set of games that use the same core options or same retroarch.cfg options, i have their individual configs pointing to a different core-options or retroarch.cfg file that i created. So for example psx games that use analog option, i would point their individual config to a different core-options config that i created just for psx that has the analog enabled. That way if the core options ever have any changes made, i dont have to change each config, just the one.

@DarkWolf mhhh i have not test the ps4 controller yet. With my Arcadestick and retropie i think it is approximately every 10th step. With recalbox i got the trouble more often. (that is the reason i give retropie a try again)

Should work, just depends if the pi recognizes it as a ps3 controller.

Yes it was set to background. I'm guessing it should be "default"? I've set the config to default and rebooted. Will run upstairs to check that the controller still works!

Thanks!

@mike1234 How?

It might be helpful for other users 😊

@JonathanK 3 separate commands. Wait for each one to do its' thing then enter the next. Yes F4.

@Rickt1962

Do you have an original controller? Or is it a clone PS3 ccontroller? How well does the bluetooth work? Are you using a dongle of Pi3´s own bluetooth?

@edmaul69 Sweet, I was looking for something like this before. After some testing I have noticed something. When turning on the Pi or rebooting it with cables plugged in for different controllers, I can have them set in their respective ports 0,1,2 etc and my PS3 controller will not become JS0 it will become whatever light is shown on the PS3 controller i.e. JS1 it will be player 1 on the controller light.

If I reboot and unplug every wire so the USB ports are empty and connect it to blue tooth as it's booting, my controller blinks for a bit then stops and shows no lights. I've had this happen before on macs and the controller still works even though it's not indicating a "player." When the controller is like this it is JS0.

So it appears that if you want your PS3 controller to be JS0 and not JS1-4 potentially, you need to connect it as it's booting through bluetooth with nothing else plugged in the USB ports.