Controller axes get sampled according to the position of a particular pot. The problem is that quite often it happens to rest in between two values (i.e. Between 244 and 255) so the computer "jitters" between them. You van sometimes see this in the calibration software.
Of course it can be filtered out quite easily by the devs by simply ignoring changes of less than 1 or two points I'd imagine but this could be the "spiking" you guys are talking about.
Tbh I've left it off from the beginning as the last thing I need is further buggy features to distract from having some fun with my limited time but the feature is intriguing, at least as a means of stemming the script-whores online, if they get it sorted out.
|