Been looking at a lot of older scripts, and a lot have speeds of 1000+ even 1500+ and I was wondering if there is some tools that can be used to auto-adjust the script to work with the handy and reduce the max speeds down to 600 for Handy.
I know that I can “cap” the speed at 600, but it seems like a lot of effort was put into creating the scripts and chopping everything above 600 to a flat 600 obviously won’t do anything useful. Is there some way to auto-calculate a reduced value for all movements?
The Handy can load and will run faster scripts than 600, it will just not go faster than that.
In OpenFunscripter there is a Range extender (under special functions) that can reduce the range of everything selected, if you want to reduce the speed of the entire script or a part of it.
Thanks, I saw the limiter function on funscript.io but that was not what I was after.
Maybe OFS will be the right tool, if it can reduce everything by 40% in a range.
Maybe it’s just a personal preference, but when I play a script created for Handy (capped at 600 from the scripter) it feels much better than when I play something that goes upto 1800/s and that section doesn’t feel “realistic” on the Handy, it’s just basically turns a scene into “maximum speed” for the entire scene.
So I’m trying to find a way to (automatically) adjust the older (Faster) scripts down to something that feels more realistic on the handy, and I figured if I take everything that’s scripted in a scene (say from 400-1800 for 3 mins) and tell a tool to reduce it by 50% (200-900) it might get closer to a realistic experience?
Maybe I’m just very naive but it seems to be a waste to let older (faster) scripts go unused because they are not designed for a handy.
For the Handy, MFP and @Yoooi working on it will not do any good. This will be a big argument against the Handy and for the SSR1 or any T-Code device when he is successfully done. Fastest way for you without damaging the script is the @quickfix macros.