Frustration.

[dc10boy]

On 7-11 you released V1.1.2 of the A300. For a pretty large number of us, and even new users this update brought with it renewed WASM crashes and The loss of all voice ATC ( a basic MSFS function). Reports of this were coming in by 7-19, and by 8-7 you knew what was causing it as Vrishabh posted "This issue is specific to the A300, due to the XML rewrite of all the switches in that plane as part of the performance optimization." 
On 8-22 he posted
"We are still committed to releasing a fix for this ASAP so you won't have to wait till the next "big" update. However until then, while we understand it may be frustrating or inconvenient, you can still make a flight with the default ATC by reading the text replies, albeit you may not have audio feedback for the interaction. This issue also does not manifest on all installations, as verified via internal testing.

You are free to disagree, but from our point of view, as the default ATC is not completely disabled, nor the plane completely unflyable in such instances, the grounding/not using the plane at all as such is entirely a user choice.

In any case, we appreciate the importance of this feature to some users, and a fix for this is still quite high up on the priority list as far as the A300 is concerned. At the same time, the team is also working very hard on delivering the other updates & products showcased during the Summer Surprises events, as such we would appreciate all your patience & understanding on this matter. 🙏

As at this time there is nothing more to add to this conversation, I will lock this thread. We have acknowledged the bug and re-iterated that a fix will be coming in due course."

Great. Text ATC, no audio, flying in radio silence, that's if you can get the thing to complete a flight without a WASM crash. It's not a good look to lock the threads referencing a major bug, as well as all subsequent reports from newer users with a "known bug" explanation. We're a couple of days away from November, and all we have heard from Ini is product updates (for other products) and your own explanation that you are working on other things. If you have no plans to take us A300 customers off of the back burner, I respectfully request that you allow users that are having issues with the update released in July, the ability to roll back and run v1.1.1, which worked well for a number of us.
Thank you.

Edited October 28 by dc10boy

[S.Sabel]

+1

Thanks for your post!

I was about to ask about the great “ASAP” update myself these days. After more than three months / a quarter of a year, you can probably ask again without it looking like constant nagging for the moderator or the manufacturer...

I wouldn't care about the ATC voice function, which hasn't worked for 3 months now, if I were flying via IVAO, VATSIM or another network, but I fly offline and really want to use the familiar standard functions that also work in all other aircraft, whether vanilla, add-on or mod, thank you!

[dc10boy]

So, I just received yet another Email from Inibuilds showcasing all the OTHER products they are working on. The "flagship product" A300 will be "Compatible" with MSFS2024 with "Outstanding bugs from MSFS 2020 fixed" Awesome. You're on top of things for MSFS 2024. When will these issues be fixed for us MSFS 2020 users, who bought this aircraft for that sim, be fixed?