KLAS runway ILS issues [navigraph]

AndyM
Posts: 88

Re: KLAS runway ILS issues [navigraph]

Post by AndyM » Sat Dec 09, 2023 7:51 am

My file is Read Only, but prior to updating Navigraph I have to uncheck it so that it updates okay. I now have a copy of the Content.xml file with the correct order of addons in a different location as well that is Read Only, so that after I have unchecked the original to update Navigraph, I then just copy and paste the Read Only file from the backup location to over write the Content.xml file that Navigraph altered. Hope that makes sense.
trisho0
Posts: 331

Re: KLAS runway ILS issues [navigraph]

Post by trisho0 » Fri Jan 05, 2024 11:11 pm

Installed the FT KLAS Las Vegas in MSFS2020 and my Bird landing weird as per screenshot. I think we need a new AFCAD file to correct the ILS of runway 26L and probably other runways too.
How to land as expected? Maybe next updates?

Patricio Valdes
FT-KLAS-RWY26L-grounded.jpg
FT-KLAS-RWY26L-grounded.jpg (180.44 KiB) Viewed 365 times
dcrflight2024
Posts: 3

Re: KLAS runway ILS issues [navigraph]

Post by dcrflight2024 » Sun Jan 07, 2024 10:02 am

I have 41 other scenery's I have purchased. Why is this the only one that has this issue? The quality is outstanding but seems Navigraph is blamed for this ILS 26L issue. It would appear an update would rectify this. I see where there was an update in March of 2023 but I purchased this in June 23 I believe. Should have been correct at that time. It is now Jan of 2024 and still the same issue today. If anyone knows please advise. TIA

DCRFlight2024
trisho0
Posts: 331

Re: KLAS runway ILS issues [navigraph]

Post by trisho0 » Wed Jan 10, 2024 7:20 pm

Tested FT KLAS Las Vegas with P3Dv4 and P3Dv5; landed on runway 26L nicely. The issue is with MSFS2020. Please, a fix is needed.

Patricio Valdes
Procamper96
Posts: 2

Re: KLAS runway ILS issues [navigraph]

Post by Procamper96 » Wed Feb 14, 2024 8:54 pm

As I have posted elsewhere on this forum in another thread on this topic:

It is a little baffling to me that this is indeed still an issue (for me, only when flying the Fenix as I have implemented the fix above, which doesn't work for the Fenix). I have reported this as a bug to both Fenix and Navigraph in the past since it seems FlyTampa has no interest in fixing their erroneous runway elevation and glideslope, and the reply has pretty much been that it's a FlyTampa issue since their airport data is incorrect. This is not a case of "our scenery works this particular way," this is a case of "our scenery is incorrectly modeled so we had to build a workaround" when absolutely no other payware scenery is this far out of whack with real-world data. I have to seriously question FlyTampa's priorities spending all that development time and effort on animating the sphere in the strip and such when there is a genuine sim-breaking issue on the most common instrument approach into the airport. I'd much rather have a glideslope that works properly and matches real-world data. Even if the "corrected" glideslope is used, your minimums callouts will still be so far off that a go-around call at minimums in instrument conditions would be far too late if you use FAA charted Baro minimums.

I can accept an occasional tweak that needs made on the user-end, but having to dive into the config files and make changes every time I want to update my navigraph data also doesn't seem to be an acceptable solution in 2024. It seems there is a pretty long to-do list for FlyTampa to get this scenery working again. If I hadn't purchased through the marketplace where customer support is all but nonexistent, I'd be demanding a refund and waiting for another dev to take on the project and do it right.
Post Reply