I have several wishlists regarding airport standards and QA, specifically with VASI/PAPI and runway lighting, but also runway markings. From what I gather, the lighting database they used to populate the generated, non-bespoke airports is 15+ years old - I’m guessing a holdover database imported from FSX. Either way, it in no way is accurate to the lighting currently indicated in the NASR database (US), nor those depicted on charts. Unless, that is, the lighting has not changed since then, which is a very hit and miss prospect.
But one giant tell is that in the time since the database they use(d) was collected, most US airports have switched from VASI to PAPI as the primary VGSI. Like, completely flipped the ratio, and still increasing in favor of PAPI. Yet, in the sim I still see VASI all over, inappropriately (not to mention positionally misplaced). This is just a timestamp that provides evidence of how low a priority airport lighting is.
What is not clear is whether the existing lighting “database” is currently readable at a higher level other than simply when it renders the airport. I believe the airport (lighting, etc) data reside in each individual airport’s bgl file and, correct me if I’m wrong, are asynchronous from those read by the EFB. So again, it’s unclear if those can be read by an application en masse, in real time. And I say real time, because third-party scenery exists, as does the scenery edited in the World Hub (which is overdue for a return). When things change/are corrected, it has to be read each time anew - not simply pushed to a static database and updated at whatever asynchronous pace.
But back to my main point, the stock airport QA standards are immersion-breaking in many regards; the lighting will actually make you fly incorrectly - it is that “sim-hazardous.” But also game-breaking with respect to your point about career mode, which is supposed to be the pinnacle mode introduced in MSFS 2024.
So I’m with you, but I’m also saying this needs to be a larger discussion and should involve a task force of SMEs that understand not only the specs, but the regional variation, who can lift the problem. An SDK with proper tools and improved UI, a bi-directionally read/write database/API that will allow interaction (like pilot or ATC-control) would go a long way. What I don’t want to see is this work pawned off to a company that sells it back to us. This should be included at the base-level of the sim - it is that important to aviation and I’m bummed it’s hurting the experience, but I’m glad people are starting to realize it.