Azlog

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

Think you need to activate it as I said - but it's been a while since I tried one and not sure actually if I've done one in the v2. Will need to give it a go later

IRPOD is the first waypoint on the ILS/LOC approach. An RNAV without a transition would perhaps default to that as the straight in waypoint in the absence of a VIA New cruise altitude happens if you set an altitude on autopilot panel that is higher than the cruise altitude that was set on the INIT page

As for the second point, I'm not on the sim right now but you need to press the top left soft key on the MCDU and then it's something to do with activating alternate. This will put a discontinuity in and have your alternate airport under it for you to set up the route and approach. The blue lines after LPMA is the missed approach procedure and become active when you overfly the runway without landing

I have noticed this as well but when I come to think of it, I think I forgot about it when I made a list of issues I had encountered. So +1 for this. Only way to exit a hold that I can find at the moment is to use direct to which doesn't seem right

Further to the Luton departure issue, MATC3B works but MATC3Y doesn’t. MATC3Y has a waypoint right next to the altitude constraint waypoint and so when you get to the altitude one, you are already within a mile of the first RNAV waypoint which means it can’t then move on itself

I changed my units in simbrief to kg and passenger number now loads in correctly. Strange and fuel and cargo were unaffected but passenger reduced as though the number in simbrief was measured in lb and in the aircraft converted the number of passengers to kg

Looking at it I see there is also a MAT3B departure that doesn’t have that initial 1 mile waypoint. I’ll need to see if that is listed in the MCDU and give it a go to see how it compares

It was enroute to Channia. VOR Y rwy 29. The DME 05 waypoint was in the wrong place so I thought I’d try to move it to the right position. I entered created a PBD waypoint and added it into my flight plan in the hope of replacing the DME05 waypoint that was in the wrong place. This worked but I then tried to delete the out of place waypoint in the same edit session as entering the new waypoint and it froze For the Luton departure, I did it again paying close attention and noticed that the first waypoint (an altitude constraint) is very close to the first chart waypoint GWS01. It passes the altitude waypoint but then gets stuck on the GWS01 waypoint as though it needs to be more than a mile away from a waypoint in order to then move to the next one once it gets within a mile of it I will check my units and see if something is up there. Fuel and cargo transfer perfectly every time but passengers don’t

Also for some reason when I download my payload from simbrief it gives me less than half the passengers that were listed. Recent flight I had 125 passengers but payload download only gave me 57. Using inibuilds template on simbrief

noticed flying out of London Luton runway 25 on the MATC3Y departure that it just wouldn’t follow it. Flew through the first waypoint but it didn’t move onto the next one and proceeded to try to turn back to it until I used direct to in order to get rid of it. Tried twice and failed both times

@richboy2307thanks for the feedback figured out how to do PBD waypoints by using the data page but when I tried to insert one the cockpit froze up Also figured out how to do fix radius and lines which is cool but they only served to show that something weird is going on the DME arcs generally. Is this a sim issue rather than the aircraft? See attached screenshots. I drew a 12 mile circle and the flight plan definitely doesn’t follow it. Still feel like the v2 should be able to follow DME arcs as the A300 and A310 do it flawlessly but the v2 just flew straight through D14 kept going straight till I took over manually

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