On the Map, at certain zoom levels, the “small airports” are being drawn as if pulled in to the map by magnets - there are not 70 small airports in a 7 mile range of Haneda… Easier to just look at the screenshot.
Edit - these all appear to be Helipads, which I’m pretty sure should not be classified as Small Airports, and should not be shown on the G5000.
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Almost every flight, I’m just noticing it recurring - the first few times I noticed it, I was focussed on other issues, not I’m seeing it recur.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
I loaded in to a gate at RJTT (live weather, live traffic (set to low)
I zoomed the map close to RJTT
I noticed the small airports that are really not in the selected range being drawn and basically covering the map.
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: keyboard, mouse, controller
[PC Only] Are you using Developer Mode or have you made any changes to it?
No
[PC Only] What GPU (Graphics Card) do you use?
RTX 5090
[PC Only] What other relevant PC specs can you share?
9800X3D
This is not a bug; in the sim, there really are that many airports in that range. If you go to the world map they will be there too, in the same places.
Sorry, Matt, but the “Airports” shown are Helicopter pads…!
Is the G5000 in the Longitude supposed to show Heliports? Or just “Small Airports?”
If it is not supposed to show Helicopter pads, then this thread should be reclassified as a Bug. Thanks. See screen shots of the he G5000 MFD, World Map, and Planner. You can see RJBAN (Tower of Wind, in Tokyo Bay) as an example
Yes it appears to be the same issue - but extended to the Garmin G5000 (and I can only assume G3000, and G1000). I’m pretty sure they should not be showing Helipads as airports. I think some real world units can show helipads (depending on the database) but are separate from small airports.
Sorry, I should have been more clear; yes, at this time in the sim Helipads are actually airports with a single helipad and no runways. We now have some ability in 2024 to filter these types of airports out, but doing so will also break backwards compatibility with existing aircraft that need these displayed (like for example, the Joby).
As such, we will need to add an option to the avionics that developers can opt into that would describe the base airport filtering parameters. Presently it is operating as designed, so I would classify this as a feature request (although of course a sensible one).
If so, I have almost no hope that they will ever fix it. I guess I’ll just try to set the “Small Airports” to the the smallest range and reduce Map detail. A shame. Thanks for replying.
I think they should be separated by avionics system, as they won’t all necessarily have the same solution (the map code is not identical across all Garmins, there are differences).
Thank you both for responding - from a purely user perspective, this sounds like Asobo should (or should have…) put identifiers for “Helipads” vs “Airports” that allow basic filtering (and therefore not force an artificial filter to be “MacGuyvered” into the avionics.
From the user perspective, it appears to be the same issue affecting the whole Garmin suite (helipads being shown as airports)… If Asobo calls that “by design”, I’d have some choice words. But again, I’m not a programmer, just a user!
If all runways have a known length, it becomes so easy to separate everything.
In the G5000 I don’t know if it’s possible, but in the GNS530/430 we can choose the minimum runway length we want to show as a nearby airport, in MSFS2024 it’s possible to access these settings but they don’t actually do anything.
As I mentioned, there is now filtering available in 2024. But, the characterization of the proposed airplane level filter options as either artificial or MacGuyvered is not really at all earned here, and I’ll explain why.
In real life, these units don’t have any pilot accessible filter for this kind of data (or else you’d see it already in the map menu). Either they ship with a database that includes heliports, or they don’t, and that depends on the aircraft they’re installed in. In the simulator, however, there’s just one set of navdata, there isn’t separate navdata per avionics install.
There are absolutely GNS units that ship with helipad data in their installs, as they are installed in helicopters. There are also units that ship without that data. Similar for the G1000 units, and the G3000/5000 units. So, just going into the code for these avionics systems and adding filtering at the core level would be an incorrect move, and break some correct usages of these systems in rotorcraft.
Therefore, the proposed solution that enables an option at the aircraft level for aircraft developers to opt into to either show this data or not is not at all a hack, but instead properly reflects the real-world installation where these databases either have this data or not in them and allows the developer to specify that.
