Juanos1980 Posted April 12 Posted April 12 Evening. thought it would be best here. so I e tried two flights one on launch and now another after the latest update. however when running in the ILS freq in Miami for Rwy 09. Which is 110.90 I’m just picking up the localiser on the HSI at all. I am however clearly seeing the Glideslope on the right. I’ve select radio on the button for insgos/radio. But the localiser doesn’t appear to pop up. however on the standby hsi I’m getting the dme to the localiser and the direct of it. But on the primary hsi nothing is showing. is this still a bug as I’m trying to do some ILS app and without it working is making things quite tricky in low visibility ?
IniJamir Posted April 13 Posted April 13 Hi, there are known issues with the ILS not capturing on the current build, sometimes enabling both APs and tuning both the CPT and FO sides for the ILS/LOC will help but still not guaranteed, issue is known and further fixes are coming in future builds. Thank you
Juanos1980 Posted April 13 Author Posted April 13 Appreciate the reply as it’s quite a tricky thing not to have working. Thankyou Inibuilds.
Juanos1980 Posted April 13 Author Posted April 13 It’s not about capturing the localiser. on Xbox x the localiser for an ILS freq with RADIO set doesn’t even pick up the localiser
IniJamir Posted April 13 Posted April 13 7 minutes ago, Juanos1980 said: It’s not about capturing the localiser. on Xbox x the localiser for an ILS freq with RADIO set doesn’t even pick up the localiser Are you able to check and verify that other aircraft (Inibuilds and Non-Inibuilds) are picking up the Localiser? Additionally what are the details of the VOR station you are attempting to acquire
Juanos1980 Posted April 13 Author Posted April 13 The A300 , A320 Neo and A340 and A330 and A350 all do it fine although it’s very different to the Tristar. from where I am. If I tune the ILS freq for x runway and set the Tristar switch to radio it should pick it up instantly. it doesn’t.
Juanos1980 Posted April 13 Author Posted April 13 Surely this isn’t a new thing that you’ve heard of ?
Eank1954 Posted 6 hours ago Posted 6 hours ago On 4/13/2026 at 12:55 AM, Juanos1980 said: Evening. thought it would be best here. so I e tried two flights one on launch and now another after the latest update. however when running in the ILS freq in Miami for Rwy 09. Which is 110.90 I’m just picking up the localiser on the HSI at all. I am however clearly seeing the Glideslope on the right. I’ve select radio on the button for insgos/radio. But the localiser doesn’t appear to pop up. however on the standby hsi I’m getting the dme to the localiser and the direct of it. But on the primary hsi nothing is showing. is this still a bug as I’m trying to do some ILS app and without it working is making things quite tricky in low visibility ? In any case, dealing with low visibility and no localizer definitely makes the approach tricky! Hopefully, a fix comes soon, but in the meantime, if you're looking to relax and take your mind off the technical issues, you could check out rolldorado bonus — an online casino where you can test your luck on various games while waiting for the update fix. It’s a fun way to unwind, and who knows, you might hit the jackpot and make that next ILS approach a whole lot easier! The fact that you're getting the glideslope but not the localizer on the primary HSI definitely points to something being off. Normally, both should be picked up together, especially when the localizer frequency is tuned correctly, as it is in your case (110.90 for Miami Rwy 09). If you're getting the DME to the localizer on the standby HSI, but it's not appearing on the primary, it could be a couple of things: Radio Source Selection: Even though you’ve already selected the radio source on the button (INS/GPS vs. Radio), double-check to ensure it’s set correctly. Sometimes after an update, these settings can get reset or might require a manual override to ensure it's sourcing from the proper nav radio for ILS. HDG or CRS Setting: Verify that the heading or course setting on your HSI is properly tuned to match the localizer's course. If the course isn't set to the runway's ILS approach course (around 090° for Rwy 09), it won’t display the localizer properly. Software Bug: It’s also possible that this is still a bug related to the latest update. Sometimes, after an update, certain avionics or display systems take a bit of time to sync up, especially with navigation data. If it’s a known issue, I’d recommend checking the forums or patch notes to see if others are having the same problem, or if there's been any mention of it being fixed in a hotfix. Reset or Reboot: As a last resort, try rebooting the system or reloading the flight. It sounds simple, but sometimes avionics glitches can clear up with a restart, especially if they’re related to software syncing. I totally get how challenging this can be in low visibility, though! Hopefully, this can help narrow down the issue, but if it's still a bug, it might need to be addressed with the next patch. Let me know if you find anything that works!
Solution Juanos1980 Posted 5 hours ago Author Solution Posted 5 hours ago Appreciate the feedback. so I didn’t realise on the GARMIN GPS you had to change from GOS to L LOC. I’ve done that and with update 1.0.2 all is working. Really great aircraft by the way. Will continue to monitor things as more flights take off 🙂 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now