Companion refresh rate looks lok, jerky movement

[wallaguest1]

hi, in the companion software, the servo movement looks way more jerky than in eepe
when using eepe, the bar move so smooth,
but with companion, since its first versions, alwas was so jerky at the output representation
i dont know if can be seen clearly in this video but anyone can try it and check it out,
right = eepe
left = companion

do you see how companion when moving looks like it doesnt move so smooth compared to eepe?
like if the refresh rate was way lower on companion,

can this be solved?

https://www.youtube.com/watch?v=NGrXjeJkT04

[Kilrah]

Can't say I see a difference at least with the new 2.2 simu UI.

But if there is one, the reason is relatively obvious below:

[jhsa]

Could it be because eepe is moving faster than companion and therefore the jumps are less noticeable?
But I think in companion jerky movement is not a big problem as you only use it for displaying.
In eepe or eepskye it would be more of a problem because they can actually control the servos on a model, so the signal sent out must me smooth..

João

[wallaguest1]

its not about speed, i put a servo test mode just so i can show both at same time,
i didnt success to put the exact same mix on both, so thats why speed is a bit different,
but when i move by hand the sticks its clearly noticeable too,
live view on the computer screen is very clear to me, screen video recording it makes it less evident, as it doesnt record at high speed frame rate,

i tried on 2.1 and i can still see the difference just by moving the sticks by hand,
at 2.2 is a bit more difficult to see since scrolls are shorter,
probably is not a big deal, but since companion exist, it has been always like that,
and i wonder why that happens?
whats the refresh rate at companion compared to eepe? might this be the reason it looks jerky to my picky eye?

at live it can be clearly seen to me... i dont know a lot about programing, but its clear to me the change was made since the first
companion version, something was touched at eepe that return a more jerky move.

[Kilrah]

Did you even read my post?

[wallaguest1]

Did you even read my post?

yes, so thats the reason? it return a lower frame rate in order to decrease CPU load?

[Kilrah]

We did find at some point that the simulator was running the mixer calculations as fast as possible with no limit and hogging the CPU. That was changed to running I believe every 10ms, which is about as fast as the radio.