"20.37 [ALRT]:autopilot DigitalFilter: unknown config node: absolute"
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
17.81 [ALRT]:autopilot DigitalFilter: unknown config node: value
The first error seems to come from Aircraft/Generic/g-forces.xml. Introduced in https://sourceforge.net/p/flightgear/fgdata/ci/38ec3d2be86cbdb83498eb4e0659f4b253e8b624/
I can't trace where the second lot seem to come from unfortunately, but it was while running the C172p.
Both issues were fixed in April 2023 per [852b6e] and [b1f87a] respectively. Unfortunately the second issue (also tracked in [#2801]) was then re-introduced by a c172p update ([536cd5]), when FGData was overwritten by the version from https://github.com/c172p-team/c172p.
@wlbragg, can you make sure the fix from [b1f87a] ends up in the c172p Github?
Reminder for @scttgs0 and all, c172p bugs should be fixed upstream in the Github repo ;-)
Related
Tickets:
#2801Commit: [852b6e]
Commit: [536cd5]
Commit: [b1f87a]
@gijs thank for looking at this.
Yes,I will take a look at it.
Pull request created: https://github.com/c172p-team/c172p/pull/1488
This has now been fixed upstream in the c172p repository. Closing this bug now, as it will be fixed in fgdata with the next sync.