LukeFF

From what I have read and have seen in my experience, the tire wear rate is exaggerated right now. After about 10(!) landings my tires were already in the red zone, and it's not as if I'd had any hard landings in that process. Perhaps with "normal" usage the tires should be in the green up to about 33 landings, yellow after 66, and red after 100?

Don't get me wrong, I really learned a lot about the A300 from A330 Driver's videos, but this guy also does a great job at explaining things, from start to finish: His checklist can be found here: https://flightsim.to/file/66539/a300-full-sop-checklist

Looking at the tires on my plane today, I noticed the lettering and numbering are reversed: .

Yes, but there are jumpseats that can be filled.

In the passenger section for the A30F on Simbrief, the options are Auto, None, and Full (0). Why does that last option say Zero for a full load?

When receiving taxi information, altitude assignments, transponder info, etc, it would be cool to have a virtual notepad we could bring up to write down that information.

On a related note, what effect(s) do worn tires have on the plane's performance? Braking efficiency?

As the subject heading says: when attempting to park at the NE parking area, all 4 positions are marked as "too small" for the A300. Beyond that, there are a lot of other places at the airport marked as too small by GSX that probably can fit the A300 just fine. Related to the first issue - when unloading cargo at NE parking, the unloading process gets stuck at 67%.

In the DHL parking area, there are some floating containers:

Also, to add: what finally worked to get the thing out of the climb was to disengage auto-throttle. Only then did the plane start descending like I wanted it to.

@Nico - Gumby, I take that back - I am trying an approach into KMEM right now, and the damn plane won't descend properly to the approach and is now climbing instead of descending. Something is seriously screwed up - no matter if try level change, vertical speed, etc, it's stuck in a climb.

When the ATC tells an AI plane to report the player's plane is or is not in sight, the AI will not verbalize the "Airbus" part of the message. It will instead say "have the in sight."

I haven't seen in it a while, no.

I'm good for the moment, now, thanks. 🙂

It has been my experience during my last few flights to and from KLAX and KPHX that certain numeric readouts on the bottom left-hand corner of the PFD will flash on and off during the final approach phase, as if they are fighting to be visible at the same time. This always happens after capturing the ILS and engaging LAND mode.

@Nico - Gumby, I am good to go now, thanks!

Thanks, will give that a try. 👍

Perfect, thank you for that. All is working as it should.

Got it, thanks. 👍 Yes, I've used it as mapped in the sim and found it to work flawlessly.

Speaking of which, I tried to map the "hold reverse thrust" in AAO last night but I could not get it to work - it would only work by pressing and releasing the button on my controller (I tried the two reverse thrust commands but ended up with the same result). Is there something I'm mapping incorrectly here?

In the MSFS Input Events list, what controls the autopilot 1 and 2 switches? AIRLINER_AP_Switch_1 and AIRLINER_AP_Switch_2 seem to be non-functional.

Thanks 🙂

I'm using Axis and Oh's, so what should I use?

Do I need to map both of those to a button or will the first one do the job?

Wait, no I did not. 😞 So, I'm trying to map my Virpil Control panel to the three gear positions, but nothing is responding. Are these the correct commands? INI_GEAR1_POSITION INI_GEAR2_POSITION INI_GEAR3_POSITION