That's strange. In a normal situation approach would give you final vectors/or let you fly a STAR to an ILS approach localizer, and when you are established (when your autopilot has picked up and is flying the localizer direction), they would hand you over to Tower. If you do capture the localizer, you can try manually tuning (or using the ATC menu) to the tower and request permission to land.
Hello SkyyStorm, thanks for the reply.
Yes, I am handed to approach, they tell me to "continue flying as planned", they make me set the altimeter, and then they disappear, as told.
Yep, I know that the above should happen in normal situation, it's more or less what it was used to be in FSX... The problem is, they never give me vectors... The lowest altitude I was in one of my flights was 2.200ft, which I believe is more than enough to catch the glideslope, I had the ILS freq set, but I never picked up any signals, which led me thinking maybe LIBP was bugged.
One reason they didn't might be that your altimeter setting (barometric pressure) is not correct, so you indicate higher than you are. Try pressing "B" when closer to the airport or set it yourself based on the ATIS (or a METAR) for that airport.
Been there, done that, but no success.
As for not descending via AP, with the Garmin 530, if you are close enough and looking to line up to the runway, you should switch it using CDI(I think?) to VLOC mode, after setting the ILS frequency. That changes the AP from flying the GPS route to capturing the localizer based on your NAV frequency.
Hm... So, what I did was to set the ILS frequency on NAV1 and I confirm you have to switch to VLOC pressing CDI button (I watched a video about it) once you are established on the localizer.
I simply haven't got there because I never pick up the ILS signal, that's what bother me.
I did not remember I had then to switch to approach mode frankly, but I have never got there, so it doesn't matter (at the moment).
Anyway, you confirm that once I am handed over to approach, I should receive vectors to final, so something is wrong here.
Maybe MSFS is fooled by the way I build the flight plan in LittleNavMap?
I select the departing airport and add it to the flight plan with one of its SID procedure. Then I select the destination airport and add it to the plan with one of its STAR. And then finally I select the last leg of dep and the first of arr and "calculate an IFR plan between selected legs". Maybe that's what's confusing MSFS? (It shouldn't though)