26L ILS MSFS
Re: 26L ILS MSFS
Would be great to have a statement from FlyTampa on this, and if they are going to update taxiway C (Charlie) as well.
Re: 26L ILS MSFS
Problem is the same on 26R as well, but because the threshold starts much earlier you land on it as opposed to the approach lights.
Last edited by BrianT on Fri Oct 20, 2023 3:54 am, edited 1 time in total.
- emilios[flytampa]
- Site Admin
- Posts: 1626
- Procamper96
- Posts: 2
Re: 26L ILS MSFS
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.
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.