A330 - can not capture Localizer and Glideslope - tried several times on different airports.

[ChristerH]

Doing this with nothing in the Community folder.
I also reinstalled from Steam.
This happens every time.
The ILF frequency is not showing the identity and the Loc and GS are armed but does not lock.
I have a 3 min video with a detailed view on what is happening below:

Detailed view of the LOC issue.

[dmajestic80]

Wow, you posted this on the 1st Jan and haven’t had a response? I’ve had this issue twice now where I too am facing the same problem of which the ILS diamonds are missing. My issue is exactly the same as shown in your video. Correct Approach is entered, ILS runway displayed and Frequency is showing on PFD, LS is selected but no GS or LOC diamonds showing on PFD. As a result, even arming APP will not capture the Glideslope or Localizer, although GS and LOC showing in PFD. 
I have never had this issue in 15 years of flight simulation flying airbuses and I have now had this twice in a week using the a330. So this surely would have to point to a bug within the aircraft itself? 
I sincerely hope my comment doesn’t get ignored like yours has  

 

[ChristerH]

I'm sorry you have this issue but I'm also glad that someone else have seen this and its not me doing something wrong. I also see many people that do NOT have this problem and is really enjoying this aircraft. Very strange.

[Eddie]

Hello @ChristerH @dmajestic80

Apologies for the late reply gents. Seems this thread went a little under the radar as it was made during the holidays. Alas, let's get to it. 

We've had similar reports to this (this exact one from you earlier Christer on our Discord) and we've tried reproducing with no success. We suggested you try using a different mouse and check if it's reproducible. 

Alternatively, some issues are solved by completely reinstalling the simulator; I'd give that a try as well. 

Again, really sorry to hear that you two are experiencing this. Hopefully above will resolve it. Thank you! 🙂

 

[ChristerH]

Hello, I have reinstalled it two times and have the same issue. Can you clarify what you mean with using a different mouse ? How would that impact the LOC issue ?
The video really shows two issues, one is that the LOC is not captured and the other is that weird thing with the right ouse click. That is of less consequence. It is the non capture of the LOC that is the biggest issue.

 

[Eddie]

The issue appears to be that the ILS only becomes "active" (as seen on bottom left of the PFD) whenever you're panning views (i.e. using right mouse click). As the ILS signal is not active, the LOC/GS capture is naturally not working.
We aren't able to reproduce this issue on our end, so we suspect something hardware or keybinds related is causing a conflict that is affecting the availability of ILS signal.
So trying a different mouse will help narrow down the issue if on hardware side. Whereas changing controller profiles (mouse related) or interaction modes might help in case of a conflicting keybind.

If that still is not helpful, I would advise waiting for an upcoming update and trying again after that. May resolve the issue then. Unfortunately cannot comment on when an update by MS/Asobo will be pushed. 

Again, apologies for the inconvenience. 

[ChristerH]

Understand, that seems like a possible reason as this is not a widespread issue. Bindings in MSFS2024 seems to be a major issue.

I will give it a try at some point as I currently have MSFS2024 uninstalled. Thanks for the reply !

[Eddie]

No worries, lycka till!