Ascent/Descent datafields are broken in 8.30 (only when verticalspeed is m/s)

[Domi93CH]

if a data field with the content increase or decrease (regardless of whether average, current or maximum)
is configured in m/s. If it says 0L or 0R, it's probably a problem with this new Balistik app. But if you select m/min, the display is correct again.
You can ignore the connect IQ data field above and I was able to get it to work again by selecting new.
It also said windage, so I think this is a mistake in the new Balistikapp

Spoiler

1100[1].bmp

1056[1].bmp

[Backstreetbob]

Does the new firmware still over read the total ascent and descent values like older firmware?