Will other traffic, however sourced, still appear on the ND, do you know?
I’ve yet to have any issues, with Simbridge running, but have been doing relatively short flights. The problem with memory leaks is that their issues will probably become more noticeable, the longer the flight and the last thing you’ll need when 7-8 hours into a long haul flight is getting a CTD.
What a great airplane! I’m already super happy with the plane. It’s hard to believe that the A380 is still in alpha. I have already fallen in love with the plane. Thank you very much FBW.
True, but it is ALPHA and will be updated. Most that info you are looking for is on the bottom of the F-PLN and PERF pages:
The A380X is a great aircraft even in Beta.
I have been flying it and here is a YouTube video showing how it follows a Simbrief flightplan from KSEA to KPDX:
Right now I am flying from Heathrow (EGLL) to Cairo (HECA) in A British Airways livery. It is a 4 hour flight and very realistic and immersive on my 55 inch OLED screen.
KUDOS to the FBW team!
[Image is of Vatsim Radar at DXB with 30 some odd a380s departing, another 40 something arriving and all the gates are a380s]
PLEASE HELP- CANNOT STEER ON THE GROUND! I have no control over the nosewheel, the plane just turns to the right and goes in circles. Rudder, ailerons and elevator are all responsive to controls, just no steering…
I must be missing something. All other planes are fine. Honeycomb Alpha / Bravo, Thrustmaster Rudder Pedals.. Any advice appreciated!
P.S. Just assigned “Nosewheel Steering Axis” to rudder pedals, I see the nosewheel turn now, but still NO control of steering on takeoff…?
Anyone having a low recommended pitch trim setting on takeoff causes the plane to rotate on its own about 15 knots below V1?
I get a transponder is in standby message but had a quick look for the control to no avail. I see code entry on the RMU but what about mode. So how do you clear this message?
Thank you for this info! Disabling Simbridge on the flypad stopped the stuttering and allowed me to enjoy a much smoother experience! Hopefully the memory leak gets traced and patched soon! 
Maybe check your bindings.
For example, does your right brake axis have the wrong ‘reversed’ setting or have you got something odd going on with your rudder and/or tiller axis.
The rudder works visually as it does on all the planes. I could not find a “tiller” axis I found a “Nosewheel Steering Axis" which turns the nosewheel with the rudder pedals, but it still will not handle on the ground at all!
@SkyVagrant4490 I’m able to replicate my issue with the approach, mainly because I repeat the same flights a lot. Here’s the scenario EGLL R09L ILS09L transition LAM, star: LOGA2H. VNAV will take me down to 7000 ft at LAM, there is an altitude constraint at LAM of 7000ft and also according to the FMS at LAM30 of 7000ft and 6000ft by LA34A. (see image)
From the FMS flight plan the speed of the aircraft has been has already been automatically reduced to 190kts by this stage, right when I am facing a steep descent from LAM30 down to what should be 2500ft by FF09L. The FMS is I think indicating that it won’t ever get there? with anomalous target alt readings for all waypoints on final approach.
The aircraft can’t achieve a faster descent rate in VNAV, and certainly not at 190kts airspeed. Hence I’d either have had to descend ahead of LAM30 and ignore the alt restriction or jump in to try to manually control airspeed and V/S, as leaving it to VNAV, only results in a very slow descent rate (700ft/min) that misses the 2500ft approach height at FF09L entirely.
Trying to use speed brakes to increase descent rate at this point leads to being too close to alpha floor protection kicking in (which is worthy of another post entirely, but is a completely mad state to find yourself in and try to get out of again with this aircraft - think TOGA LK, an enforced 3000ft/min climb while completely stuck at alpha floor speed!, with no manual input by stick possible to reduce the pitch of the aircraft! ATHR disconnection only removes the TOGA LK, but still leaves the pitch uncontrollable even though they say the way out of A.FLOOR is to pitch the nose down manually. Seems like this is bugged maybe. 
I’m not to familiar with how this works on the A320 for example though.
The VNAV issue seems to be relate to late/steep descents, and the aircraft’s airspeed which the FMS has already reduced to 190kts quite far out. It is fine and works as expected with longer/shallower approaches eg into EDDF. It is fine if you resort to manual control of aircraft ahead of time or indeed ignore the constraints causing the steep descent ahead of turning onto final.
I guess I’m not sure if what I am seeing is down to me and this is normal behaviour, or if this aircraft being in alpha release and has a bugged VNAV on steep descents.
I had this happen to me, a couple of times and now tend to avoid too much use of the speedbrakes when descending, as part of a prevention-better-than-cure approach.
When I did get into Alpha-floor and then Toga Lock, the only thing I could do to get back control was to turn off both auto thrust and autopilot. Once the aircraft was back on an even keel, I switched them back on again. Unfortunately, that leaves you even higher and with a greater altitude to lose, so avoiding it is definitely the better approach.
It appears as though switching to open descent before deploying the speedbrakes might also be a plan, manually controlling the rate of descent with VS.
I’m glad it’s not just me! The A.FLOOR protection mode was wild. It forced the circraft into a climb to FL290 with TOGA LK enabled all while staying stuck at the low A.FLOOR speed! Not accepting manual pitch input to level off. It was off the charts level of bonkers. 
I may have to give that open descent mode a try and ignore the FMS controlled VNAV managed decent for now as it seems broken on steep approaches.
Also, have you noticed that VNAV even on descent before the star while it works always seems to over compensate v/s to reach the path, so it tends to overshoot then undershoot the ‘green dot’ a lot while targeting the vnav path. Again I’m not sure if this is just a symptom of it being an alpha release or not.
Had the FMC.1 screen go blank during flight yesterday. I was able to switch to the FO FMC.2 so FMC.1 was still working but the screen stayed blank for rest of flight.
Anyone else seen this?
Curious. Sorry i didn’t get a pic but it would just be a blank screen with all other displays working just fine so not terribly interesting.
I think expectations are exceeding reality. It is freeware and as explained by FBW is an alpha release. It was also explained that everyone should understand that it’s likely to be buggy and certain parts either not working or unavailable at present. Give it time and I am certain that we will have another excellent offering from this dedicated team.
You might need a fairly tall set of step ladders to use your wipes on the A380’s windshield. 
I actually quite like the “lived-in” feel of the A380, but I wonder if that might just be a feature of the default liveries and cleaner variants might be available at a later stage?
