I am trying to move a simple shape (rectangle) along in the Y-axis by turning the wrist. The accelerometerRawY() function (ypos:225+((accelerometerRawY())*5))usually works well for some time but as time progresses it looks like the buffer of the app fills up and the vertical movement gets more & more jerky with a lot of lag. I also tried to limit the values with ypos: (clamp((240-((accelerometerRawY())*18)), 140, 252)) but to no avail.
Is this something that is just a thing of the facer app or are there any workarounds?
Any insights greatly appreciated…
1 Like
Keep it simple. Obviously posx; is not in your formula . I dont use Clamp. The whole thing is a bit jerky. Good Idea to try a Re Boot. .
You colud try use the Accel Angle as a Condition then scroll your Image at the speed of your chosing.
I am busy Today.
Someone else might join in and Help.
never managed to make it work well in Facer, although I have had it work flawlessly and very smoothly in “other places”. Seems Facer just cant figure it out and I junked it ages ago because it’s clunky and has even locked up my watch due to the lag.
1 Like
I think resulys from the Accelerometer vary on different watches. As No Pro I found it very usefull. Truthfully I mostly used it as a trigger to switch stuff.
I was going to say to @timeasart. Yo have to make a little test. Just put
(accelerometerRaw())
In a Text Box and send it to your watch. You will note thst half the repors are Negative. I can not test the cide you have posted. But you need to go a long waycwith you redearch befor you start using clamp to try sort stuff out.
Hello @russellcresser @kirium0212 Thanks for the replies. Yes I think this is just a facer app issue - on Watch Face Studio everything is very smooth.
Another question that came up: I would like to use accelerometerRawY() for opacity and run a conditional for a shape: if accelerometerRawY()>5 and accelerometerRawY()<15 then hide/show.
Any insights greatly appreciated…
1 Like
I just used it to try to create highlights and shadows with gradients for added realism. I’m sure there is way more functionality to it for other purposes.
1 Like
Let me answer my own question here: The statement with conditionals would be:
$((accelerometerRawY())*9)>30&&((accelerometerRawY())*9)<50?100:0$
But again - the facer output is too unreliable to make good use of it…
1 Like
Yeah that looks good. All these sensors will jitter arround the selected angle number. To make motors accelerate and decelerate smoothly to the position data they us a complex algorithm called PID. That is well beyond what can be achieved on a watch Face.