Smoother movement as an option in FW4+
Firmware 4 introduces a more mechanical and direct movement when switching direction compared to FW3, which was smoother. In my opinion, this feels worse. Additionally, most existing funscripts were created with the previous built-in smoothing in mind.
My suggestion is to add the option to turn on a smoother movement in Handy settings and in the API. Maybe there could even be different levels of smoothness.
Comments: 4
-
20 Nov, '24
HandyAlexander AdminHi. We agree that FW4 might feel more robotic. The problem is that FW4 moves more correctly to the scripts and that the scripts themself are scripted mechanically. Most scripts only have top and bottom points, resulting in mechanical motion if followed correctly. FW3s motor driver is not as smart as FW4s motor driver and has a build-on more organic motion to it. The problem is that the motion FW3 outputs are different from the script.
7
So we have two choices:
A. Dumb down FW4s motor driver
B. Adjust the scripts to be more organically.
We will probably land with option B since that opens up more options and is not a patch to another problem: the scripts themself. We plan to add a script smoothing algorithm that can be set through the API so you can set your "desired organic profile". In the future, scripts will most likely be captured 1:1 with the motion in the video, which will be organic data. Without an intelligent motor driver, that motion will not be replicated as well. -
22 Nov, '24
kineticsSounds great! I would really like for that smoothing setting to be available through the settings app as well, though, just like you have done with stroke length. It usually takes a long time for third party apps (like Stash that I am using) to implement these new API features.
1 -
22 Nov, '24
MarooningSpeaking as a user:
14
Is it possible to rely on a tag within funscripts that says "I'm made for v4!”?
That way, if a creator is making a funscript with v4’s detailed motion in mind, they add that tag.
Then when the Handy reads a funscript:
If that tag does not exist, use the v3 smooth motion by default.
If that tag exists, use the extra detail available in v4.
That way backwards compatibility is maintained, and creators can work with v4’s improved motion going forwards.
From there, the suggestion of motion profiles. It sounds very cool. But starting every session by needing to figure out the “correct” motion setting for each script by digging around to find when it was made or which motion profile the creator recommends, then plugging that setting into the fiddly app, sounds like a miserable start.
If a creator can tag a script to say “this is a v4 script, use this motion profile” that’s a win.
If a user can then say “I want to try this motion instead” that’s a cherry. -
07 Dec, '24
NunyaI don't see why not just have a setting to choose either the newer or older movement. Then I can just choose which one I prefer.
2
I would love to be able to use FW4, but having to use the newer movement completely pushes me away from FW4 and all of its otherwise amazing benefits. I'd also really rather not just eventually be forced to give up the old movement entirely, since all of our existing scripts are already designed for it. My device would instantly lose a large chunk of its value to me if that were to happen.