Compass trouble in Virb Edit

I tried downgrading to version 2.8.0.0, which is the first version supporting custom gauges, but unfurtunately this version have same problem with the gauges not wrapping correctly from 0 to 360 degrees.

So unfurtunately it seems like there is no workaround for this, and I just have to wait for this bug to be fixed in the future.

I spend some more time analyzing this problem.

And I realize it's not a problem with the rotation at all, and the "problem" has probably been there in all the versions.

The situation is that the gauge I'm using is not a true compass, it's a cloned compass which actually shows the power.
The reason for that is that the direction of the drone is mapped into the power data field in the gpx file.

I tried just displaying the power value as a gauge showing the value directly instead of a rotating gauge, and I realized that the value here also can't jump directly from a low value to a high value, when trying to change the value from 1 to 200, the gauge will not jump directly from 1 to 200, but it will ad some values in between, so when displaying 1 , the next values will be displaying something like 76, 132 and then finally 200.

I seems like you guys have made some kind of averaging of the value to prevent fast changes in values.

I have tested it, and it is exactly same problem for both power, heartrate and cadence.

I guess this is something you have made on purpose, and in most cases this will not cause any problems for the user.

Are there any workaround for this?

Thanks

I was wondering about the "power abuse" as well. I might know more when we actually try tackle the issue.

What it seemed like to me that even the regular compass gauges were broken.

Hi there

Any news on a solution for this?

Thanks

The problem still exists in version 3.1.0.2 where the values can't jump directly from 0 to 360 without generating a couple of extra steps with values in between these values.

Are there any plans for fixing this?

Thanks in advance

Br
Kenth Jensen