MarsVenus

Update to V 1.06 - EA Basic variant still unable to capture localiser and glideslope on runway extended centreline on launching from a saved game. Both localiser and glideslope magenta "triangle" indicators remain inactive. If game is played from new flight, then ILS can be captured without problem. I then tried using the same saved game. After launching and flying for a while I used the jump ahead function to jump to a waypoint nearer to the runway for approach. I then extended the runway centreline, flew parallel to the centreline and turned the plane back to capture the localiser and glideslope along the centreline. I was successful in capturing both the localiser and glideslope. Both were active and the aircraft followed the ILS onto the runway. You may want to use the attached saved game starting from EDDF using the AB variant of the Inibuilds A380 v 1.06 to testScreenshot 2026-10-30 11-18-48-3.mp4 AB-EDDF-07C--LFPG-09L-TOD.bin

I extended the runway centreline in EGCC 23R and vectored myself back onto CF23R. On final approach to runway 23R localiser and glideslope were captured and centred in PFD with magenta indicators but aircraft no aligned to runway centreline (see atached)

LKPR/06 N0418F280 DOBE8E DOBEN DCT NIRGO T108 LANDU LAND2A EDDM/08L Saved file and photos showing loc and gs not re-activeAB--LKPR-06-----EDMM-08L.bin

Flew the A380 EA Basic variant under V 1.04. Localiser and glideslope cannot be captured. Both megenta indicators in PFD remain inactive and do not move. But no such issue in the RR variant

This same issue was seen on the RR variant during V1.03, but after update to V 1.04, this issue was resolved

Inibuilds A380 - Looks like all saved games under V 1.03 now no longer works after update to V 1.04. All saved games loaded with WASM crashes with orange instrument panels in cockpit.

Encountered this whilst flying the EA Cabin variant after TOD. See attached. But did not encountered this issue on the RR variant

I updated to Version 1.03 and flew a 1.5 hour flight from Hanoi to Hong Kong. I am glad to report that after the update the frequent autopilot disengaging that I encountered previously above, did not happen at all throughout the flight even as I turned on live weather and medium turbulence. I did calibrate my joystick in Windows though before I flew that flight. I extended the runway centreline and the aircraft did capture the localiser and glideslope beautifully.

I have tried everything that were suggested...adjusted turbulence to low, unbind autopilot keys, no live weather, increase sensitivities of flight stick to 5%, no auto rudder and other stick controls etc.....nothing works. Seems these intermittent autopilot disengage happens on every flight but with varying frequencies...the most frustrating thing about flying the aircraft. I am at wit's end as to how to neutralise this very frequent autopilot dis-engaging. One factor that would make me give up on flying this aircraft. Starting to regret on my purchase of the Inibuilds A380. The free FBW A380 flies flawlessly.

Inibuilds A380 - When can we transfer the sim from MS Marketplace to iniManager for easier updating

Some additional info to my above post. If I launched a previously saved game from the EFB, on an ILS approach to the runway I cannot capture the localiser nor the glideslope as both the magenta on the right of the PFD are not active. But if I launch the same saved game from the EFB but then used the Jump to function to jump to any waypoint ahead in the flight plan, then on ILS approach to the runway, the localiser and the glideslope both become active and both can be captured the magenta triangles on the right of the PFD are active and a proper ILS landing can be achieved. Strange?

Please note that in the PFD the localiser and glideslope are capturedIls Not Aligned To Runway.mp4 but aircraft not aligned to runway

loadiyng in, do you have a flight plan Yes, I do. I launched from a saved game and the MCDU shows the flight plan as saved previously. On approach, after pressing LS on both sides and trying to intercept the Localiser and Glideslope both related magenta indicators do not show up and remain inactive.

The Speed window indicator alternating between "SPD" and "MACH" throughout the flight? A bug or normal?speed indicator.mp4

Even after updating to Version 1.01 the localiser and the glideslope remains dead and inactive if game is launched from a previous save game. In that case saving a game to continue later is redundant.