Getting tired of being told its on are end when lots of us are having problems.
"Lots of us" are exactly 6 different people that posted here, with 3 of them having the problem solved by removing the ClipMode=Minimum and one not really minding the problem.
If I fly to klas KJFK or other FSTD airports that I have I do not get this.
Every area is different and chances for a conflict with something else depend on the area, the settings and what else you have installed.
One day you guys will find a solution that really works and all of use will say told you so.
Since there's no flickering for 99% of users, there's no solution needed on our side. The only solutions that works are those already explained above: finding a conflict caused by something else, fixing the camera cfg file and keep the scenery setting as suggested.
You said you did all of them but, since the mesh/complexity and the ClipMode=Minimum are easy to test, it can only mean you have a conflict caused by something else that you still haven't found yet.
Of course, I can only speak of KNOWN solutions. It's possible someone might find another solution for a problem caused by something else (like the ClipMode=Minimum) that still doesn't require we have to "fix" anything in the scenery. We would never have the time to test a scenery with any possible add-on out there.
THAT'S what the Trial is made for: to allow you to test the scenery on YOUR system, using YOUR combination of add-ons and settings.