Just speaking from experience. If your experience with a specific device differs, please share
(When talking about Bluetooth I’m speaking about BLE and its most common implementation, where commands are executed as they are received, without any predictions and caching. Bluetooth itself is a capable medium, it’s just sad that most implementations are bad.)
This script is compatible with all devices.
This script is widely compatible. On Bluetooth it won’t feel different.
This script is best with Wi-Fi and USB. On Bluetooth it may feel less smooth due to noticeable stutters.
And some notes:
-
There is a diminishing return. A simple triangular wave already makes people cum. One middle points per stroke can make a significant difference and represent actions more accurately. Two makes it very detailed. The nuance brought by three and above is hardly noticeable, let alone the compatibility issues it may causes.
-
Don’t go frame-to-frame to add points just to match the static frame. Only add them when you think it’ll make a difference, such as representing a drastic speed change performed by the actor.
-
For fast actions > 380 unit/s, don’t add extra points. They are hardly noticeable and may mess with the device’s behavior. In fact, your device naturally decelerates at both end, so there’s no need to tell it to.
-
Slow actions can use more intermediate points. However do mind the minimum speed limit of some devices.
-
Note all of these are based on the assumption that you want to be efficient. If you want to hone a highly detailed script out of love and your device can handle it, nobody is stopping you!