Made this post because I’m seeing a lot of scripts with actions that are too fast / slow to be executed properly.
Most device limits the speed in their firmware. If an action is too fast, the firmware will reduce the length of it in order to perform it in time.
From the “Statistics” window in OFS you can check the speed of the action. Here, the speed is over 1000 unit/s. Too fast for any toys to perform correctly.
In the Handy’s case, speed is capped at 500 unit/s by its firmware. When playing this script on a Handy, the stroke length will be reduced to less than half of the original.
Whilst it is okay to have strokes exceed that limit, you must be careful at how it actually plays out. In this case, because the first point is at the top position, these strokes will be shortened towards the top, stroking the tip only. If we are scripting a scene with full insertion, this is not ideal.
Turn on “Max speed highlight” in your OFS settings. This option highlights all overspeed strokes.
Keep things under control by keeping them within the speed cap. Reduce stroke length, and shift points if necessary.
The “Modify Script” feature on Funscript.io provides a visualisation of how your script’s fast actions will actually plays out by the device.
Most commercial strokers also have problem playing slow actions. The Handy for example, has a minimum cap around 33 unit/s. When a stroke sits below this threshold, you’ll notice a period of stopping before / after the stroke.
Sometimes, the firmware alters the actions so it can be played in the smoothest possible way, resulting in different timing than what the script suggest.
For more information on the Handy’s behavior over slow actions, read this topic:
Try exaggerating the stroke length, thereby increasing the stroke speed.
You can speed up the stroke by purposefully adding stops before, after, or within it. This still causes stopping, but at least you can control where it happens.
Wiggling - You can split the long, slow action into numerous smaller, faster ones that are beyond the minimum speed.
My own approach is to add tiny vibrations to the stroke. This is a stylized technique that works well for my content (animation), but is not endorsed by everyone.
@kinetics made a detailed guide on scripting slow actions for the Handy:
Also note that the OSR stroker robots can handle very slow strokes, as it communicates with the player software in high-frequency commands via serial connection. So slow actions isn’t really an issue for these.
Contribution to this wiki-post is welcomed.