Azlog

I'm on Xbox series X so not got any WASM crash error log. But I just posted in this thread now speculating that not all arrivals are prone to WASM crashes

I just had what can only be described as mixed results on 3 flights. On the first flight, I flew KLAX to LEMD. While in the air, I noted that the arrival was the ZAMORA 5A for an ILS 18L VIA RILKO and so I programmed this in and went to bed. In the morning, everything was still fine but the wind had changed. So I got brave and changed the arrival to ZAMORA 5C for an ILS 32R approach VIA FAFEQ. Worked no problem so I landed and ended what had been a very nice, uneventful flight. I then flew down to Casablanca GMMN, programming the arrival (TUSOR 1A for ILS 35R VIA KOTAG) before I departed due to the short flight time. Took off, flew and landed, again no issues. Then I flew back to LEMD ... Despite the short flight, I didn't program the arrival on the ground and instead did it during the climb but I don't think that made a difference. Arrival was to be SOTUK 4C for an ILS 32R approach VIA FAFEQ. Not expecting any issues as it had worked fine on the previous 2 flights, I entered this and the instant that I selected FAFEQ from the dropdown menu, everything went orange. This is making me think that there's a chance that some arrival routes are problematic but not all, hence the mixed results

Just had a ghost WASM crash in the A350-1000 (version 1.2.4) around 2 hours into a flight from Boston to Heathrow on Xbox series X 😞

So the livery packs are here now, but what happened to the livery that we all loved on 2020 and wanted on 2024?

And the “Bird” doesn’t work. Toggle switch for FPV/FD goes up but doesn’t reset back to centre and change from FD to FPV

One more small thing - logo lights don’t work 🙂

That’s fantastic news - chuffed to bits

So happy to finally have an updated A300 premium on Xbox series X. Performance on SU5 beta is fantastic and I’m loving being back in the skies in my favourite aircraft. But a couple of small things I’ve noticed: 1. many of the clickspots on the overhead panel are tiny compared to the size of the buttons. Takes some very precise mouse movements to turn on the fuel pumps for example. Wouldn’t like to be trying to do it with a controller in cursor mode 2. liveries. The base aircraft comes with less liveries than it did in 2020 and none of the purchased livery packs are compatible. Please bring those to us - I’m missing my flying banana, my UPS freighters and my shiny silver AA in particular

As the title says, flying the approach extend flaps 1 and you hear them. For some reason 1+F automatically comes out when the speed drops enough. Correct me if I’m wrong as could be A350 specific but these should only be for takeoff and shouldn’t extend to this settings? But then you select flaps 2 and silence while they extend which doesn’t seem right And then flaps 3 and flaps full you hear them again.

I have noticed that in cruise, the engine blades are spinning very slowly as though they were windmilling in a way that you would expect to see on the ground at the gate. Xbox 1.1.8

I just mentioned this in another thread that I started on the A350 1.1.8 on Xbox but I am having to manually enter the ILS code into the NAV AID page every time. I'm using the sim default nav data as the navigraph data won't update since SU4 but it's been this way since the 1.1.8 update. I have tried multiple airports both 3rd party and default and encountered the issue every time

I know we're an update behind but I don't see anything about these on the 1.1.9 PC changelog so here goes: The aircraft keeps trying to go to 1+F flaps setting. Climb outs close to the max speed for 1+F cause the flaps to constantly retract and extend between 1 and 1+F as speed fluctuates. On approach, you select flaps 1 and once it gets there, it automatically then goes to 1+F which it shouldn't do The ILS never populates itself on the NAV AID page. I always have to do this manually during the descent And finally, since SU4, I can't get the -1000 engines to start. The red line appears on the EGT gauge as normal but nothing happens. No such issue on the -900

Took the PAX version for a flight last night and performance is better than it was thanks for SU4 but still has some work to do to get it to being enjoyable to use like the rest of the airbus family (inc. A350). But while I'm here, we still don't really have any liveries on Xbox. None of the livery packs are compatible and the base aircraft only includes 1 livery per type (FedEx on 300F PW, Hong Kong on the 300F GE, Monarch and Thai on the 300 PW and Emirates on the 300 GE) which is significantly fewer than the base aircraft on 2020

I really hope this aircraft finally gets updated with SU16.1 appears as there is much that is fixed on the FS24 version. But while I have managed some RNAV approaches in this on 2020, it seems to be a bit hit or miss. Yesterday I was doing 22R at Nice LFMN and APP NAV remained blue so I had to hand fly the whole approach from the FAF. Vertical deviation showed correctly on the PFD

Yeah it probably got auto-deleted after this time. I’ll see if I can do another and get that onto YouTube so it stays. But the key is to have your FCU altitude set as the final approach altitude on the charts. So for runway 21 at LFRS you need to be at 3000ft by waypoint FRS21 in approach mode on the MCDU and with flaps 3 and gear down