Alexair

I concur, uninstall/reinstall fixed it. Regular updating doesn't...

Thanks, but unfortunately the problem isn't solved. I did a full desinstall and a full reinstall and still have the same covers in place issue.

Known issue being investigated. They working on a fix. In the meantime, remove the maintenance option and you'll be fine...

Thanks a lot for your effort to being more reactive, very much appreciated !

Yes, I agree. They really should be more proactive. Doesn't incline me to purchase more stuff from them unfortunately. And some of their answers to justify not correcting things make no sense at all, especially when users are providing near perfect solutions. Let's wait and see...

Same here, as well as for bunch of people. Inibuild team is working on it but, as usual, it will take a loonnnggggg time to get a fix... In the meantime, I've opted for removing the maintenance option.

Please disregard this post and delete it. I've finally found the culprit, nothing to do with the A300... Sorry !

and got same issue not only with the A300 but with all MSFS aircraft as well and VATSIM !

Dear all, After the recent update I cannot hear ANY ATC in VATSIM in ALL aircraft I have in MSFS. I thought it was only in the A300 as others have already reported, but on my side VATSIM ATC reception doesn't work at all now for all aircraft.

Got same issue too...

+1 !!!

It's type specific, not livery specific, so anything that will happen on your American PAX model, will happen to all PAX model but not to the FREIGHTER model.

There is really no "normal" CI used in any aircraft. CI change very often and in real life, even when the release give you a CI (the "release" is the real name given to the equivalent of simbrief FPL), it is not very often used. Most of the time the capt is using whatever CI is more convenient for the flight or to him (is the flight late, is it a go-home day, is he flying a super-critical line (ie: making more money for him), etc.), sometime we don't even use CI at all, but either FLC or VS with speed/Mach. At least that's what we do in real life in US (same for Airbus or Boeing).

You're right, known issue, hopefully they will fix it...

Just to be sure you're using the right GSX profile, you can remove the GSX that is currently in your virtuali folder and get the one from the A300R folder and put it in the virtuali folder instead. Give it a try, maybe that's your problem as on my side the pax profile work fine.