VARIO not working anymore on 4.5RC4. It was working fine on RC3 about betaflight-configurator

[Giammi]

@haslinghuis GPS is a Flywoo Goku V3 M10 with QMC5883L. BTW never mind, I've flashed it again with full chip erase and now it works. So you can close this. Thank you anyway for your time looking into this.

[haslinghuis]

• Do you have a support ID?
• Try debug DEBUG_ALTITUDE

[Giammi]

@haslinghuis support ID is d9452f24-f4e1-4877-ac3a-cdc7d61da9f6
Attached you can find a log with ALTITUDE logged. It's just a hovering test with some up and downs.
LOG00012.zip

[haslinghuis]

Checked on blackbox.betaflight.com but could not get the ALTITUDE debug data.
In the header it says GYRO_SCALED ?

[Giammi]

@haslinghuis sorry, my bad. I got fooled by the new blackbox interface in the configurator. I selected ALTITUDE in the dropdown list, not in the debug. Now I set it to DEBUG_ALTITUDE. Here you go.
LOG00013.zip

[haslinghuis]

Vario works in blackbox. What symbol is shown in OSD?

ifdef USE_VARIO
static void osdElementNumericalVario(osdElementParms_t *element)
{
    bool haveBaro = false;
    bool haveGps = false;
#ifdef USE_BARO
    haveBaro = sensors(SENSOR_BARO);
#endif // USE_BARO
#ifdef USE_GPS
    haveGps = sensors(SENSOR_GPS) && STATE(GPS_FIX);
#endif // USE_GPS
    if (haveBaro || haveGps) {
        const float verticalSpeed = osdGetMetersToSelectedUnit(getEstimatedVario()) / 100.0f;
        const char directionSymbol = verticalSpeed < 0 ? SYM_ARROW_SMALL_DOWN : SYM_ARROW_SMALL_UP;
        osdPrintFloat(element->buff, directionSymbol, fabsf(verticalSpeed), "", 1, true, osdGetVarioToSelectedUnitSymbol());
    } else {
        // We use this symbol when we don't have a valid measure
        element->buff[0] = SYM_HYPHEN;
        element->buff[1] = '\0';
    }
}
#endif // USE_VARIO

[Giammi]

@haslinghuis symbol is just the unit of measure m/s with 0.0 before it. I don't see anything wrong with respect to the past. To me looks like it's well represented in OSD, just the value is stuck to 0.0.

[haslinghuis]

What GPS / MAG unit is used? Try disabling MAG (might have to remove from firmware build for testing)