Everything posted by Nick H
-
Update this week seems wonky
Hey, There was an update for the A306 for FS2020 this week (cw20) . The iniBuilds Manager doesn't show the latest version. However, upon installing the A306 becomes unusable. The mouse doesn't work, and I see the pilot/co-pilot. The EFB is not clickable, nothing is. How can I reverse this? nick
-
Difficulty to maintain directional control on approach and landing
Hey, I use the Airbus Thrustmaster Sidestick and read and followed the recommended sensitivity settings. But I find that on approach and landing, as the aircraft gets also slower, it tends to bank easily left and right, and it's really hard to maintain center line. The pitch up and down is a bit easier to control. Maybe this is correct behavior, I don't know. I am more looking for ideas and suggestions on how to maintain better directional control. I try to make small inputs, but maybe not small enough. 🙂 Also on lifting off, I almost always experience a roll behavior. -- nick
- CAB PRESSURE incorrect
-
Cabin Announcement Sounds
Hi, With the latest update, v.1.0.1, I now hear the cabin announcement super loud in the cockpit. In the OIS I turned down volume for announcements but it has no effect. I also deselected the PA/Intercom. This is super annoying when flying online.
-
Cabin altitude suddenly drops then increases on decent?
-
Flight director 1 disappears
Yes, I had the Pitch Trim 1 trip and the standby indicator rolled/failed. I reengaged Pitch Trim 1, but the standby indicator remained failed. I noticed a drop in fuel quantity, but the FD1 remained engaged I believe.
-
MCDU: PROG return out of ENG OUT mode?
Hello, On a recent flight, while step climbing from FL340 to FL360, my left engine suddenly shut down. It was not exactly clear why it did that, but I could relight the engine and continue. However, the PROG menu remained in the ENG OUT CRZ "mode." How do I return to the normal mode, i.e., not ENG OUT?
-
Autopilot lights not working during the day
Hi, I experienced the same with the latest version (v1.1.1), and it appeared to happen when there was a night/daylight transition. Turning the FCU brightness didn't resolve it.