LukeFF

From A330 Driver's latest video:

Click the button next to the squawk code.

It's a known issue.

You almost certainly have a controller binding conflict somewhere. No one from the team is laughing at you. 🙂

Right now it looks like ATIS reports are coming from somewhere like VATSIM. This is very suboptimal, as the number of ATIS reports they have online at any one time is far less than those available through other sources. Tried KMEM and KTPA tonight and both came back with no information - even though it's easy enough to pull up their current ATIS reports from other sources.

As the title says - whenever you navigate away from the en route map and then go back to it, it's fully zoomed in as far as it can go.

As of the latest update, this is still an issue, as reported here - it skips over the part where it should say "Airbus":

Bumping this one up. It really looks silly seeing two GPUs when using GSX.

An ASL Livery for the PW freighter variant would be a nice addition. Right now we have just one and it's for the GE variant.

From the MS forums: https://forums.flightsimulator.com/t/inibuilds-airbus-a300-for-msfs/371370/346

Watch the YouTube video they posted yesterday to their channel. It explains it all. 🙂

Watch the video posted yesterday. It goes over all of this. 🙂

This bug was reported as fixed in the latest update, but I still cannot change the altimeter setting in the EFB from hPa to inHg:

When using GSX, I have both the GPU as provided by GSX and the one that comes with the A300, at the parking stand. Is there a way to remove the GSX one so only the A300 one is rendered?

This was with an FSLTL-inserted plane:

Huh, that is really weird. Not that I'm trying to change anything, but I was just curious what sort of parameters had been set for the cargo area.

In the screenshot below, the Agent 1 and Agent 2 switches can be moved up and down without moving the red guards out of the way first.

I just noticed the A310 manual is twice as long as the A300 manual because the former has the (very helpful) expanded procedures checklist but the latter does not. Whenever a manual revision is done, could this please be added?

Bump! 🙂

It was with the default GSX profile that can be downloaded through the iniManger app (the full-detail one, not the "lite" version). The error message showed up in the cargo area, namely in the ramp spaces marked 601-609 (can't remember the exact one, but it was one of those).

When opening up the GSX editor, I see an error message about "parkings not being found in navdata."

West of Terminal 2B, this parking garage has trees growing through it. Also, the signage for it is very low-res:

It remembers tire, oil, and brake status but not where you landed. Little NavMap is helpful for that.

That's up to Microsoft.

The north cargo parking area - where FedEx parks - is extremely dark at night. It needs a lot more lighting intensity.