Hi. In both 1.01 and 1.02 I've noticed that the LOC or ILS buttons do not engage. The only way for me to track the approach path is the VOR function as neither LOC/ILS would work. I know people reported funny behaviour when changing from INS to radio navigation but I've tried it in a flight between 2 nearby airports (TAPA to TFFR), without even turning on the INS, and I get the same issues. 

Also, I fly in VR. Could this be the problem? I'll try tomorrow in 2D in case it's a VR issue but hopefully this is fixed soon as makes approaches in tricky weather impossible. 

same here, in 1.0.2. ILS or LOC will not engage. Not flying in VR.

 

 

Edited April 16Apr 16 by Genista

Works for me, both NAV radios tuned to the ILS, and intercepting from underneath the GS seems to do it.  Maybe you're out of the engagement envelope?

It seems hit or miss with the ILS, I am one of those that cannot activate the ILS button even though ILS freq is tuned and showing so currently having to manually land. Also not flying in VR. Looks like still a few of us seem to have this bug which is strange when others are fine. I know Inibuilds have acknowledged its still happening to some.

It's still in the works, users have reported that ARMING both APs, and tuning both NAV Radios have increased the intercept and acquisitions. This behavior is still being looked into as well as improved. Let me know if this helps in the meantime, thanks 🙂

12 hours ago, IniJamir said:

It's still in the works, users have reported that ARMING both APs, and tuning both NAV Radios have increased the intercept and acquisitions. This behavior is still being looked into as well as improved. Let me know if this helps in the meantime, thanks 🙂

Did a flight today, can report that tuned nav1 and 2 with both autopilots engaged. She captured the LOC as I could not engage the ILS button. Once on the LOC and catured I could activate the ILS switch. Would not capture the G/S however. So 50% there.

 

 

Okay another flight done and noticed some things with repaints. Just flew BAW Landor G-BLUS and everything worked perfectly. Pan Am I flew before had no DH tape and also the ILS issue. So I wonder if its repaint dependant.

 

On 4/17/2026 at 8:18 AM, smileybeaches said:

Okay another flight done and noticed some things with repaints. Just flew BAW Landor G-BLUS and everything worked perfectly. Pan Am I flew before had no DH tape and also the ILS issue. So I wonder if its repaint dependant.

Repaints (those obtained via iniManager) should not affect this as there are no files included that would affect systems logic. We can't say the same for all community-made liveries however.

On 4/17/2026 at 6:53 AM, smileybeaches said:

Did a flight today, can report that tuned nav1 and 2 with both autopilots engaged. She captured the LOC as I could not engage the ILS button. Once on the LOC and catured I could activate the ILS switch. Would not capture the G/S however. So 50% there.

 

Changes have been made in v1.0.3, so please let us know if this is still the case now?

I was having the capture issue. But it appears to be because the trim got stuck and was disengaged the autopilot. This is on the ground once I discovered it as a possible issue. I have the entire Twitch stream if you want additional evidence from approach.

https://drive.google.com/file/d/1pvNbIW0-A-VRuO002RSzfBeAk64aREHU/view?usp=sharing

1 hour ago, Madwolf05 said:

I was having the capture issue. But it appears to be because the trim got stuck and was disengaged the autopilot. This is on the ground once I discovered it as a possible issue. I have the entire Twitch stream if you want additional evidence from approach.

https://drive.google.com/file/d/1pvNbIW0-A-VRuO002RSzfBeAk64aREHU/view?usp=sharing

You have CWS engaged, this will control the trim. Disengage CWS/CMD on the ground.