qDot
@Yoooi0 Ok, so, questions 1 and 3 overlap a bit. If we assume a feature will have no more than 1 actuator/sensor/raw, then we'd use the feature index, because no...
Also cc @blackspherefollower because they're the one with *all* the devices. Any ideas about single versus multiple actuators/sensors per feature?
@blackspherefollower Where did the "OscillateWithRange" discussion happen? I can't find anything on discord history nor here, so I don't remember what the context was. Also, I should say: This isn't...
> Technically the server could just start supporting the new protocol and without it being documented or exposed by clients the downgrade logic should just make this invisible to existing...
Yeah it's supposed to be signed. However although the messages are defined, they're not really used at this point due to #535. There's some upcoming work to fix that, at...
These are getting updated to i32's as part of the new config format work.
Nope that's a buttplug-js bug. We're not encoding position as a 0.0 < x < 1.0 double here.
@mnh86 Ok, taking a look at this again: Are you sending 28 as the position? Because we expect 0.0
@mnh86 Oh I see what the issue is there. You aren't putting a move duration in, and the system isn't throwing when you miss the argument. God I hate js....
Please do not move with linear duration 0. Either things will not work or it will move as fast as possible and in some cases can cause the device to...