Yesterday I was away the whole afternoon, and since Alessandro ( KORD's author) is on a very short vacation until Friday, he likely locked the thread so people won't assume "I wasn't responding" for the whole day.
Anyway, back on the topic at hand it seems this problem is in fact another simulator bug, and it has been known since 2018, see this post from Aerosoft:
https://forum.aerosoft.com/index.php?/topic/132680-no-dynamic-lighting-at-destination/We never got to encounter it before, simply because ( AGAIN ), when objects the DL effect are attached to are created as Simobjects, the problem doesn't happen, and since we USED to make most of our scenery using dynamically created Simobjects, we weren't affected by this in KCLT or KSDF. And, we couldn't noticed during KORD developement, because we started by doing everything as Simobjects, like we usually did, and converted most of it back to .BGL in the last days, because we wanted to be the scenery to load as smooth as possible and not use Simobjects if wasn't really necessary.
So, again, just like the "floating object" bug, which wouldn't have happened if we relied on Simobjects created by Couatl, we were affected by another bug of the simulator because we decided to be as standard as possible with KORD V2.
Fortunately, there IS a workaround for this, without having to be forced to convert even the general DL into Simobjects, which of course is already up on Live Update now, together with the other problem reported of bumps at the end of the the northern runway.