LukeFF

Next to the loudspeaker knob on both sides of the cockpit, there is a 3-position switch that controls the lighting of the console. Around the time the new radio stack was released, a bug was introduced where this light is now on by default. I'll try to take a screenshot later on. Regarding the heading knob, yes, it was my misunderstanding.

When requesting winds, the resulting output is still borked like it is/was in 2020

The sound for the red AP disconnect button on the yoke has no sound right now.

Two things I noticed tonight: The "push to sync" the heading knob is reversed (it's now pull to sync) The console flood lights are on at the beginning of every flight (originally reported as an issue with the 2020 version)

No

I'll try that when I get a chance, thanks.

Nope, no dice. I tried for instance "Parking Brake On" and "Parking Brake Off", with a clean controller profile, and nothing happened.

Alright, I'll give it another try when I can.

It might be because the knobs aren't animated - I tried the default inputs (i.e., those not created by a third-party profile), and those work fine, although the knobs will not rotate.

All of those commands are in the default MSFS commands menu but none of them actually do anything in the A300.

There are a few sets of default commands that do not work with the plane: - Beacon Light On / Beacon Light Off - Taxi Light On / Taxi Light Off - Parking Brake On / Parking Brake Off

Two things: 1. It seems the APU can run indefinitely with one of the fuel pumps running. That doesn't seem right 2. Internal temperature display: is the cabin temperature supposed to be shown on the CRT screen when the rotary knob is set to something other than "CRT"?

WASM is a code format used in MSFS for a number of planes. Unfortunately it turns the A300 into a plane that may be rendered unusable at any moment.

I don't know if it's me, but I'll try to explain it the best I can: ILS landing, had to perform a go-around. Raised flaps and gear, trigger the TOGA button, set my new altitude to 5000 feet. Plane instead goes into warp drive, over 400 knots, 7000-plus feet per minute. Autopilot and autothrust were enabled. Even when I tried altitude hold or manually setting the vertical speed to -1000 fpm to try to get the thing to stop climbing, it just kept going and going to about 10000 feet. It was just unresponsive to any sort of altitude changes. Finally somehow it leveled off and started descending, and we got back down to where we needed to be. Unfortunately I had to fly another go-around, and the same thing happened again. At this point I just had enough and shut the thing down. Did I do something wrong in my procedures here that would cause such a thing?

Okay, now it's working - the cockpit door has to be open to be able to hear it (PW freighter).