They have rewritten parts of the SDK documentation already that deal with aspects of the gateway.
Surely a first in the world of flight sim: the manual being ready before release.
This is a reminder that this thread is meant to serve as a bug topic, not a discussion topic. If you are experiencing this issue, please feel free to report your findings using the following template. You may also post any work-arounds if available.
Outside of this, please use an existing or new topic in the appropriate #gd-commsupport sub-category to discuss this bug. All other posts will be removed.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes. Same is true for a significant number of U.S. airports.
Provide extra information to complete the original description of the issue:
As Papi and Vasi lights are an integral part of flying, it is important to get these fixed. Also, Vasi/Papi location data in the U.S. is freely available. I don’t know about Papi and Vasi location in other countries. The issue might extend to other countries, too.
If relevant, provide additional screenshots/video:
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
2 tags are required: One for platform, and one for aircraft.
Are you using Developer Mode or made changes in it?
Have you disabled/removed all your mods and addons? 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 Community Support section.
na
Which aircraft are you reporting an issue about? (Please also add the proper tag for it)
jets
Brief description of the issue:
attitude wrong
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
fly appr ifr or vfr. look at the attitude indicator bars above horizon would be climbing. fpm on right shows good descent. look at VASI all white 100ft above ground short appr. all white just b4 touchdown 30ft above ground touchdown. airport elev 96’. this is pretty normal appr and vasi all white.
PC specs and/or peripheral set up if relevant:
win 11 more than adequate
Build Version # when you first started experiencing this issue:
3 builds ago
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? 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 Community Support section.
This issue is not related to any addon.
Brief description of the issue:
In general, the PAPI lights and ILS Glide Slope Paths lead the planes to wrong altitude above the runways at the runway thresholds resulting in longer and incorrect landing. In reality, the planes should pass the runway threshold at 50 feet above the ground. This will give the pilots a chance to flare and land the plane properly at the aiming point. Currently the PAPIs lead the plane to at least 70 feet above ground and the G/S lead the plane to approximately 100 feet above ground which is incorrect. Also PAPI and G/S glide path a lot of times are very different.
Provide Screenshot(s)/video(s) of the issue encountered:
see the following video: https://www.youtube.com/watch?v=kucERBQMVl4
ICAO or coordinates (DevMode > Debug > Display position)
Detailed steps to reproduce the issue encountered:
Land a plane at several airports using PAPI lights and ILS G/S. See if you will pass the runway threshold at 50 feet above the ground (matching the charts).
PC specs and/or peripheral set up if relevant:
Irrelevant
Build Version # when you first started experiencing this issue:
From the introduction of the Sim
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
1 Like
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
Exactly what BossRaccoon7630 wrote
If relevant, provide additional screenshots/video:
Someone flagged my post as off-topic without reason, so let me say it in other words.
It’s disappointing that this has been a long-standing issue for years. Has anyone asked Zendesk if they plan on fixing it?
You likely won’t get anything useful out of Zendesk; once the feedback is logged to their internal tracker all they’re going to do is confirm that (which you already know, because the thread is tagged with “feedback-logged”) and close your ticket.
The only way to get any attention seems to be to hope that someone with access to the Asobo team happens upon the thread and brings it to the developers’ attention and they prioritize giving you a response, which is extremely rare.
(Note that simply pinging moderators in the hopes this will happen is forbidden by forum rules, so please don’t do that. 
)
1 Like
This is a reminder that this thread is meant to serve as a bug topic, not a discussion topic. If you are experiencing this issue, please feel free to report your findings using the following template. Outside of this, please use an existing or new topic in the appropriate #gd-commsupport sub-category to discuss this bug. All other posts will be removed.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
1 Like
I have noticed some airports have missing PAPI lights. KDLH is a prime example of an “International airport” missing a major piece of hardware. The PAPI lights are not shown any of the four runways.
AirNav: KDLH - Duluth International Airport (proves they are there.)
I’ve heard/read others (in other threads) saying they are misplaced too far down the runways in some places as well. Asobo, you need to spend more time making sure the basics are working before worrying about “missions”. Yes, it a game, but make it accurate.
1 Like
This is a long-running issue that has been detailed previously. To my knowledge, the problem has not been addressed:
The incorrect placement is one issue, addressed in this thread. The problem is, with the exception of bespoke and third party airports, they’re fairly defaulted to a position around 1000’ down the runway. If you’ve ever flown into a small airport, you’ll quickly realize there is no default and they’re placed in all sorts of configurations to provide not only obstruction clearance, but to get the airplane safely down in a reasonable touchdown zone. 1000’ on a 3000’ runway makes for a dangerously long landing. You’re already outside the touchdown zone (1st third of the runway).
The missing elements are another issue, part of a larger scope of incorrect/missing runway lighting, including approach lights, centerline/TDZ lights, REIL, vasi when it should be papi, 4-box papi when it should be 2-box, etc. I believe, and have collected evidence to support this notion, that the database used to generate airports (along with the AI scrub) is 15+ years old.
The reason the threads are separate is because one involves scrubbing a database for all lighting types, however the database does not contain VASI/PAPI position, which will instead have to be hand placed (or better noted by the next AI scrub). If we treat it the same, the positioning will get lost in the noise of correcting/updating the database.
1 Like
95% of the third party sceneries have misplaced GS/PAPI as well
It is incredibly frustrating that this is still not fixed, when will they look into this?
Since it will be a MASSIVE task, requiring a lot of data collection over a long time, I cannot see it being done any time soon, or even started any time soon.
Well the scenery gateway thing that was supposed to be released sometime back in the stone age is expected to allow crowdsourcing of such airport fixes.
1 Like
So my long landings arent my fault!!?
So really, would you get a better landing location going with 3 or 4 red, even though thats not realistic?
Unfortunately yes. And in some cases extremely so. NOTE: doing this could get you killed in the real world.
Also, the majority of real-world smaller runways only have a 2-box PAPI, so we shouldn’t expect the slightly above/below indications you’d get with a 4-box installation, but that’s often wrong in the sim as well, so here we are.
3 Likes
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
no
Have you disabled/removed all your mods and addons? 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 Community Support section.
no addons
Brief description of the issue:
vasi not accurate changes even when flight is steady.localizer/ glide path don’t match to vasi approach touch down should be same on all
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
fly
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
latest
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Can you provide an example? There are plenty of ILS approaches out there with a notation that the VGSI and GS are not coincident….