Sascha

Ooops, sorry, thats my fault. xDraconian is correct. This 0 values are default inputs if no other input condition is meet. So they should defined as <input>0</input>. I updated my git-repo. Please test and merge into FG if all is fine.

Thats right, because the C172p in next (2020.4) use the new KAP 140 that Josh and i build from scratch. The old one in 2020.3.x is crap. It has never worked as it should. So this bug report relates definitive to the old KAP 140. (Maybe we should ship a new point release of FG with a newer C172p ?)

For some hours we had a discussion on Discord about this problem and Jonathan pointed us to this patch: https://sourceforge.net/p/flightgear/simgear/ci/7ac90850d3b8adc613fb07acaad7b6aaee0844d4/ I reverted the changed manually in the code and compiled a second time. So, i can confirm that this patch breaks the animations. But as i reverted the changes line by line i saw that this patch introduce the 'offset' to the animation and especially this line jump in my eyes: offset = axisSegment->getStart()...

Looks like some effects have problems with transparent objects. In the Citation II every instrument has a glass with the effect 'model-transparent'. Depenting on the view angle, some objects behind the glass (digits and stripes) vanish. In this shot, the view is close to perpendicular to the engine panel and all is visible. http://lepanto.at/download/flightgear/screenshots/fgfs-20211209180718.png In this two shots i turned the view and the digits and/or the stripes vanish. Also one digit on the VNCC...

DHC6 Twin Otter (stable - 2020.3)

DHC6 Twin Otter (trunk - 2020.4)

DHC6 Twin Otter (trunk - 2020.4)

DHC6 Twin Otter (stable - 2020.3)