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! 

[ChristerH]

Eddie,
I tried again after SU1 and I still have the issue.
What I'm seeing is that ANY VOR seems to be inactive as a default and when I use the right mouse button, the LOC engage. I could actually make it go back and fourth on the LOC course by holding and releasing the mouse button.

So the question is, what is controlling the VOR/LOC being active in the bindings ?
I tried with a different mouse but no improvement. I also made sure that nothing related to VOR is mapped to the mouse.

So this is truly vexing as there is some setting that is established with LOC/VOR non active when I start the plane.
Do you know if there is any setting in the plane that would create that behavior and if it is mapped with any action?
I think that is the key question.
On the two images you see the VOR status with right mouse button held in.  (Pic 1) and then without the right mouse button held in. (pic 2)

Edited March 16 by ChristerH

[ChristerH]

Additional interesting observation:

When I initially start up the A330 with the GPU, the VOR is active, but as soon as it is OFF, the VOR is inactive.
So as follows:

- Start plane from cold and dark with GPU on and APU on. VOR works.
- Disengage external batteries with APU on - VOR do NOT work
- Turn on external batteries - VOR works
- Start engines and then turn off external batteries. VOR does NOT work
- Turn on external power when the engines are running. VOR works

So this is very strange. I have not tried this, but if I could turn on external power in the air, I bet the VOR comes back working.