Compass trouble in Virb Edit

Former Member
Former Member
The compass I use in Virb Edit uses values (from the GPX file) between 1 and 360, where 1 and 360=north, 90=east, 180=south, 270=west.
If a device is pointing east, and you turn it counter clockwise 180 degrees slowly, then the values go from 90 down to 0, wrap over to 360 and continue down to 270 degrees.
But the compass doesn't rotate correctly when it jumps from 1 to 359, then it instead rotates clockwise pretty fast from the value 1 to 359, instead of just rotating counter clockwise as expected.
That can be seen 49 seconds into this video: https://www.youtube.com/watch?v=ZKuckqtSEWk
This also happens if I use the default compass. What am I doing wrong here? Or is this a bug in Virb?
  • Former Member
    0 Former Member over 10 years ago
    Yes, this looks like a bug. We thought we had this working correctly, but it looks like we don't. I'll create a case and hopefully get this fixed soon.

    Nice work on the custom gauges! How did you get "distance to drone" and "battery" in there?
  • Former Member
    0 Former Member over 10 years ago
    How did you get "distance to drone" and "battery" in there?

    I was wondering that.
  • Former Member
    0 Former Member over 10 years ago
    Nice work on the custom gauges! How did you get "distance to drone" and "battery" in there?


    Hi guys

    Glad to hear that you can fix this issue.

    I'm actually the one having made the tool for converting the logfile from the drone to a gpx file.

    Distance in meters is reported as Temperature in gpx file
    Battery level of drone is reported as Cadance (0-100) in gpx file
    Orientation of drone is reported as Power (0-360) in gpx file
  • Former Member
    0 Former Member over 10 years ago
    FALAGAR: thanks for the very quick reply and the fact that you'll fix it. How soon would this be done?
    On a separate note, it is Kenth who made these custom gauges; see his page for details.
  • Former Member
    0 Former Member over 10 years ago
    I have also set "wrapValue" : true under manipulations in the veg file, which I guess should be for exactly this purpose, and it does not solve anything

    Falagar, do you have any rough idea of time estimate for fixing this?

    Thanks
  • Former Member
    0 Former Member over 10 years ago
    I am not sure. To be honest, this is not a high priority issue, unfortunately. I put it on the tentative schedule for the next release, but it might still fall off the wagon.
  • Former Member
    0 Former Member over 10 years ago
    I am not sure. To be honest, this is not a high priority issue, unfortunately. I put it on the tentative schedule for the next release, but it might still fall off the wagon.


    That was a shame.

    It seems like it has been working earlier, I have seen youtube videos where it wraps from 0 to 360 correctly.

    Will be be possible to download an older version of Virb where it works?

    Thanks in advance
  • Former Member
    0 Former Member over 10 years ago
    Hi again

    I tried to uninstall version 2.9.2 and instead install version 2.6.2 instead.

    There the compass worked, it wrapped fine around zero, but in that version all my custom made gauges from version 2.9.2 didn't work at all, and it seems like it was not possible to create custom gauges in that version.
  • Former Member
    0 Former Member over 10 years ago
    Hi again

    I tried to uninstall version 2.9.2 and instead install version 2.6.2 instead.

    There the compass worked, it wrapped fine around zero, but in that version all my custom made gauges from version 2.9.2 didn't work at all, and it seems like it was not possible to create custom gauges in that version.


    In the version history I can see that custom gauge was introduced in version 2.8, but I can't find that version anywhere, is it possible to download that version from somewhere to see if the compass gauge wraps correctly from 0 to 360
  • Former Member
    0 Former Member over 10 years ago
    http://gawisp.com/perry/virb/ has all the versions.

    Yes, this behavior broke somewhere along the way. We'll try to fix, I just didn't want to promise anything because I know how long the list of bugs and features is we have scheduled for the next version.