February 19, 20251 yr I have recently experienced a failure of the ILS glideslope at one of my paid airports. FSDG- FACT. The frequency is correct both on Radar Contact and the PMDG 747-400 and the approach locks in fine. However, the glideslope is way under the plane and even at 1000' at 5nm from the runway, I cannot get near it. It is as if it is almost level with the ground. I do not know where to look. What generates the glideslope is it the Airport, NavData, the plane itself or what? Any help much appreciated. Intel i7 6700K @4.3. 32gb Gskill 3200 RAM. Z170x Gigabyte m/b. 28" LG HD monitor. Win 10 Home. 500g Samsung 960 as Windows home. 1 Gb Mushkin SSD for P3D. GTX 1080 8gb.
February 19, 20251 yr Look in the scenery AFCAD. You'll need ADE for that. Best regards,Luis Hernández Main rig: self built, AMD Ryzen 7 5700X3D (with SMT off and CO -50 mV), 2x16 GB DDR4-3200 RAM, Nvidia RTX 5060Ti 16GB, 256 GB M.2 SSD (OS+apps) + 2x1 TB SATA III SSD (sims) + 1 TB 7200 rpm HDD (storage), ID-Cooling SE-224-XTS air cooler, Viewsonic VX2458-MHD 1920x1080@120-144 Hz (G-sync compatible), Windows 11. Running P3D v5.4 (with v4.5 scenery objects as an additional library, just in case), FSX-SE, MSFS2020, MSFS2024 and even FS9! Lossless Scaling for all my sims. What a godsend...Mobile rig: ASUS Zenbook UM425QA (AMD Ryzen 7 5800H APU @3.2 GHz and boost disabled, 1 TB M.2 SSD, 16 GB RAM, Windows 11 Pro). Running FS9 there .VKB Gladiator NXT Premium Left + GNX THQ as primary controllers. Xbox Series X|S wireless controller as standby/mobile.
February 19, 20251 yr I also have FSDG FACT and went for a check flight approaching runway 01 (110.30) and 19 (109.10) using visible flight path. It looks perfect to me from the visible flight path and from the instruments in the cockpit. What I have in mind you may have taken the wrong frequency or have another afcad active. You may have used another FACT before buying the one from FSDG. My FSDG-FACT afcad is not modified. It's correct on my place and it's called AFD_FACT_v5.bgl and I use p3dv5.3. Regards Dan OS=WIN11 Home, Sim=P3D5 5.3 (P3D4 and FSX for install reasons) Addons=ORBX, ASCA, AS, TOGA and tons of sceneries, aircraft MB=Gigabyte AORUS Z790 Elite AX, CPU=i13900K, Cooling=Be quiet! Pure Loop II FX GPU=KFA2 RTX3090 24 GB, RAM=64 GB DDR5-5600, HOTAS=Logitech G Saitek X52 Pro Visit my website for fixes and addons: https://sites.google.com/view/dans-p3d-mods
February 19, 20251 yr Author 1 hour ago, blaunarwal said: I also have FSDG FACT and went for a check flight approaching runway 01 (110.30) and 19 (109.10) using visible flight path. It looks perfect to me from the visible flight path and from the instruments in the cockpit. What I have in mind you may have taken the wrong frequency or have another afcad active. You may have used another FACT before buying the one from FSDG. My FSDG-FACT afcad is not modified. It's correct on my place and it's called AFD_FACT_v5.bgl and I use p3dv5.3. Regards Dan Thanks Dan. I have that exact file and no other version of FACT files show up in a search. It has worked fine ever since I bought it, so I doubt if it is an old version that is conflicting. I deleted and re- installed the airport and ran Makerwys, so the info should be up to date. Tomorrow, I will try a flight to another airport and see if ILS works. Looks like it is going to be a long painful process. Intel i7 6700K @4.3. 32gb Gskill 3200 RAM. Z170x Gigabyte m/b. 28" LG HD monitor. Win 10 Home. 500g Samsung 960 as Windows home. 1 Gb Mushkin SSD for P3D. GTX 1080 8gb.
February 19, 20251 yr 1,000 ft 5 miles from the runway is way too low anyway. At that distance you would typically be at around 1,500 ft David Porrett
February 19, 20251 yr Author 10 minutes ago, DavidP said: 1,000 ft 5 miles from the runway is way too low anyway. At that distance you would typically be at around 1,500 ft Exactly what I am saying. Even at that height the Flight path is still below me. Intel i7 6700K @4.3. 32gb Gskill 3200 RAM. Z170x Gigabyte m/b. 28" LG HD monitor. Win 10 Home. 500g Samsung 960 as Windows home. 1 Gb Mushkin SSD for P3D. GTX 1080 8gb.
February 20, 20251 yr Don't forget https://www.aero.sors.fr/index.html may be of help in this if you are using "current" charts / FMS data. for now, cheers john martin
February 20, 20251 yr Sounds like it could be an elevation issue. Does your aircraft actually intercept the glidescope if you fly low enough and is then taken "underground"? Ian S
February 20, 20251 yr Author I haven't been able to get low enough without crashing. It seems to be at ground level. So, I think the answer is yes. Intel i7 6700K @4.3. 32gb Gskill 3200 RAM. Z170x Gigabyte m/b. 28" LG HD monitor. Win 10 Home. 500g Samsung 960 as Windows home. 1 Gb Mushkin SSD for P3D. GTX 1080 8gb.
February 20, 20251 yr 17 minutes ago, IanHarrison said: I haven't been able to get low enough without crashing. It seems to be at ground level. So, I think the answer is yes. Can you check if the airport scenery is at the top of the layers? Try Lorbi's product if you have it? Do you have Orbx Africa LC?, if so ensure the FACT scenery is on top of it. Ian S
February 20, 20251 yr Using ADE you can search for all active Airport BGLs for a given Airport, and de-activate any that may cause a problem. Raymond Fry.
February 20, 20251 yr 2 hours ago, G-RFRY said: Using ADE you can search for all active Airport BGLs for a given Airport, and de-activate any that may cause a problem. The title "Beyond my knowledge" suggest that the threadstarter can not follow your cryptic hint. You may want to explain this procedure in a way, ordinary people can understand it. OS=WIN11 Home, Sim=P3D5 5.3 (P3D4 and FSX for install reasons) Addons=ORBX, ASCA, AS, TOGA and tons of sceneries, aircraft MB=Gigabyte AORUS Z790 Elite AX, CPU=i13900K, Cooling=Be quiet! Pure Loop II FX GPU=KFA2 RTX3090 24 GB, RAM=64 GB DDR5-5600, HOTAS=Logitech G Saitek X52 Pro Visit my website for fixes and addons: https://sites.google.com/view/dans-p3d-mods
February 20, 20251 yr Author Thanks for all the suggestions. Good news. After doing a re-install of the Airport (to no avail), and checking all the frequencies (with ADE!) I decided to try a repair of the actual PMDG 744 and for good measure to reload NavData from Navigraph. That seems to have fixed it. This morning I flew both 01 and 19 approaches and the Localiser and Glideslope worked perfectly. I have no idea what caused this to happen but thanks to all the helpful people out there. I am back in business! Intel i7 6700K @4.3. 32gb Gskill 3200 RAM. Z170x Gigabyte m/b. 28" LG HD monitor. Win 10 Home. 500g Samsung 960 as Windows home. 1 Gb Mushkin SSD for P3D. GTX 1080 8gb.
Create an account or sign in to comment