I would like to report a small error on the taxiway signs in EKCH. When we are on taxiway "C" approaching taxiway "B" taxiway (on both sides on B taxiway), the signs on taxiway "C" say that we are on "B" with directions for taxiway "C". In fact, it should say that we are on "C" with direction to tax...

I too had app hang around CYUL/CYMX after installing MirabelX. Could not correct the problem so I uninstalled MirabelX and that solved the problem. Even though the scenery is said to be compatible with FSX and Prepar3D, there is no mention of which version of P3D. My guess is that MirabelX has somet...

Gerrit, I updated Vienna 2.9 to the new V3.0 this afternoon using the universal setup without uninstalling 2.9 first (updated on top) and everything is OK. For P3D v4.4, all you need is "FlyTampa_Universal_P3D_Setup.exe". I did the same with all my other P3Dv4 sceneries and all is well. The only tim...

The ILS are from stock indeed, and those seems to have the DME co-located with the localizer instead of the GP. This explains the distance error when compared to the approach charts.

The only solution I can think of is for someone to replace the stock ILSs with corrected ones.

randy wrote:I just bought it from this website, i get this weird blue aura around the airport. Any ideas how to get rid of this ?

Go into your P3D "Navigation / Navigation Aids..." menu. You have some navigation aids items selected (probably airspace).

Mine does (Athens v1.6 patched on P3D 4.1). If you are checking the file with ADE, make sure that the option "View - Hold Short Node Limits" is checked otherwise it won't be displayed.

Hi Daniel, George will correct me if I am wrong, but in 2015 when FT CYUL 1.4 was released, the only runways with PAPIs at CYUL were 06R and 28 (as correctly depicted in the scenery). The current "Canada Flight Supplement" (August 2017) now shows that only runway 28 still has PAPI, probably because ...

george[flytampa] wrote: Thanks NBouc. My fault; I screwed up some code & was working from the wrong Athens build.
Download Lights_ath.zip again & you should have working lights.

Thank you George, it works. I now have approach lights at both ends of the runways and no CTD. I am a happy camper

It looks like the lights are completely missing. The smaller lights you can see are just the night textures on the approach light poles. Check again you installed the files from within lights_ath.zip into your Athens\scenery folder. George, the files from "lights_ath.zip" are present in the Athens/...

george[flytampa] wrote:
Could you post a screenshot please?

George, here's how the approach lights look on my computer. I tried with re-installing the libraries and deleting the shaders, but with the same result.

George, Having the same CTD problem as mentioned in this thread, I tried your new approach lights (lights_ath.zip) at dusk and at night, with the default BE58 and PMDG 777 (3D Grass OFF). The good news: no more CTD. The bad news: The new approach lights only become visible at 1/2 nm on final on all ...

Hi Boeingman07, I don't know for sure if it would solve your problem, but using Open LC NA myself, I always deactivate Fly Tampa's Toronto_LC in P3Dv4 scenery libraries to avoid conflict between the 2 LCs. I do the same with Sydney_LC since I am using ORBX Australia. It might be worth trying since I...

What if I still have P3Dv3 installed with my Fly Tampa sceneries in P3Dv3 and want to install them in v4 ? Should I uninstall the FT sceneries in P3Dv3 before re-installing them in P3Dv4 ? (or can they co-exist in both version 3 and 4 of P3D ? You leave your V3 installation as is, install into V4 u...

What if I still have P3Dv3 installed with my Fly Tampa sceneries in P3Dv3 and want to install them in v4 ?
Should I uninstall the FT sceneries in P3Dv3 before re-installing them in P3Dv4 ? (or can they co-exist in both version 3 and 4 of P3D ?