#DUALSHOCK 3 PC INPUT LAG BLUETOOTH#
Testing it with " sudo l2ping AA:BB:CC:DD:EE:FF" reveals (for me anyway) a relatively consistent ~12ms round trip ping time, suggesting a potential ~6ms input lag/latency delay over bluetoothĤ bytes from AA:BB:CC:DD:EE:FF id 0 time 13.81msĤ bytes from AA:BB:CC:DD:EE:FF id 1 time 11.28msĤ bytes from AA:BB:CC:DD:EE:FF id 2 time 12.32msĤ bytes from AA:BB:CC:DD:EE:FF id 3 time 12.29msĤ bytes from AA:BB:CC:DD:EE:FF id 4 time 12.27msĤ bytes from AA:BB:CC:DD:EE:FF id 5 time 12.14msĤ bytes from AA:BB:CC:DD:EE:FF id 6 time 12.36msĤ bytes from AA:BB:CC:DD:EE:FF id 7 time 12.26msĤ bytes from AA:BB:CC:DD:EE:FF id 8 time 12.27msĤ bytes from AA:BB:CC:DD:EE:FF id 9 time 12.14msĤ bytes from AA:BB:CC:DD:EE:FF id 10 time 28.64msĤ bytes from AA:BB:CC:DD:EE:FF id 11 time 18.44msĤ bytes from AA:BB:CC:DD:EE:FF id 12 time 12.30msĤ bytes from AA:BB:CC:DD:EE:FF id 13 time 12.28msĤ bytes from AA:BB:CC:DD:EE:FF id 14 time 12.11msĪt this point, play over bluetooth is (for me) indistinguishable from play over direct USB connection on the Raspbery Pi 3. This (I think) switches things so that the Pi is the Master and ping times are considerably reduced. Replacing AA:BB:CC:DD:EE:FF with the PS3's address. $ sudo hcitool sr AA:BB:CC:DD:EE:FF slave This seems to switch the refresh/polling/delay time rate to the lowest possible bluetooth setting of ~6ms.ī) Switching bluetooth connection to slave mode
#DUALSHOCK 3 PC INPUT LAG PS3#
And this is achievable if the PS3 controller is set from being the MASTER in the bluetooth connection to the SLAVE instead. Notice that 13ms ping round trip time which occasionally appears, suggesting that a ~7-8ms input lag time is in fact possible. This improves gameplay considerably, but there is still some noticeable input lag, which affects many platformers. Even at this stage, we have perhaps ~18ms of input lag from bluetooth - just over half a frame. I realise this may not be an option for everyone, but the reality is that bluetooth and WiFi do interfere.) (Note: Wifi is now permanently off until the command " sudo iwconfig wlan0 txpower on" is run and the Pi rebooted. Testing it with " sudo l2ping AA:BB:CC:DD:EE:FF" reveals (for me anyway), a ~20ms ping time improvement, translating into a 10ms reduction in input lag/latency.Ĥ bytes from AA:BB:CC:DD:EE:FF id 0 time 13.70msĤ bytes from AA:BB:CC:DD:EE:FF id 1 time 36.19msĤ bytes from AA:BB:CC:DD:EE:FF id 2 time 34.83msĤ bytes from AA:BB:CC:DD:EE:FF id 3 time 36.08ms In console, type the following command (warning this will disable wifi until txpower is turned back on AND the Pi is rebooted) to disable the transmission power of the Pi3's onboard wifi (this also reduces temperatures slightly I have found) Now, an immediate improvement can be obtained by This is a very noticeable amount of lag during gameplay. These are round trip ping times, so I presume the actual input lag/latency is around half of this. Ĥ bytes from AA:BB:CC:DD:EE:FF id 0 time 53.73msĤ bytes from AA:BB:CC:DD:EE:FF id 1 time 54.29msĤ bytes from AA:BB:CC:DD:EE:FF id 2 time 16.00msĤ bytes from AA:BB:CC:DD:EE:FF id 3 time 53.73ms Replacing AA:BB:CC:DD:EE:FF with your devices address. Now, to test the connection to this device type Where one of the address AA:BB:CC:DD:EE:FF shown is your (PS3) bluetooth controller. > ACL AA:BB:CC:DD:EE:FF handle 11 state 1 lm MASTER The address of the Bluetooth device can be found somewhere in the bluetooth menu, but to get it in the console type (Without the $) While input lag can be felt subjectively during play, it's also possible to get a more objective measure by pinging the bluetooth device itself(We will be using the console for this fix). However when using bluetooth, there is a VERY noticeable input lag making the characters in game feel sluggish and sticky.
#DUALSHOCK 3 PC INPUT LAG TV#
When the controller is plugged in directly to the USB port, there is no noticeable input lag delay (Yes my TV is tuned to game mode and Retroarch is not using any filters/mods. The controller is set to use udev and the firmware hack is off (I don't think either of these matter though).
I have set up the PS3 Controller for bluetooth play using the 8bitdo guide, which my understanding is the default bluetooth option in 4.1.
A) Coexistence of Bluetooth and Wifi, B) Whether the bluetooth controller is in master or slave mode. To summarise, I have identified two actual sources of input lag which affect the PS3 controller, and possibly others. However I believe this will work on Pi 3's with the PS3 controller, and possibly other controllers as well. I am using Retropie v4.1, but I must add that this is not entirely stock as Retroarch was updated and I have installed then uninstalled the ps3controller packages. I have only tested this with a PS3 DualShock 3 controller, on a Raspberry Pi 3.
I think I have a fix which reduces a lot of Bluetooth input lag (latency).
0 kommentar(er)
