Hi, good to know. The problem is, I’m on console But if this comes on console, I’d like to thank you in advance for the information.
The hand crafted EDDK still isn’t fixed yet..Still showing the wrong runway numbers …the default version has the correct numbers but a terminal building is missing while showing just jetways ..due to the wrong runway numbers it makes flying IFR there impossible as no procedures are shown ..(using a PS5 so its the LIDO nav data)
Identifier - FIMP
Name - Sir Seewoosagur Ramgoolam International Airport
Category - Runway
Description - Both left and right PAPI systems are present for the same runway end, resulting in duplicate PAPIs. The PAPI systems also provide differing indications and are not coincident as expected from real-world airport data.
There’s quite a bit wrong there. The numbers shouldn’t be inside the threshold markings, the threshold markings go too wide (outside the edge stripes), the aim points are fixed distance instead of being independent, s/b beyond the 1000’ marks. The PAPI on the left should be harmonized with the aforementioned aimpoint, and there should be no PAPI on the right side.
But it’s weird in that it has the 3-per-side 500’ markers (which is correct). That’s usually not a thing with stock airports. It’s almost as if this was bespoke or maybe third party?
If it’s not autogen it may show up in a search for the ICAO in VFS.
Yep, I really hope that we’ll soon get the possibility to fix all these issues…
I looked at the default FIMP and see what is shown in your image. Comparing this to both Google and Bing maps causes me to wonder how MSFS 2024 could generate such incorrect images.
Identifier - UBBB
Name – Heydar Aliyev
Category – Grounds and Facilities
Description – There are no ground services at this airport in SU6 v1.8.14.0
Selecting:
Gives:
(FYI: Also, jetways are broken, as reported in this bug topic post)
Identifier - LIRQ
Name - Florence Airport
Category - Runway
Description - PAPI systems are missing in the simulator compared to published airport information.
Identifier - VVPQ
Name - Phu Quoc International Airport
Category - Grounds and Facilities
Description - PAPI systems are missing. Multiple taxiways are missing from the airport layout despite being visible on aerial imagery. Taxiway edge markings are incorrectly rendered as runway holding position markings. Additionally, several jetways and stands are missing compared to the real-world airport layout.
tl;dr LYBE has missing parking places, those existing are aligned wrong, taxiways aren’t labelled, and that’s ignoring the issue of a whole runway being missing
I may have gotten a little tilted and crafted the following rant('s body) on the 6th anniversary, ended up not posting because other examples weren’t as drastic but I still want to use all that as feedback:
Welcome to Belgrade, a major European capital served by an international airport hosting around 160 flights a day - so not some minor nitpick. This is a comparison of how it should be, as shown by the LIDO chart available to us, and how it is via LNM’s scenery view:
Not good. Ignoring the obvious problem of a whole missing runway, the number of parking spots is simply missing: 3/10 on Apron A (and 6/12 on GA apron), 3/10 on Apron B and 8/14 on Apron C - and that’s excluding the smaller “suffix A” ones - and the entire apron E. It did make up a whole mess at the maintenance ramp from the planes positioned there, but that’s forgiveable.
To make the in-game parking spots more prominent, I’ve added them on top as the cyan lines, which showcases a more common issue: the angling of the parking positions is all over the place, when in reality they face towards the terminal at a right angle without fail. Look at the “C9” or “C7”, at “A3” or “A8”, or the whole B apron - which used to be accurate, but was redone to the current scheme five years ago.
And no, they don’t match the ground imagery at all:
The stand names are in quotation marks, because obviously they are not real-life accurate, even though with current AI tools you’d think this wouldn’t be such an issue even if the numbers couldn’t be read from the imagery. The equivalent numbers in FS24 for the four mentioned above are: “stand 46”, “stand 47”, “gate 0” and “gate 6”.
This extends to taxiways, or in this airport lack thereof: I had to get in-game to check, and sure enough the map in LNM is accurate and the sole named taxiway is A, and even it has gaps where it stops being named.
And this issue is not just a problem with sceneries, it extends to other functionalities of the sim. To return to the hypothetical I presented about made-up navaids: imagine using the in-game ATC (I know), or any solution using the in-game scenery database, and receiving this kind of instruction: “taxi through Alpha to gate 6”. You look at charts and are utterly confused: how far down Alpha? Which gate 6, A6 or C6?
Or you use a third-party multiplayer server and the in-game map, and are told “vacate through Romeo 4, hold short runway 12R/30L, after vacating taxi through Delta 4 and Hotel to stand Bravo 8”. You look at the in-game map and NONE of these are present.
And how different this would be compared to the esteemed competition’s scenery, by no means perfectly up-to-date either:
ISSUE DESCRIPTION
Description of the issue:
At Málaga–Costa del Sol Airport (LEMG), the parking stand lighting is missing during nighttime operations.
In addition, the green taxiway centerline lights appear to be missing in several areas.
Considering that LEMG is a major international airport, the lack of realistic lighting around the parking stands and along the taxiways is particularly noticeable at night and has a significant impact on immersion.
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
N/A – PlayStation 5.
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Observed during a nighttime flight to LEMG. The issue appears consistently when operating at the airport at night.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
- Start Microsoft Flight Simulator 2024 on PlayStation 5.
- Use the current public build 1.8.14.0 (Sim Update 6).
- Set up a flight to LEMG – Málaga–Costa del Sol Airport.
- Arrive at LEMG during nighttime.
- Land and taxi to an aircraft parking stand.
- Observe the lighting around the parking stand and along the taxiways.
- The parking stand area is very dark and the green taxiway centerline lights are missing in several areas.
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using, if relevant:
PlayStation 5 DualSense controller.
[PC Only] Are you using Developer Mode or have you made any changes to it?
N/A – PlayStation 5.
[PC, MSFS 2020 Only] Are you using DX11 or DX12?
N/A – MSFS 2024 / PlayStation 5.
[PC Only] What GPU (Graphics Card) do you use?
N/A – PlayStation 5.
[PC Only] What other relevant PC specs can you share?
N/A – PlayStation 5.
MEDIA
Please add screenshots or video showing the missing/insufficient parking stand lighting and the missing green taxiway centerline lights at LEMG during nighttime operations.
[END OF FIRST USER REPORT]
Identifier -LFPO
Name - ORLY Airport
Category - parking slots, aircraft parking directions wrong.
Description - Some parking slots like C7, C8, C12, C13, and probably on other places, are wrong, I saw B737 parked parallel to the terminal, and as I was approaching gate C7, the visual assistance showed the way to the slot as in the screen below. I restarted from the same gate and the plane was effectively with the tail heading to the terminal. Stock scenery, no GSX as they have deactivated the jetways for MSFS 2024 yet.
Title: [AIRPORT BUG] SANR - Termas de Rio Hondo: Missing runway markings, lighting (ALS/PAPI), and misaligned VOR approach
Category: Bug Reports > Scenery & Airports
Platform: Xbox (Series X/S)
Sim Version: MSFS 2024
Detailed Description:
The default scenery for SANR (Termas de Río Hondo Airport, Argentina) lacks basic airport environment features and contains navigation discrepancies, especially when compared to nearby regional hubs like SANE.
Key Issues Identified:
- Runway Markings: The runway surface has no painted markings, thresholds, or centerline details.
- Lighting Systems: Complete absence of runway edge lights, Approach Lighting Systems (ALS), and PAPI/VASI indicators.
- Navigation / VOR Approach: The VOR procedure is misaligned with the actual physical runway heading/centerline, leading to incorrect guidance during instrument approaches.
Expected Result:
SANR should feature proper runway paint textures, functional PAPI and approach lights, and an accurately aligned VOR approach procedure.
Steps to Reproduce:
- Spawn at SANR (Termas de Río Hondo).
- Set time to night/dusk to verify missing lighting systems (PAPI / ALS).
- Inspect runway surface texture to observe missing paint markings.
- Fly the published VOR approach to observe the lateral track misalignment relative to the runway centerline.
Raw Screenshots:
You’re right about the lighting and markings, but I’m not sure about the VOR, though.
The VOR is offset to the side of the runway in real life, so it’s not going to be in perfect alignment. It’s not easy to discern from the approach chart itself, but the last mile or so from the threshold is a visual segment that requires a slight turn off the VOR inbound course. This isn’t unusual for VOR approaches.
It’s kind of hard to tell what’s going on from the picture of the ND because there’s a lot of clanker stuff obscuring it.