It happens for me too, with my

8Bitdo NES 30 Pro and FC 30 Pro.

i have 4 of them connected to my System.
Before 17.12.02 all of them worked fine after i setup them on bluetoothctl.
Now after the update, it is russian roulette after each restart if i have to pair them again entirly.

I don't know what has been changed, but it broke something for bluetooth connection.

@substring

yeah but that was with Mame, i would like to use them for PSX. I honestly havn't found enough information if this would also work.

Hello everyone.

I checked some threads now but was not successful on file ding an answer about this topic.

Will there ever be an emulation. For recalbox which can work with lightguns?

I know that the old lightguns needed the infrared stuff and only works on a cRt

But I wonder if we could emulate this with a Kamera like the cinect and An open source api for the cinect.

Which would interpret the controller on a fence which acts as the screen size.

Kind regards
Tepoo

Normal behaviour when the screen has a low quality and creates to much temp.

You have 3 possible ways

1. buy one which has a better quality
2. deal with it
3. find a solution to compensate the temp.

Kind regards
Tepoo

@substring said in [REQUEST] Update XU4 Kernel to 4.0+:

@tepoo https://github.com/recalbox/recalbox-os/wiki/Connect-bluetooth-controller-manually-(EN)#if-your-recalbox-version-is-41x-or-later

weird,

if i search for bluetoothctl on the github it sais nothing found on that repository.
i guess the search function is not working pretty well.

@farbkasten

i am not sure if this website will work correctly.
a cue file is not just a list of the bins, it also contains correct timestamps.
if they are wrong, the game will end up somewhere in a blackscreen.

best example for this is Tekken3, which endsup in a blackscreen after the arcade mode, if the CUE file is not 100% correct.

@substring

don't get me wrong, but would you mind linking me the part about bluetoothctl on your wiki?
i spend 1 week of researching through google and your wiki, to find a solution for this. and i ended up alot with bluetoothctl on google, but not on your wiki, also for someone who is not into bluetooth console based handling that much, it is not very logical that the bluetoothctl system works oob but the recalbox gui itself fails on this by saying "No Controller found".

@Basti
i did what you suggested, and trusted the devices indeed, but it does not work.
based on my last tests, it was always neccessary to go into bluetoothctl and first make "power on" and "agent on" before i was able to pair the devices.
so trusting the devices, will not help alot here, would it?

Kind regards
Tepoo

Hello Everyone,

i am looking right now into solutions, how to be able to have all controllers connected on startup to not always have to deal with it.

one solution i found is expect. a console automation which seems to work quite well.

the only problem is that i do not find a way to bring it to my recalbox to test if it would work.

does someone know how todo this? or knows another good way for auto connecting the bluetooth controllers, which have been paired already after restart directly again?

i still wonder why nothing is yet implemented for this.

was thinking to implement like a script which runs every 5 seconds as long as no game has been started, to check for bluetooth controllers and connect them if they are already known.

Kind regards
Tepoo

the tip from basti works.

the onlything which is abit annoying right now is that the controllers does not auto pair on startup or restart.

and yes, i would also love to see the upgrade to 4.14.

Thanks for answering to my problem, i highly appreciate this Keep up the nice work guys.

King regards

You are right, over the bluetoothctl it works oob.

all of them.

Thanks alot.