Are you using a pi3 without a bt dongle ? We don't support the pi3 bt yet

@subs thank you. I'm new to python so just knowing thats the route is a big help. So far using one relay to toggle the power state of the pi is working very well. it's nice to have all my custom lighting and speaker/monitor turn fully off while operating the pi with the same switch.

I'm so sorry I wrote that I started my Nes30 Pro pads by pressing Start, instead of pressing POWER. The correct one is of course POWER, only POWER. So sorry!

@Marius-Hecht Gerne. Ich mache den hier dann zu.

@derbaron Hi! Have you checked this? https://github.com/recalbox/recalbox-os/wiki/Compatibility-(EN)

Hello
you need to edit recalbox.conf and active xboxdrv driver.
https://github.com/recalbox/recalbox-os/wiki/recalbox.conf-(EN)
it must resolved the problem

------------ D2 - XBOX Controllers ------------ Xbox controllers are already supported, but xboxdrv can solve some compatibility issues Enable xboxdrv driver, disable this if you enabled ps3 controllers (0,1)

controllers.xboxdrv.enabled=0

Set the amount of controllers to use with xboxdrv (0..4)

controllers.xboxdrv.nbcontrols=2

thanks for the help, Got the following info this is all the buttons and joystick outputs. Looks like some <p style="text-align: left;"> Testing ... (interrupt to exit)</p> <p style="text-align: left;">Event: time 1468867888.810859, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70060</p> <p style="text-align: left;">Event: time 1468867888.810859, type 1 (EV_KEY), code 72 (KEY_KP8), value 1</p> <p style="text-align: left;">Event: time 1468867888.810859, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867888.890830, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70060</p> <p style="text-align: left;">Event: time 1468867888.890830, type 1 (EV_KEY), code 72 (KEY_KP8), value 0</p> <p style="text-align: left;">Event: time 1468867888.890830, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867889.554908, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7005e</p> <p style="text-align: left;">Event: time 1468867889.554908, type 1 (EV_KEY), code 77 (KEY_KP6), value 1</p> <p style="text-align: left;">Event: time 1468867889.554908, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867889.666927, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7005e</p> <p style="text-align: left;">Event: time 1468867889.666927, type 1 (EV_KEY), code 77 (KEY_KP6), value 0</p> <p style="text-align: left;">Event: time 1468867889.666927, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867890.034960, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7005a</p> <p style="text-align: left;">Event: time 1468867890.034960, type 1 (EV_KEY), code 80 (KEY_KP2), value 1</p> <p style="text-align: left;">Event: time 1468867890.034960, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867890.130986, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7005a</p> <p style="text-align: left;">Event: time 1468867890.130986, type 1 (EV_KEY), code 80 (KEY_KP2), value 0</p> <p style="text-align: left;">Event: time 1468867890.130986, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867890.571018, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7005c</p> <p style="text-align: left;">Event: time 1468867890.571018, type 1 (EV_KEY), code 75 (KEY_KP4), value 1</p> <p style="text-align: left;">Event: time 1468867890.571018, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867890.643025, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7005c</p> <p style="text-align: left;">Event: time 1468867890.643025, type 1 (EV_KEY), code 75 (KEY_KP4), value 0</p> <p style="text-align: left;">Event: time 1468867890.643025, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867891.523120, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0</p> <p style="text-align: left;">Event: time 1468867891.523120, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1</p> <p style="text-align: left;">Event: time 1468867891.523120, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867891.627127, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0</p> <p style="text-align: left;">Event: time 1468867891.627127, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 0</p> <p style="text-align: left;">Event: time 1468867891.627127, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867891.979205, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e2</p> <p style="text-align: left;">Event: time 1468867891.979205, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1</p> <p style="text-align: left;">Event: time 1468867891.979205, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867892.091177, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e2</p> <p style="text-align: left;">Event: time 1468867892.091177, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0</p> <p style="text-align: left;">Event: time 1468867892.091177, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867892.427211, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7002c</p> <p style="text-align: left;">Event: time 1468867892.427211, type 1 (EV_KEY), code 57 (KEY_SPACE), value 1</p> <p style="text-align: left;">Event: time 1468867892.427211, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867892.547227, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7002c</p> <p style="text-align: left;">Event: time 1468867892.547227, type 1 (EV_KEY), code 57 (KEY_SPACE), value 0</p> <p style="text-align: left;">Event: time 1468867892.547227, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867892.963286, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e1</p> <p style="text-align: left;">Event: time 1468867892.963286, type 1 (EV_KEY), code 42 (KEY_LEFTSHIFT), value 1</p> <p style="text-align: left;">Event: time 1468867892.963286, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867893.067298, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e1</p> <p style="text-align: left;">Event: time 1468867893.067298, type 1 (EV_KEY), code 42 (KEY_LEFTSHIFT), value 0</p> <p style="text-align: left;">Event: time 1468867893.067298, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867893.419326, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001d</p> <p style="text-align: left;">Event: time 1468867893.419326, type 1 (EV_KEY), code 44 (KEY_Z), value 1</p> <p style="text-align: left;">Event: time 1468867893.419326, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867893.523339, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001d</p> <p style="text-align: left;">Event: time 1468867893.523339, type 1 (EV_KEY), code 44 (KEY_Z), value 0</p> <p style="text-align: left;">Event: time 1468867893.523339, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867893.875375, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001b</p> <p style="text-align: left;">Event: time 1468867893.875375, type 1 (EV_KEY), code 45 (KEY_X), value 1</p> <p style="text-align: left;">Event: time 1468867893.875375, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867893.987384, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001b</p> <p style="text-align: left;">Event: time 1468867893.987384, type 1 (EV_KEY), code 45 (KEY_X), value 0</p> <p style="text-align: left;">Event: time 1468867893.987384, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867894.499457, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70006</p> <p style="text-align: left;">Event: time 1468867894.499457, type 1 (EV_KEY), code 46 (KEY_C), value 1</p> <p style="text-align: left;">Event: time 1468867894.499457, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867894.595485, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70006</p> <p style="text-align: left;">Event: time 1468867894.595485, type 1 (EV_KEY), code 46 (KEY_C), value 0</p> <p style="text-align: left;">Event: time 1468867894.595485, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867894.995523, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70022</p> <p style="text-align: left;">Event: time 1468867894.995523, type 1 (EV_KEY), code 6 (KEY_5), value 1</p> <p style="text-align: left;">Event: time 1468867894.995523, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867895.083510, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70022</p> <p style="text-align: left;">Event: time 1468867895.083510, type 1 (EV_KEY), code 6 (KEY_5), value 0</p> <p style="text-align: left;">Event: time 1468867895.083510, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867895.947606, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70020</p> <p style="text-align: left;">Event: time 1468867895.947606, type 1 (EV_KEY), code 4 (KEY_3), value 1</p> <p style="text-align: left;">Event: time 1468867895.947606, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867896.107625, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70020</p> <p style="text-align: left;">Event: time 1468867896.107625, type 1 (EV_KEY), code 4 (KEY_3), value 0</p> <p style="text-align: left;">Event: time 1468867896.107625, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867896.475667, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001e</p> <p style="text-align: left;">Event: time 1468867896.475667, type 1 (EV_KEY), code 2 (KEY_1), value 1</p> <p style="text-align: left;">Event: time 1468867896.475667, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867896.563696, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001e</p> <p style="text-align: left;">Event: time 1468867896.563696, type 1 (EV_KEY), code 2 (KEY_1), value 0</p> <p style="text-align: left;">Event: time 1468867896.563696, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867897.211789, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70021</p> <p style="text-align: left;">Event: time 1468867897.211789, type 1 (EV_KEY), code 5 (KEY_4), value 1</p> <p style="text-align: left;">Event: time 1468867897.211789, -------------- SYN_REPORT ------------</p> <p style="text-align: left;">Event: time 1468867897.283758, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70021</p> <p style="text-align: left;">Event: time 1468867897.283758, type 1 (EV_KEY), code 5 (KEY_4), value 0</p> <p style="text-align: left;">Event: time 1468867897.283758, -------------- SYN_REPORT ------------</p> <p style="text-align: left;"></p>

I get the feeling most questions would be more likely to get answered if we asked them in the relevant core's forum, or emulationstation forum, etc.

shift gears ? 😄 Do these games use triggers and not buttons to accelerate ?

To be clear: The stick IS operating as analog. But the zone of movement where it is analog is very small, kicks in at a relatively high value (presumably at least 4096,4096), and reached 100% input almost immediately with only a very small movement. There is a large area towards the outside of the movement circle, seems like more than half of it, where all movement is at 100% despite not being anywhere near the physical limit of the stick movement. black=no effect grey= effect, engages suddenly at high value, and quickly reaches 100% with very little movement. white=100% effect, reaches 100% well before stick physically reaches edge of range. ^^^ bad ^^^ Modern controller sticks self-centre, so a huge analog deadzone is redundant, and suddenly outputting 100% effect when it's nowhere near 100% of it's physical movement range.. is very tedious.

re: CRT only. Right. So then faux-lightguns.... Is the use of mouse and wii controller likely to be included soon?

NOW WORK AWASOME!!!!!! thanks you a lot!

the button mapping is made on my experience : the 2 lower buttons can easily be pressed by mistake. So, when playing you could combo HK+A and ... reset your game ... so HK is on a flipper button, select is on the right of those 2 buttons, and start is ... well, no need to say 🙂

I finally figured out how to access the recalbox.conf  tool through wifi on my Mac and was able to save from there eventually after lots of false starts.  It's working now and I'm very impressed with recalbox.  Nice work developers, really nice work.  Thank you for your work.

Many thanks Acris, I appreciate the fast response.   Tim

of course all the configs is ready   and plug it, wait 10 seconds, push PS button then unplug  <span style="line-height: 1.5;">of course</span>

Hello @Gerickt I need your es_input.cfg to add your gamepad out of box in recalbox. in ssh : /recalbox/scripts/recalbox-support.sh Can you upload the archive request in this page : https://github.com/recalbox/recalbox-os/wiki/Recalbox-support--(FR)