Andrew Miller

Might be worth trying this with an LOC approach to see if the behavior is identical. Not sure if it’s correct or not, but that would at least establish whether this is an LDA-specific issue. An LDA should be handled the same as an ILS or LOC approach (depending on whether it has a glide slope or not), but I know of at least one other addon that doesn’t handle them properly, so it’s possible something needs to be fixed here, too.

Very excited about the new release! Two questions: 1) When switching between old and new winglet types on the 359, does this only change the winglets themselves, or the entire wing? My understanding is that when the new winglets were introduced, there were also some changes made to the wing design itself, adding more twist. Both of these combined contributed to improved aerodynamics and an increase in range. Also, do the flight model and fuel burn profile account for different wing and winglet types? 2) Have the Variable Camber and Differential Flaps Systems been modeled? They deploy small amounts of flaps during cruise to adjust the center of lift in order to reduce drag and increase efficiency. These systems were added in lieu of using trim tanks. If these systems are not modeled, is the impact to fuel burn reflected, and do we need to make any corresponding adjustments to our fuel planning? Thanks!

On the first livestream, there was discussion about how the A350 eliminated the use of trim tanks to manage CG during cruise as fuel is burned off. I know the real a/c instead has the Variable Camber (VC) and Differential Flaps Setting (DFS) systems, which manage CG by selectively deploying small amounts of flaps during cruise. However, I didn’t hear any mention of these systems during the livestream, or notice those systems in operation during the short demo flight. Will the ini A350 have these systems modeled? It seems like an important thing to include, in order to have an accurate flight model and get accurate fuel burn figures. Thanks!

Hello! I took off from RWY 22R yesterday, which has a very long displaced threshold. I was using the default ATC. When I pulled up to the hold short point on taxiway E, there was no option to request takeoff clearance. I had to pull onto the runway and taxi all the way past the threshold before the sim recognized that I was near the runway and gave me the option to request takeoff clearance. I was flying the PMDG 777 at the time, and I noticed that the TORA displayed on the EFB performance calculator (which reads runway length data from the sim) was much shorter than the actual runway length—it corresponded roughly with the intersection with taxiway G, a fair ways past the displaced threshold, at roughly the midpoint of the full runway. The default ATC gave me taxi instructions to enter the runway at G, as well (which I ignored). It seems the sim doesn’t recognize that RWY 22R exists at any point behind taxiway G. I noticed a similar problem with RWY 13R a few weeks ago—the sim gave me taxi instructions for the displaced threshold, not the runway end, as expected.

Sorry for the delay! Had a busy week and didn’t get a chance to use the sim till today. I just tried again and had the same result. This was at KMIA instead of KSNA, and I was using the pax version instead of the cargo version, but I followed the same process: THR RED altitude set to 1500 AGL, ACCEL altitude set to 3000 AGL. At 1500’ the a/c maintained V2+20, but the TRP stayed in AUTO/FLEX mode instead of switching to CL. At 3000’, the TRP switched to CL and the a/c accelerated to 250 kts. Hope that’s helpful—let me know if I should try anything else! Also, I updated to v1.0.2 before this latest flight.

Hi! No, not yet, I should be able to test it tomorrow, though. I’ll report back!

Just tried an NADP1 takeoff out of KSNA, but it was unsuccessful. When entering my v speeds before departure, I changed the Thrust Reduction height to 800' AGL and the Acceleration height to 3000' AGL. Took off with Profile mode activated on the FCP. At 800 ft, the TRP did not switch from Flex to Climb mode. I tried to manually force it by first changing the TRP mode to "auto", which did nothing, then to "CL". This reduced the thrust, but it also overrode my acceleration height and the nose went down to accelerate to 250 kts. I can try it again another time to see if I can reproduce it, but I'm curious if anyone else has encountered the same problem. It seems like the TRP is following whatever's set in the EFB, not what's being entered into the FMS (FMGC?).

That's because KRNO's runway designations recently changed, but it hasn't been updated in the sim, so the latest navdata has all of the procedures pointing to runways that don't exist in the sim. All of the SIDs/STARs point to runways 17L/35R & 17R/35L, but the sim still calls those runways 16L/34R & 16R/34L.

Hm, interesting…well, at least I know I’m using the right key bindings! I’ll take a look at it again and see if there’s a problem with my controller. Thanks for the response!

Hello, I use a HOTAS controller that doesn’t have a separate flaps lever, so I’ve assigned two buttons on the throttle quadrant to the “increase flaps” and “decrease flaps” commands in MSFS. On every other a/c I’ve flown in MSFS, these commands will set the flaps lever in increments of +/-1, but on the A310 these commands don’t do anything—I have to use my mouse to manually move the flaps lever. Is there something I’m doing wrong with my controls setup? Thanks!