Azlog

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

Need to test this in 2024 as well but last night on 2020 I had my first go-around in a long time and it was an RNAV approach into EFHK runway 33. First approach the RNAV engaged perfectly and there were no issues. But I floated it half way down the runway due to gusting winds and went around for another go. On my second approach having set it up again, Alt and Nav remained green with the RNAV indicators remaining blue. Vertical deviation box was working so I just followed that manually

Here’s the video of it working into Nantes LFRS 21 https://www.xbox.com/play/media/aZuRixYhq7

Doing LFRS 21 right now on 2020 and I was in approach mode (minimums 827 set) with gear down and flaps 3 before FRS21 waypoint and FINAL APP worked fine

Got any examples I could try? I’ve done a few recently with no problems but I’m flitting between 2020 and 2024 so can’t remember which sim I’ve done what on

Version 1.1.4 on XBox - still getting the "the cockpit is ready for landing" announcement when climbing through 1000ft after takeoff

It is still a problem after SU16. Still need toggle glareshield and toggle pedestal lights buttons to get them to work

Removed

It's a WASM crash and the default inibuilds aircraft are very prone to it. The safest thing you can do is enter your approach routing while on the ground setting up the flight. At the very least, make sure you are several hundred miles away from the arrival airport when you do it

There is an issue with this aircraft on 2020 that they said would be fixed on the sim update and wasn't. If you spawn cold and dark, the glareshield lights are turned off by a button that doesn't exist in the cockpit. If you spawn on the runway, the dome and pedestal lights have the same issue. What you need to do is go into control settings and assign 2 buttons - "toggle glareshield lights" and "toggle pedestal lights". Now load in, turn up the light knobs and then press those buttons and voila, light

Correct. You need to have activated final approach on the MCDU PERF page and be in managed speed mode for FINAL APP to work

The passenger version on 2020 is very laggy so sim time passes very slowly compared to real time which would give you 1900ft in 60 seconds at 3000ft/min. If you look at the clock in the cockpit, you'll see that for every minute that passes in real life, only around 40 seconds pass on the sim On FS24, time can't lag as it is fixed to real time. So what you get instead is a horrific amount of stuttering that make it unflyable

Oh and wind import for descent is still being input upside down (top of descent wind as runway wind)

Hi. A300 now released on Xbox (1.1.6) but performance is absolutely horrific on SU2 which is tolerable for all other aircraft, including the a350. I’m cruising at FL340 and it’s a slideshow and has been since I loaded in. All seems to be working fine other than a slight niggle that the emergency exit lighting is set to “on” when you load cold and dark That and I thought for the £12 price tag that it might be the enhanced version but apparently not?

Hi. A300 now released on FS24 on Xbox (1.1.6) but performance is absolutely horrific on SU2 which is tolerable for all other aircraft, including the a350. I’m cruising at FL340 and it’s a slideshow and has been since I loaded in. All seems to be working fine other than a slight niggle that the emergency exit lighting is set to “on” when you load cold and dark

It's what is known as a WASM crash and they are very frustrating. Nothing you can do other than restart the flight which isn't too bad if you are just setting up at the gate but is horrible if you are setting up prior to top of descent

@BoeingSpeedbird it turns out that there is a workaround. If you go into control options and find "toggle glareshield lights" and "toggle pedestal lights" and assign keys to these, you can then load in, turn up the dials and then press these keys and the lights come to life

Almost a month on and still radio silence as is the case with anything that isn’t A350 related. I want my A300 passenger version back. How can it be so bad compared to the freighter when the freighter has a fully modelled cabin and the passenger version has nothing?

I’m giving this another bump as I was just on the inibuilds discord and noticed a chat about how this same problem exists in the A350. I’m guessing that it’s an issue with the fly by wire coding in all inibuilds aircraft that really needs sorted