Ah! I just looked up your profile. I could tell you knew good stuff, but didnât realize the context! Just this morning I watched Lemioneâs YouTube video about the May F35 crash at Eglin. That was all about mistakes in not selecting the correct command mode during the approach, then hitting hard on the main and nose gear, then not understanding the mode the plane would change to, then trying to go around and the plane ignoring his manual inputs.
PIDs! This is a HUGE source of pain to me in the sim, and I started a big discussion over at Avsim on PIDs and the autopilot turn bug Asobo introduced. Discussion of PIDs is on topic in this thread, so we can have at it and most everyone will just tune us out â with a little bit of complaining, probably.
AP TURN ISSUE AND PIDs
So like I said, back in late November, Asobo changed the AP turn behavior (think HDG mode heading change) so that it:
-
Rolled in proportionally according to the amount of heading change â it took a heading change of more than 90 degrees to achieve anything near 25-30 degrees of bank.
-
Never stabilized on a constant bank until time for roll-out. Just another way of saying proportional control was in effect.
-
Proportionally rolled out very, very, very slowly, taking years to go the final 3 degrees or so of heading error, and frequently missing a course / localizer intercept.
SYSTEMS CONTROLLING SYSTEMS â AKA AP CONTROLLING TURNS
Clearly, this was not a problem with the flight model PIDs (or various flight model tables). This had to do with the AP in HDG and NAV mode.
The previous behavior clearly showed that the AP itself was in direct control of the roll in to a max bank, and remaining at that constant bank until time to rollout. The rollout did seem to be PID-based, but only for the last few degrees of heading error. Until then, it seemed to be linear with a constant turn rate. The roll in was a constant acceleration to a max turn rate velocity, which was then held until max bank was achieved. This was the AP system dynamically changing âmodesâ and choosing between systems and various manual and automated inputs and feedback loops.
After they broke that logic, the behavior clearly was PID all the way, with P and D gains set low, and the I nearly non-existent. I think they did this to try to get rid of the pitch âporpoisingâ and roll oscillations. In heading, the Integral drives the final few degrees very slowly, but if they increased it, they would get the bad oscillations in roll upon any minor adverse input.
Note that in the sim, there are two parameters that will filter I and D â called âboundaryâ parameters. For the heading PID, the I boundary is in degrees of heading error, and the D boundary specifies when the Derivative factor starts to take effect (minimum limit). So I is only applied within +/- some degrees of heading error (close to 0 error when P and D go close to 0), and D begins to dampen the oscillations caused by P only above some number of degrees of heading error.
AP PIDs IN THE SYSTEMS.CFG FILE
The AP PID parameters are in the SYSTEMS.CFG file, which is encrypted on all but the base aircraft. Prior to the mid-December patch, the PID parameters had an effect, but after that, the turn behavior is better but the parameters not longer affect anything. The MAX_BANK parameters seem to work now, though, whereas before they didnât.
So now we again have to await an Asobo fix, and hopefully their opening up more control over the way the autopilot behaves.
Your comments about dynamics open up another can of worms. Elevator effectiveness and lift vector should be proportional to speed. Trim doesnât work as it should because the aircraft never seems to reach stability in pitch, roll, or yaw â and all of those axes are way too sensitive at speed. When an aircraft is moving quickly through the air, its inertia and aerodynamic design (wing dihedral, etc.) should act as stabilizing forces. They donât right now.
So there is a lot of work left to do, and right now, we donât have many ways to âroll our ownâ. The controls and interfaces are not yet sufficiently implemented or exposed to do much more than get close.
Itâs still fun to fly and we can live with it for now. It just makes me even more excited to see what Asobo has up its sleeve with each new update!