Please provide more information such as plane, airport, runway, ILS, etc. where you are experiencing this issue, and with proper reproduction steps. Unfortunately limited information like this does not help the test team figure out if there is a bug.
why are airport beacons on during VFR daylight? they should only be on in IFR conditions
papi vasi isn’t consistent on a stable flight path or even unstable flight path.
ground vehicles driving into path of airplanes
taxi lights in middle of taxiway intersections where they shouldn’t be.
jetway shocked me by positioning itself to plane at gate. happened once never again even when using hotkey
restart a flight and plane is in the grass instead of starting where it originally started
the list goes on but i’m sure msfs2024 will fix it all …
I’ve already corrected five airports in the world Hub! But I’ve also been correcting taxiways and parking, so it’s not just focused on lights.
I’m still trying to discern standards and expectations over there and learning how to triage accordingly. I do not yet know the criteria for acceptance of the edits.
That said, 5 down, probably several thousand to go!
Yes. I’ve been correcting other airport items as well. It sure is nice to be able to fly into more airports with the benefit of VASI, PAPI and approach lights accurately placed, with the proper slope and of the correct type!
Unfortunately, while the small number we can do may be fixed, there are, as you state, thousands more that need to be.
I totally can’t just stop at lights. I wish I could, but before long I’m redoing the entire parking ramp and everything else.
I don’t know the rate of how these will be accepted and implemented in the sim, so it seems like you want to get it done in one shot versus piecemeal, where we submit one, then come back for more. My worry with the latter is that it’ll just be a lot of re-work, not necessarily knowing (or trusting!) that the lights alone have been done correctly. We need a lot more feedback.
Yes, I hope they get a list together defining what is acceptable and what is not, and kind of a checklist to go by so there will be some structure to what is done by all. There are many things wrong or not yet included at many airports, at least all those I’ve done so far. Each airport fixed “completely” represents many hours of tedious work (anywhere from 24 to 60 hours or more). It’s going to take a long time with many people involved!
They will as soon as the beta is over. Each person making changes lists the changes made when the airport is submitted and these are shown on the Worldhub website.
It’s really annoying isn’t it. I forgot about this thread and made another thread, and one of the mods said he’d never even heard of the issue. I found that surprising as it’s so common.
Yep or you can be perfect on the papis and can tell perfect by the picture you see in front of you and the plen will be shouting glideslope glideslope glideslope
Apparently the position data for VGSI are now being provided by the FAA! This seems to have started a few months ago. This is being updated every 28 days.
I strongly urge the Asobo folks to look into incorporating these data for correct placement, angle, type, etc.
Here are the data fields included:
ARPT_ID – Associated Airport Ident
RWY_ID – Associated Runway
VGSI_LIGHTS_TYPE – (VGSI_CNFG_CD) Type of VGSI Lighting
TH_CROSS_HT – (TCH_MSMT) Threshold crossing height
COM_ANGLE – (CMSN_ANGLE_MSMT) – Commissioned Angle
REF_PT_LAT_DEG – (LAT_DEG) – Reference Point Latitude Degrees
REF_PT_LAT_MIN – (LAT_MIN) – Reference Point Latitude Minutes
REF_PT_LAT_SEC – (LAT_SEC) – Reference Point Latitude Seconds
LAT_HEMIS – Reference Point Latitude Hemisphere
REF_PT_LONG_DEG – (LONG_DEG) – Reference Point Longitude Degrees
REF_PT_LONG_MIN – (LONG_MIN) – Reference Point Longitude Minutes
REF_PT_LONG_SEC – (LONG_SEC) – Reference Point Longitude Seconds
LONG_HEMIS – Reference Point Longitude Hemisphere
REF_PT_ELEV – (POINT_ELEV_MSMT) – Reference Point Elevation
REF_PT_THRES – (THLD_DIST_MSMT) – Reference Point Distance
The key to this would be using the reference point lat and long (which defines the threshold for the associated runway) and computing the REF_PT_THRES, which is the distance from the VGSI to the threshold. Unfortunately, there is no lateral position or spacing, but this would at least give the proper glidepath and TCH (assuming the runway elevation and slope data are correct).
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:
The ILS and PAPIs are all over the shop.
If relevant, provide additional screenshots/video:
Just watch some streamers… it’s been widely discussed for years, unbelievable that it hasn’t been properly addressed at all. If you can’t fix it, at least say that. Same with turbulence, rudder sensitivity, freelook controls lock, 0.5 FPS over the poles… not buying 2024 until all those are fixed.
It doesn’t even seem like its off by a constant amount, but rather that its not a straight slope, and seems to have a curve below 400ft-ish.