Azlog

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

Giving this a bump. The A20N has the same issue. Last week I flew an A320 in a full size training simulator and there is a quite a significant difference in the handling on the roll axis. Nice and smooth compared to the sim where small movements are difficult to make

Pretty much all of the 3 way switches in the cockpit are reversed since the last update. And the passenger version is now unflyable due to heavy stuttering. Used to love this aircraft but every time they fix a bug they introduce a load more and now I haven't flown it in months. And that's not to mention that it was supposed to be day 1 compatible with FS24 and here we are almost 6 months on and it still doesn't work 😞

This was brought up in a previous topic but the topic suddenly got sidetracked onto the A400 and closed. But it’s still an issue so I want to raise it I have a great many hours in the A300 on the sim which the A330 was the replacement for. As such, it was meant to feel very similar. But the issue is that it doesn’t and to be specific, it is very hard to hold the centreline/localiser on final due to what feels like a dead zone in the roll axis control. I am using a Thrustmaster Hotas One and my friends who also flies the A300 and A330 on the sim uses the TCA Captains Pack But we both agree that the aircraft has a dead zone making it go from nothing to a large response - small changes to the aircraft’s roll position are impossible to do, especially on final. I’m not sure what his sensitivity settings are but I fly completely linear with a small 3% dead zone to prevent unintentional inputs Is this something that could be looked into?

Cruising along quite happily, I leave it flying to go and do some other stuff. But when I come back, it's flying in circles at FL400 in TOGA with the cavalry charge blaring. Sound familiar to anyone? Well I believe this is a feature rather than a bug but still one that perhaps needs to be addressed. In the real A320, if the speed suddenly goes outside of the safe band and into the red, this will cause autopilot to disconnect immediately. And this is fair enough as it means that something has gone wrong. But in MSFS, more often than not it simply means that the live weather has updated and the wind has changed direction So would it be possible to add a delay to this disconnect happening on the sim so that wind direction changes don't cause an autopilot disconnect and ruin our AFK flights? It only happens on inibuilds aircraft so I suspect that this is either something that other developers have accounted for, or the A320 family flies much closer to the red band than most other aircraft. I tend to fly relatively low to counter it but I shouldn't really need to and it still happens some of the time

With the most recent update, the ability to request winds in the MENU page is back however it gets it wrong. Load a simbrief flight plan on XBox series X on the latest release of the A300 and complete the setup of the aircraft. Go into the descent forecast and you'll see that the data is upside down with the airport winds being the top of descent winds and the top of descent wind being the airport wind

Left hand logo light points the wrong direction when viewed from some directions/orientations. SU1 beta .22 build

On sim update 1 beta .22 build I have had 2 avionics freeze events when entering the arrival. Selected the arrival runway and went to select the arrival STAR and all of the avionics froze up. The first time it happened I was on the ground so I restarted the flight and it worked fine when I tried again. The second time I was en-route so had to just end the flight. A330-300GE. Xbox Series X

I've only had this happen once and I saw what happened. The wind in the sim suddenly changed pushing the speed up into the red overspeed area. This prompted the autopilot to disengage and the flight directors to turn off

Yeah I absolutely love flying it. Is really well done and works well - just got a few bugs that need squashed: descent winds import, 3-way cockpit switches and ATC sounds mostly

Yeah these issues were introduced in the last update. Hopefully will be resolved soon though haven’t had any feedback yet to my post where I raised these issues

Descent winds are being imported again but they are upside down as they were before

I haven't tried that yet - the flight I did was flat terrain both ends

Light switches still broken (inverted) reading light appears on but turned to zero when starting cold and dark emergency exit lights on when starting cold and dark ATC voices now very distorted - see video On the plus side, RNAV worked perfectly https://www.xbox.com/play/media/ZkeAvzGxZS

I find that the approach speed set by the MCDU in this aircraft is too close to the stall speed. This means that small gusts can trigger a stall disconnecting the autopilot and triggering the alpha floor (TOGA LK). If you use the performance calculator in simbrief, it will always give a Vapp that is 6kts higher than what the aircraft says it should be. As such, I always go into the PERF page and change the Vapp to a value 6kts higher than what it says. So if it has Vapp of 128kts, I set 134kts and that removes the issue Not sure on your second point. Are you using sim rate? The v2 doesn't like sim rate very much and it struggles to stay on track