Azlog

I'm on Xbox. The crash only happens when ending the flight or exiting to the menu after using any of the import functions on the MCDU. This includes init request to download the simbrief flight plan, and confirm T.O. data to move takeoff info from the EFB to the MCDU That's interesting that the 2 types work differently. Shame the Honeywells one is so clunky for entering direct waypoints but at least airways is slick

So I’ve put this in the A330 section as it’s where I noticed it but it applies to all as listed in the title Normally I would just use INIT REQUEST to do the flight plan for me from Simbrief but I recently found this to be the reason for the sim freezing when ending a flight so started doing it manually But manual entry felt really cumbersome. Airways are slick and easy to enter - it is happy for you to simply enter the airway numbers and it figures out where they join However when you have direct waypoints, it only lets you enter one at a time. You should be able to keep adding them but it insists on pressing INSERT after each one and gives you the error “Temporary Flight Plan Exists” Here’s a video of me doing both airways and direct to show what I mean. Could this possibly be fixed as it’s not right and works fine in the A300/310 https://www.xbox.com/play/media/hF2qrDMXu3 Thanks

I've noticed this as well that the A20N v2 just won't follow RNAV approaches on APP mode. It flies straight through the vertical path and doesn't descend. No issues before the last update that broke the cockpit lights

I just need to post here to say thank you to inibuilds for the incredible aircraft they have brought to FS24. Now that the sim has started to settle and stabilise on my Xbox series X, I’ve been able to get in the new A321LR and A330-300 and both are just incredible. The A330 is an absolute beast and feels so heavy - it really is a work of art. Can’t wait to chock up many hours in these, as well as of course the A350 when that releases. Job well done 👍

Sometimes the brightness is turned right down on it. Then it up using BRT button on side of tablet

There’s a knob on the TCAS panel bottom left that is turned to off - turn it to on by clicking it

I find it generally helps to be prepared well in advance in any airliner, especially if there is a tailwind on the approach as it can really cause you problems if you hit the glide slope a bit fast. The one thing that always catches me out with this aircraft is that as soon as GS becomes active, the speed changes to selected instead of staying on managed. Worse still is that the selected speed that it takes is the speed you were doing when it changes. So many times I’ve wondered why it’s not slowing down and then I realise that it’s set to maintain 180kts Best advice I can give is to try to be no more than S Speed in 15/15 when you catch the glide slope. It should be happy enough maintaining that until you get the gear down around 7 miles out and then the speed will drop off enough to do the next 2 stages of flaps before you are 1000 above

Bottom knob on transponder panel on left hand side. Turn it to on

Need to press autopilot disconnect twice - toggle autopilot won’t do it. There’s a red button on the stick to press

I had this happen to me once. It told me to set a pitch trim of something crazy like 1.5 and it was up in the air well before v1. Going to pay closer attention to the actual CG for setting pitch trim for takeoff as really wasn’t convinced about that one

Payload page on the tablet is the only way to add fuel. Can't do it from the world map or the fuel and payload window

On XBox Series X - dome light is the only cockpit light that works. Front panel lighting is non-existent. Side EFB area lighting is ok

The left tank feeds the APU. So when you have the APU running on the ground, it is using fuel from the left tank

The MCDU database pulls straight from the sim and I don't think the airport exists in the sim

I had this happen to me on the A300-600F PW version. It was was loading in with all of the lights turned on and TCAS Fail came up when I powered up properly. Nothing I did seemed to fix it so I disabled and deleted the rolling cache on the sim and that fixed it for me

You used to be able to arm RNAV approaches by being in ALT HLD mode and pressing profile. This would put P DES in blue under ALT on the PFD but now it flickers on blue and immediately goes away. I have to wait and press Profile at the exact moment that the VDEV diamond gets to the middle mark for RNAV to work. Is this a bug?

Also, uploading winds from the data page puts the winds in upside down and gives top of descent wind as the airport wind

Very happy with the latest A300 update but I've noticed a few things that would be worth looking into When you apply the load to the aircraft, it now places values on the INIT B page. But it seems to place the same values in to INIT B page every time (6.0 BLOCK, 96.4 ZFW, 27.0 ZFWCG) and these don't match up with what I have in simbrief and are showing on the EFB. Not sure if this is just on the PW A300F version or if common to others as have so far only flown this one ATC voices can't be heard (you know about this one) DHL livery on PW version is still a weird mess 😞

I've been flying the A20N v2 a lot and occasionally the PMDG 737-800 and these 2 aircraft have something in common that the A300 doesn't have. On the N1 gauge, there is an indicator on the outside edge that shows you were your physical throttle lever is in relation to where the current set power is. This is really handy for getting the physical throttle lever into the right position for disconnecting autothrottle and would be a great addition to this aircraft if that was possible. Disconnecting the autothrottle and then moving the throttle lever to try to find the right position can destabilise approaches quite easily and is a bit of a pain

To add to what @richboy2307 has said, different airlines use different calculations which they have worked out depending on what the airline requires. Some will be looking for minimum noise and engine wear (low Vr) while others might be looking for maximum climb performance (high Vr) but it doesn't mean the aircraft couldn't get airborne at lower speeds. So some might use the whole of a 3000m runway just to get off the ground at a relatively low speed. Others might decide that they want maximum climb performance, even from short runways and use low FLEX temps to get extra thrust. The calculator on the v2 EFB seems to like to use the whole runway when compared to the FBW version. Only potential flaw I've encountered in it is that it doesn't like to use low V1 speeds compared to the Vr speed which makes short runways return an UNABLE message. For example, you would never see on this EFB calculator a V1 of 104kt and a Vr of 134kt which I have seen and used on other calculators

Descent winds you get from the Simbrief pdf and put them in on the PROG page where there is a DES WINDS button (might be in fuel pred page which is accessed from PROG page - can't remember)

I have noticed among some of my friends who are flying this aircraft that they are reporting autopilot disconnecting during cruise. When we looked into it further, they were flying too high and too fast. This led to a very narrow safe speed envelope and so any slight changes in wind speed caused it to over or under speed resulting in the autopilot disconnection Only thing I have noticed is that the Vapp speed given in the MCDU is within a few knots of the orange section on the speed tape. If for any reason it dips into this orange section, the TOGA LK comes on and wrecks your approach. As such, I tend to add at least 5kts onto the Vapp speed

Autopilot randomly disconnecting during cruise is because of flying in too small a speed envelope. Ideally you want to be flying in the middle of a 40kt gap between overspeed and stall speed. I’ve seen people flying within 5kts of overspeed so the slightest gust and autopilot disconnects

RNAV works every time for me - I've probably only done 1 or 2 ILS approaches in the A300. There's a bit of a knack to it so best find some YouTube tutorials for it

That's the one. Haven't had a chance to try it yet but if it caused the cockpit to freeze then there could be an issue there than needs investigated. If you are in managed mode then yes it should follow the speed of the route - unless of course the speed of the route is less than your green dot speed which I'm guessing it wasn't