Azlog

Saying this though it maybe does feel better. But on approach you need to be very organised and not follow the close deceleration procedure (intercept glide slope at flaps 1 and S speed) as it just won’t slow down enough to get configured for landing. Is it maybe more that the gear and/or flaps aren’t producing as much drag as they should?

Rudder trim doesn’t appear to work either. The switch moves in the cockpit but the shortcut keys I set for it don’t do anything and the digital display beside the switch doesn’t change value from 00

Also wondering about taxiing. When sitting at idle with both engines running, the aircraft will easily get up past 30kts and so you are having to constantly use the brakes. Is this right? I know it should move on idle but this seems a bit excessive

Couple more things: Didn’t follow DME arc and just went straight ahead (EGPE ILS RW5 approach). Will try some other ones Position Bearing Distance entries not working Speed brakes still not doing much in flight. Was on a real one a few weeks ago and when they deployed the speed brakes in flight you felt yourself shift forward in your seat as soon as they went up but a down arrow on the speed tape barely appears and takes a while to do so

Did a flight last night in latest update: Landing lights much better - can actually see the runway now Manual entry of VORs working Noise in cockpit much better MCDU now inputs a really random CoG if you don’t enter in manually Takeoff roll feels better I think (either that or I’m getting used to it) but I have 1 comment for landing. In the real Airbus, the aircraft starts trimming down at 50ft to encourage the pilot to initiate the flare at 30ft but the sim version doesn’t do this. This means that 30ft is too high to start flaring and it’s possibly what’s making a lot of people float so badly. Would it be possible to add this feature?

You need to use your pilot ID in the neo which is a 6 number ID that you’ll find in your simbrief account settings. On the EFB for that, you need to use the EFB keyboard and not the Xbox keyboard or it won’t work. haven’t tried the A300 yet due to WASM issues on beta

Also got this problem on Xbox

Yeah it really doesn’t like to slow down during flight

Enjoying this aircraft. It followed ILS and RNAV approaches perfectly. Hold function works great as well and the ground steering feels really good. Have noticed a few things though … Can’t input VORs manually in MCDU MCDU inputs wrong cg (gwcg instead of zfwcg) when taking from EFB Landing lights could be brighter Cockpit wind noise really overpowering Aircraft feels very heavy to rotate at vr, especially in flex. A300 you give a slight bit of back pressure and up it goes whereas this needs a very aggressive and prolonged input to get it in the air Floats better than a boat on landing Not always getting correct ILS in MCDU after selecting ILS arrival. Tenerife south (GCTS) runway frequencies are the wrong way around and Leipzig 26L (EDDP) is just random. Getting code from charts and putting that into rad nav page works to fix it in both instances

The buttons either side of the display screen on the MCDU

I found that if you hit the soft key beside weight/cg it takes the wrong cg from the EFB. It should use zfwcg but instead uses gwcg also the takeoff calculator is wrong, often giving relatively high speeds as well as a v1 = vr. I left Gibraltar earlier and had to use an online calculator as the EFB told me the runway was too short. Online gave me a v1 of 106kts and vr of 134kts on flaps 2 which worked aside from the usual issue that the aircraft doesn’t want to lift off the ground for some reason on the subject of flaps 2 takeoff, I entered 2/1.1up onto the MCDU but the checklist went green when I got to 1+F flaps. Surely it should have stayed blue until I selected 2 to match the MCDU?

My understanding was that it won't come out on the beta as there isn't enough time left for that with the update coming in less than 2 weeks and it will just wait until then - but I'd love to be mistaken so I could put it through its paces

Great presentation on the A320Neo on yesterday's livestream. Hugely looking forward to flying this aircraft - the Xbox has sorely needed a high fidelity modern Airbus for way too long and it's finally almost here

I'm also on xbox with version 1.0.9 and my EFB looks exactly as pictured above. Hasn't updated as it maybe should have. It also doesn't save any settings that I change

Have you correctly entered the thrust reduction altitudes in the takeoff page? I found they are defaulting to the airport altitude when they should be 1000 above

Ok so I’ve noticed 2 things on reviewing Profile was disengaging somewhere between me setting it and getting to the runway. Not sure what was happening but if I engage NAV and then Profile when I’m taxiing then it stays on and works fine Thrust reduction altitudes look as though they set by the EFB but they aren’t. I set up a flight from EHAM and I noticed that they all said -12. Changed them all to 1000 and the engine management system flicked over from flex to auto as expected The EFB doesn’t seem to be saving my settings. Every time I load in it changed auto filler disconnect to yes and resets the thrust reduction altitude to 1500.

Happy with the fixes for the Xbox version but got a few points: Passenger version still unflyable due to lag Engine management system doesn’t change to Auto at thrust reduction altitude when doing a FLEX takeoff Pressing TOGA on the runway for takeoff starts a very slow engine spool up that means full power isn’t achieved until you are most of the way down the runway. Is only happening on first takeoff after loading in. I did a multi leg trip and didn’t have it at the second or third takeoff Chocks toggle in EFB is inverted - turning them on takes them off

Have you gone into the EFB and done throttle calibration? There’s plenty of reasons why the update need to hurry up and arrive on Xbox but throttle isn’t one one of the reasons I’ve come across

Seconding this in the hope that nav gets fixed at least

So I just tried my theory again of changing the SID or STAR while taxiing and during the flight and it didn’t kill NAV. However weather at Heathrow today is pretty challenging and I had to do a go around. Go around procedure had a manual discontinuity so I use direct to in order to skip it back to BNN waypoint for doing the approach again and immediately the aircraft did the classic 10 degree bank to the left and wouldn’t follow the route

I should probably have clarified that I’m on Xbox. I forget that the builds of the aircraft are different between the two platforms

I might have stumbled upon the cause of the issue surrounding the A300 not following NAV. Need to do more testing but thought I’d put this out there now If you enter your flight plan including the SID and STAR but then change either of those in any way, the flight plan will get stuck. So let’s say you were thinking of taking off from one runway and programmed that but the tower told you a different one. You decide to change to the one they told you in your flight plan and boom - there goes your nav for the flight. Or perhaps you had an approach in mind for your arrival and programmed it early but then the weather changes or you change your mind enroute and decide to do an ILS instead of an RNAV and change it in your flight plan. Suddenly the aircraft is still on NAV but it just keeps going on the heading you were on and doesn’t register passing waypoints Am I onto something?

Also in the air

Yeah I’m not quite sure how it is done in real life as normally on an ILS you’d want 180kts at more than 8 miles out, 160kts between 8 and 4 miles out and then final approach speed at less than 4 miles out but RNAV doesn’t really allow for that. Or at least not in the A300/A310. In the A320 RNAV works the same as ILS in that you just press the approach button and don’t think it matters if not fully configured Could be the order you are doing it. I always think level hold, final 3.0, profile and it works almost every time. Had a couple where I’ve had interpreted the chart wrongly and had to descend further before trying again but it always gets there eventually. Since getting the A300, I’ve been doing quite a few cargo ops routes in the US which involves a lot of airports with RNAV approaches You probably could disengage auto throttle and it might still work manually. I’ve never tried it as I normally keep auto throttle on until around 400ft to avoid chasing around trying to find where the throttle was set which can very quickly destabilise the approach

I feel that it’s also worth mentioning that the speed it gives you should be the speed you should use unless the headwind component exceeds 10kts (in which case, add half the headwind component minus 5. So 16kt headwind, add 3) or it is gusty (in which case, half of headwind before and all of gust. So 16kt headwind gusting to 20kt you would add 7) but no more than 15kt addition I think it is. The reason for the speed it gives is to allow the aircraft to sink gently down onto the runway when you reach 5ft after idling the throttles at 20ft or so. If you come in too fast, you’ll just float down the runway and touch down far too late and/or hit it hard