I believe I have found a possible issue with the Vorze Piston implementation in Intiface Central.
Environment
-
Intiface Central: 3.1.0+42
-
Device Config Version: 5.3
-
OS: Windows
-
Connection: Bluetooth
-
Device: Vorze A10 Piston SA+
-
Hardware Name: Vorze Piston
-
Protocol: Vorze SA
Problem
The device does not use its full physical stroke when controlled through Intiface Central.
Even when sending the actuator to 0% and 100% using the Device Test slider inside Intiface Central, the piston only moves approximately 50% of its available stroke.
What I tested
-
The same device reaches full stroke when controlled with the other application and standalone.
-
My funscript uses the full 0–100 position range.
-
OpenFunscripter preview also shows the expected full-range movement.
-
ScriptPlayer settings (Range, Filter Range, Speed Multiplier, etc.) have been checked and do not affect the issue.
-
Since the problem also occurs in Intiface Central’s built-in Device Test, it does not appear to be related to ScriptPlayer or the funscript itself.
Expected behavior
Moving the Linear Position slider from 0% to 100% in Intiface Central should move the Vorze Piston SA+ through its full physical stroke.
Actual behavior
The device only travels roughly half of its physical stroke, even when commanded to move from 0% to 100%.
Is this a known limitation of the Vorze SA protocol implementation, or could this be a bug in the current device configuration or protocol implementation?
If there are any debug logs or additional information I can provide, I would be happy to help.