However, it has the typical problem (similarly to great airports adjusted for p3dv4), i.e. drop of FPS by cca 10.... (due to full workload of GPU).
As you can see here:
There's no fps hit whatsoever, using KCLT + GSX (BOTH using Dynamic lights), with a default airplane. But of course, if your GPU is already overstressed by the usage of several dynamic lights that comes with a complex airliner or a complex airport not optimized as KCLT, there's not much we can do.
KCLT, thanks to the usage of our software module, is WAY more optimized than any other airport out there that doesn't use our software, because we never display more than 6-7 lights at time, by checking the terminal side closest to your parking and showing only the row of lights on that side.
Airports from other developers that feature dynamic lights but don't use our software modules, don't have this optimization so, they don't have much control over the number of dynamic lights displayed by the scenery, and the fps impact of them is multiplied by the image complexity.
The more objects you have in view, the more the dynamic lights will affect fps so, Scenery Complexity and Autogen will affect them, even if it doesn't seems to. This has been confirmed to us by LM on their developers forum so, in addition to the antialiasing settings, there are other settings that will affect fps with dynamic lights.