Aviation G-metrix virtical speed

I just updated to 5.1, and I'm disappointed to see that there is still no vertical speed for aviation. Everything is scaled in ft/second, which is useless. Aviation uses ft/minute. How hard is it to create a gauge scaled in ft/minute? Is it something I can do myself?
  • I'm a flight instructor and use VIRB videos with my students.

    The 5.3.0 addition of vertical speed would be great if...

    1. I was able to export the videos with the gauges. It's broken. AGAIN. Seriously, this is the fifth or sixth update of this software where I've been forced to download a new version only to find the "new" has broken something...usually the export of gauges. Does anyone test this stuff before you make it live???

    2. The vertical speed was instantaneous instead of smoothed. It appears that the algorithm calculates vertical speed over the past X seconds (20? 30?) of data. The display thus lags the video by quite a bit. For example, I filmed some approaches/landings yesterday AM. The student started off level, then descended, and finally landed. After touchdown, the vertical speed display slowly went from -400 fpm back to 0fpm.... over the course of about 30 seconds. When we're on the runway, we have a vertical speed of 0fpm.

    The VIRB has been a great camera and the ability to overlay very helpful... just frustrated with constant software issues.

  • @equinox1234

    Thanks for the update.

    I had a little bit different experience than namerank. I only used the textual overlay, but it seemed to be a fast update to the VS display. It jumps all over the place. Rolling down the runway after landing, it averaged zero FPM, but jumped up and down, plus and minus about 75 FPM.

    Is VS derived from the pressure altimeter, or GPS?

    Also, as noted above, the overlays don't export with the video.

    Another bug to report - every time I try to capture an image from the video, the program crashes completely.

  • @equinox1234

    Both the gauge export, and the image capture now work for me, with 5.3.1. Thank you very much.

    I played around some more with the VS, and when using a gauge as an overlay, it seems smooth and correct to me. With the digital display, it updates very fast, and jumps all over, with what I assume to be GPS position error. Can that be smoothed at all?