GS is rather steeper (3.8deg) than normal GS so you should reduce speed early. Set heading 290 immediately after reposition. Position Aircraft In Air with following parameter. the c172), where you can be sure that the Space-bar is not reassigned e.g. Remove line 14275 of following content of nav.dat.ĥ 47.31452500 011.60235000 1906 10970 30 69.000 OEJ LOWI 26 LOC If that does not work try first to use one of the very Standard airplanes (e.g.
#FLIGHTGEAR RADIO NOT WORKING HOW TO#
If someone knows how to use this LOC for approach, please lecture us.Īnyway unfortunately the first one is adopted by FG because FG can not assign 2 LOC for one runway. It is assigned to runway 26 but the course is 066. This is because LOWI has special approach pattern and 2 LOCs. Many thanks in advance! dutchguy Posts: 108 Joined: Mon 5:16 pm I don't know whether it has anything to do with the problem, but I'll mention it anyway.ĭoes anyone know what is going wrong here? Some airfields doesnt arrange one more radio for ATIS if there is a NAVaid close to. In the end it did start to move, but only when I was directly over the runway.Īlso, I remember that for EHAM it happened only the first time when I landed into that airport (I had departed it before), and here it also happened on my first time. The metar shows up, ATIS just doesnt read it. However, the localizer needle still shows the runway to be far to my left.
As can be seen in the screenshot, my nav1 radio is set to the correct ILS frequency, according to my gps, I'm aligned with the runway, and the runway is visible in the distance (dead ahead). Its not written in the instruction I tried to use fgfs.ext and.
Check the FlightGear radio button, then click the Start FG Plane button.), it asks me to choose some file, I am not sure which file to choose. Posted by Aakash Dawadee on Apat 6:31pm Hi everyone, I. When this didn't happen, I used the map to align myself with the runway, and descended since I was probably too close already. Hardware-in-the-Loop (HIL) with FlightGear not working. This time, however, I made sure to document it as soon as I saw it.Īccording to the approach plate, you should catch the glideslope at 9500 ft. Now, however, it has happened again, but now for LOWI rwy 26. The time after it happened everything went fine, so I didn't pay any attention to it any more. Some time ago I noticed that when approaching EHAM rwy 18R the ILS never showed any activity.
0 kommentar(er)
