Tried the 4.0.12 for the beatbox and the keyboard controls for adjusting strokes and offset. Thanks again for so quick implementation @handyAlexander.
Found 1-2 minor bugs there though:
When setting offset by keyboard you can’t get back to 0. My step is 5 and it just jumps from +5 to -5 and back.
Kinda nitpicking here, but controls can be mapped only to alphanumerical keys. While I understand you can’t really allow users to map to special keys with either browser or system-wide function, I don’t see why e.g. “-” or “+” can’t be used.
Thanks. Would you mind adding the suggestions to our new “suggestions” tool? https://suggestions.handyfeeling.com/ . With this tool it will be easier us to sort the incoming requests.
Tried FW4 again and I think it moves better now. But as you wrote before the movement is more mechanical now compared to FW3, less smooth. Is this by design or do you plan to correct it?
The motion in FW4 is more “correct” compared to FW3. I’m not sure it would be wise to introduce smoothing on the firmware side. It might be better to focus on refining the scripts themselves, as most of them currently rely on mechanical movements with only top and bottom points defined.
Vitor helped you out by providing an initial suggestion as a starting point, so hopefully, future suggestions will follow the same “template”. Feel free to add more suggestions here:-)
Ok. I definitely had the built-in smoothing in mind when spending tons of hours making scripts by hand. I think it does save a lot of time as it feels good, human movement is almost always smooth and don’t have to spend a lot of time putting in tons of midpoints in my scripts.
I guess it could be possible to for example develop a smoothing OFS plugin to run all old scripts through but i would definitely prefer if there was a smoothing setting to have it behave like before.
I’ve been trying to create a user so I can create an access token for the v3 API, but I don’t get any emails.
Is this a manual process or should I get an email automatically?
Update:
Got the invite-links with several hours of delay in my spam-folder.
Unfortunately they were all expired. Now that I’ve whitelisted the sender address, the mails arrived instantly and the activation link worked
We can add a smoothing option when using the API. If you like that idea or have another idea, do you mind adding it here https://suggestions.handyfeeling.com ?
As a new user, I havn’t really compared v4 to v3, but logically, immersion seems to be a key aspect here. Shifting from something smooth to something more robotic feels questionable—especially if it impacts all the scripts people have created and collected so far. Just my two cents!
I took a few minutes in Photoshop and here is what I envision. The suggestions site doesn’t seem to support image embedding. Beyond what you see in the screenshot with user created presets, the other important part would be to be able to drag and drop the order of any of the presets. Then, on the remote control page, you can have the same presets, and once again the ability to organize them. Might also be good to have a few example canned presets that you can use or delete if desired to give users the idea of how it works.
As ridiculous as this may sound, I think v4 firmware and the new API need a way to request “classic” smoothing.
While the new motion may be more correct, there are literally THOUSANDS of scripts made for FW3 and lower. It has become the de facto standard to the point that non-handy devices emulate this smoothing behavior, or have user requests to do so when they don’t.
The community has grown a lot, and single axis funscripts are built on pre-FW4 motion characteristics.
Changing this without a way to request the old method is akin to disregarding backwards compatibility. We can still run ancient x86 code on modern machines, with a few shims. A pre-FW4 API call would be that shim.
Heresphere and other apps could, in theory, add a toggle right alongside stroke length modifiers and the like. Or maybe scripts could make it known in some kind of header data, although then we’re back to potentially breaking backwards compatibility.
I do not disagree, can be a boolean value that or something more advanced when using HSSP mode in API v3. Do you mind adding it as a suggestion? https://suggestions.handyfeeling.com
Does FW4 have the same limitations as FW3 when it comes to min speed, max speed and how many points it can process @handyAlexander ? Would be good to know to start tweaking existing scripts to feel better with FW4 movement.
Min and max speed limitations are the same on paper, but FW4 is better at getting to the correct speed faster. The result is that on fast strokes the device moves around 10-20% faster than with FW4. The same goes in the other end when you go from a fast speed to a slow one, FW4 will react faster and move slower than with FW3.
When it comes to point frequency, FW4 should be able to handle process more points, since the points are in RAM (fast) and not FLASH (slow).
I approved the comment you made on our suggestion board.