Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

I stand corrected. I should have said the autopilot variables in the systems.cfg file. I realise they are not actually PID parameters but general a/p controls, though I'm guessing they rely on the PID values elsewhere.Rob, i don't see any PID values in systems.cfg I've been adjusting the PID values in ai.cfg and i am able to change behavior.

I agree very much with this. I'd like to add that in general all aircraft a/ps are incredibly sensitive in MSFS to where you place the C of G. If it is just a tad too far back (only needs to be a fraction) then I find you get a lot of porpoising, so I tend to err on the side of slightly forward C of G.Well, that makes it a PITA to "tweak" !!
But its only a SIM, so no reason why you cannot introduce a Impulse and see the response, in real time, to what the aircraft does.
The issue then become, you are looking at the combined response cause by both the AP and the planes dynamic and static stability.
So #1 is to measure the Planes Stability to an impulse, with the AP off.
Then, when that is "Good", either fully optimized, or something representing the real aircraft, only then can you start Optimising the AP to match that planes response.
I believe, as a RL private pilot of over 30 years, that for example, the MSFS's C172 is unrealistically Dynamically unstable in Pitch.
So trying to tweak the AP, to compensate for that is just covering up the issue, for a plane that does not even fly correctly with the AP OFF
Unfortunately, so many over on the MSFS Forum, are just complaining about the AP, (the Dolphin effect), without 1st considering that the AP can only do so much to tame an unstable aircraft.
If I allowed it, I would find it highly frustrating, especially having had a background in designing and testing RL Guided Missle Control system.

AMAZING -- so a FUDGE the user can so is to move the CG far forward to reduce the porpoising !!! (until Asobo fixes it)I agree very much with this. I'd like to add that in general all aircraft a/ps are incredibly sensitive in MSFS to where you place the C of G. If it is just a tad too far back (only needs to be a fraction) then I find you get a lot of porpoising, so I tend to err on the side of slightly forward C of G.

To be fair it is not exclusively Asobo's issue. I had very similar experience when developing for FSX and P3d. It is not unreasonable that a slightly aft C of G might promote pitch instability under autopilot. In fact there are quite a few historical upsets in the real world, and a number of bad accidents caused by shifting cargo, over-loading, too much weight in the back of the aircraft and so on. A relatively small imbalance can create a serious situation because only a small value out of kilter produces a strong moment (a bit like a seesaw).AMAZING -- so a FUDGE the user can so is to move the CG far forward to reduce the porpoising !!! (until Asobo fixes it)
The question still remains WHY .. and it seems to be connected to the Dynamic stability and the sensitivity to trim to a stable configuration.
Can't wait to try moving the COG and see if it helps !!! thanks
Will probably be fine after the Christmas Holiday, when my C172 co-pilot & I put on some weight, eating too much.
Not going to make much difference in the Airbus !!

