Is the issue that the underlying code doesn't expose the real-time coordinates of the various controllers? It's crazy how we can't implement this in a straightforward way. The AnimationPattern or CycleForce works perfectly. Is it because we can push coordinates to the controller and just not get them back directly?
I'm not sure exactly how the api works behind, I just initially redid a pack for the original plugin. Code interacting with electronics is something I never did and most certainly is way beyond my coding skills.
In the case of AnimationPattern and CycleForce, it is pretty easy because you can do the maths in advance.
I assume that, for the "dynamic version" (the zone one) the way it is implemented in VaM is an approximation of the motion. It does not know exactly where it is nor what it's gonna do. Which result in an algorithm trying to emulate and anticipate the next motion with the previous ones. You can heavily notice that if you have extreme speed changes, it takes a few cycles for the toy to actually reach the pace of what you see.
This is something that will always be like that as soon as you use prediction... there is absolutely no information for the code to know that after a few back and forth, the motion will suddenly stop for 2 seconds or go twice as fast / slow.
The only perfect way is to have a system that directly feeds the destination in advance with the exact pace, so yes, a "funscript like" track on Timeline for instance would be flawless : )
You said "won't jump back on... for VAM"... what are you working on in this front instead?
Nothing! I won't make new content / scenes for teledildos. 2069 was the first and the last for the big scenes and content. It is way too much work and way too impredictable in the way I'm making my scenes to actually be enjoyable. I have several scenes that had teledildonics, and Djinn has also some experiments, but I threw them away pretty quickly seeing the results.
That said, I don't say that to discourage people from creating content for this plugin. I think that creating scenes at slow / average speeds and most importantly with a pace that changes over a few seconds should do the trick. But this is not the kind of content I wanna create... and I'm way too demanding on my own work to release something that doesn't work perfectly.
I might do a demo scene to support
@Blazedust and give a few hints to people who want to create content for it... but after that, I'll be waiting for a future (potential) "funscript" solution before considering spending time on teledildos
github.com
