Azlog

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

RNAV - so I thought it was working but it isn’t. Instead of arming in blue, it is now immediately turning green and beginning the descent path angle from the exact point that it activated. Has almost killed my virtual self twice now so definitely not pilot error

Exactly how it is for me. APP NAV and FINAL in blue should change to FINAL APP in green and follow the purple rectangle but it doesn’t. Also got a problem with the A300 RNAV since the last update but that is for a different thread

The FD/FPV switch also moves the wrong direction WX worked fine for me the other night flying into East Midlands during storm Eowyn. Although that also reminds me: SYS switch for weather radar also moves the wrong way

Landing went well. Couldn’t really test the RNAV arming due to the continuous descent approach I was flying but all worked well Performance was good flying between KLAX and KSEA which are both handcrafted airports Still getting WASM crash (yikes turned fully left) on loading in 2024 but at least the character now stands beside the aircraft instead of being stuck under it as it was before - or maybe that’s the beta

Landing calculator is good for MANUAL and AUTO MED braking for having 15/20 vs 30/40 shown the correct way around but AUTO LOW still gives longer landing distances for 30/40 than it does for 15/20

When I listed the lights, I missed that landing lights are also inverted

So happy to finally have the update released on Xbox. Noticed a few things though while setting up for a flight: Nav lights, no smoking and elapsed time switches are all inverted (on is off etc) Cost index and FLT ID no longer import from simbrief (minor issue) Wind import is gone (guessing intentional?) Got an RNAV approach lined up for landing in a couple of hours so will see how that goes. ATC voices are working which is nice

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

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

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