We have tried to squeeze out some more stroke length on FW4, but it seems like it overshoots too much in the end. We have done some updates that will come out in FW4.0.12
Under consideration. Will not happen before we have full adaptation on FW4 and API v1 and FW2 are depricated (next year).
I appreciate you trying to fix this but, having it show up under that name would be even worse. Put it into google and you’ll see why.
Changed it to “Ohd - Norge”
I’m having a problem with FW 4.0.11 and 4.0.10 as well.
I’m using the handy in legacy bluetooth mode to connect to intiface central, and when I play a funscript through scriptplayer and pause on an upward/downward stroke it just keeps moving up/down until it reaches the top or the bottom of the handy.
What happens?
Stroker continues traveling after pausing a funscript until it reaches either the very top or very bottom, depending on which direction it was traveling during the pause.
What should have happened?
Stroker stops in place when paused.
Steps to reproduce
Put handy in legacy bluetooth mode.
Connect the handy to intiface central.
Connect to buttplug/intiface in scriptplayer.
Set mpc-hc to video player in scriptplayer.
Play script in mpc-hc and pause while the device is stroking.
I have found that the new firmware struggles to follow faster movements, or more accurately simply skips them.
Even on their own sync test, when it goes to the top, and has a little downwards indent and then up, simply gets skipped for one big top.
So i have downgraded to firmware 3 again.
Thanks for the detailed feedback. We are working on a fix in 4.0.12, and I hope that the bugs do not discourage you from continuing to help us in the beta testing.
I just found this, so should I WAIT for the potential fix to update, or should I yolo and just do it now?
I would wait, FW4 just doesn’t have nearly the same level of performance at the moment.
You can try the latest update. It should address many of the described issues. FW4.0.12. NB! It is only available with the STAGING FW feature flag at the moment.
The latest update works great! Fixed all the problems from the first release. Thank you!
you walk around it still doesn’t detect in Bluetooth and there is no update unless you have a VIP update??
Okay… two questions:
- Why would you walk around with your handy?
- What the heck is a VIP update?
My handy stays clamped to a desk during use and updates are free. Got mine this week from the new handyfeeling site and it worked like a charm. They changed how the handy connects and you can change the settings if you want. Try the new website
sorry for my little English it’s just that the bluetooth does not work with intiface and funplayer by vip I meant that you may have a beta update
What happened? I was hoping you would let the Handy stroke all the way to the end. It stops about half an inch.
I’ve gotten around to testing out 4.0.12. While performance is better than the earlier FW4 variants, it’s still inferior to FW3 in terms of speed and accuracy.
The device also still sounds odd when running FW4, and stroke length, especially on the downstroke, just isn’t there.
However, by every other metric it’s a vast improvement. Connection to players and the downloading of scripts are exponentially faster, to the point of being nearly seamless in FW4.
Of particular note is the uptick in reliability. I’ve found connecting to Wi-Fi under FW3 to be wildly variable; the device can rarely hold a connection for an entire session, eventually timing out or failing to connect in the first place. FW4 exhibits none of these issues.
I’m really hoping FW4 continues to evolve, though at this point a FunSR1 is looking more and more appealing.
I agree 100% with this evaluation. The connection to wifi and script loading, jumping around within a script are all VASTLY improved with FW4. It makes you realize how much you had to deal with disconnections, script upload fails and waiting around at critical junctures, and then with FW4 I had NONE of that. The script uplaods are wonderful and it makes jumping around in videos almost seamless.
However, the smoothing (and perhaps speed limits?) and overall feel of the device breaks the immersion for me a lot in scripts that I know used to feel fantastic before in fw3.
At this point, I go back and forth between the 2 firmware versions, and all I want for christmas is the reliability of script loading of fw4 and the movement response of fw3.
I’m hoping that can get resolved because the reliability and API potential is a huge step forward. Please let us know if there’s anything we can do to provide more specific feedback, but I imagine a slow-motion video of two handys next to each other playing an aggressive script would show significant differences between the two firmware version.
FW4 also handles long scripts significantly better than FW3, which chokes up or times out on a lot of long (30m+) ones. Like you say, FW4 really highlights just how unreliable FW3’s Wi-Fi mode can be.
I’d like to hear more about their goals when it comes to FW4 and performance, as the primary concern (reading between the lines a bit) seems to be protecting the device. This seems like an odd thing to focus in on 5 years after release, which hopefully does not indicate they’ll be doing some “value engineering” on the mechanism in the future.
Thank you for your feedback! We have tried to make the device motion more “true” to the script, but it might be that the result makes the sensation feel more robotic. We will continue to finetune before a full release (all Handy users are recommended to update).
How to give more feedback: If there are some spesific videos or even better, a spesific part of a script that feels wrong vs FW3, please let us know and we can take a deeper dive into it.