LOC/ILS updated files test
-
hello
quick local flight to test the ILS (LOC/GS) with v1.06.
60° intercept - uuhhh........ hard work for the system but gets the bird aligned and established - thats the way to go!
maybe some fine-tuning after more flights.
and: the tablet is a nice surprise - I like it - thank you very much!
stay healthy -
Now that the LOC intercept is fine, maybe the Glideslope intercept needs to be revisited as well. Please see attached screenshot. Due to the Speed reduction VS has dropped to -1200fpm, the Glideslope indicator is at two dots already, and there is no attempt anymore to correct.
This happens not always, but at every third flight it does. Initially it's correct, but it looks as it can not handle the speed reduction and at some point simply gives up correcting at all.https://www.dropbox.com/s/xbpwb9of008d4s3/glideslope.jpg?dl=0
Mike
-
Can you update me on how the localiser and glideslope hold are behaving with v1.6.2? I've just flown a stable ILS approach into Orbx EGNT (one of the earlier examples above) without any issues, capturing the glideslope first and then localiser with an approx. 50 degree intercept. That was after a quick circuit so no use of the FMC/LNAV.
EDIT: Also flew the same ILS after using the FMC/LNAV, again without any issues.
Can you also confirm what version of P3D v4 or v5 you are using?
Is use of the HSI nav selector switch (RNAV/NAV) still causing issues?
-
Hi Martyn,
I'm using P3Dv5.2. HSI NAV Selector is fine. So is the LOC intercept. But Glideslope has the same issue as described above. It initially intercepts it correctly. But then it doesn't cope for the speed reduction, so it more and more deviates with no further attempt to correct. Without manual interference it's almost at 2 dots below at decision altitude.
I get this on 8 out of 100 attempts. After the initial correct intercept I don't see any attempt to STAY on the Glideslope. The vertical speed stays the same even though the speed gets reduced.Mike
-
@mikealpha Hi Mike. Do you get the, "Established on the ILS", call-out when that issue occurs? Or just the, "Glideslope captured", call-out?
If possible a video showing an ILS approach where this issue occurs would be great in identifying the cause.
