onox

In the future it would be nicer if you could click on the AP screen and then a new Canvas window pops up showing the same KAP-140 AP.

> that might be alright, too... and link it to F11, too If we manage to replicate the AP in a Canvas window I don't have any problems with binding...

> but the autopilot is quite lacking Can you elaborate?

Isn't it then just sufficient to tune the PID controllers? That's what I wanted to do when I wanted to refactor (https://github.com/c172p-team/c172p-detailed/issues/603#issuecomment-164162176) the code and clean it up a bit....

Tuning the PID controllers just requires changing some numbers, it shouldn't require extensive changes, should it?

@it0uchpods How much code are we talking about? Does it reproduce the KAP140 oddities like requiring the pilot to set the HDG bug when switching to NAV for example? Is...

I meant some of the ``'s in `Systems/ground-effects.xml`.

> So we can simply change any of the int's to bool where appropriate? Yes, but many of the XML files for the effects have to be changed. In those...

If we use a JSBSim `` property (in `Systems/c172p-ground-effects`), then we can use/alias that property in `` and in the flight recorder. And we don't need those filters in `Systems/ground-effects.xml`...

Hey @dany93, I noticed on the [FG forums](https://forum.flightgear.org/viewtopic.php?f=4&t=28279&p=329936) you mentioned the P-51D. I've worked on it for a while in my [repostory](https://github.com/onox/p51d).