KorEl

Something that has to be fixed: The start sequence procedure is wrong as it is now, the HPC should be off and set to ON after the starter is engaged and RPM reaches 1200-1500 This is a page from the training manual:

This is correct, see the page from the training manual:

The audio panel works, what it is not working is the volume control on the freq selector. If you try maybe you can hear the morse code, it is very weak as it is now .

-Please add a clock to the instrument panel!

Yes, a complete uninstall/reinstall fixed it, thanks.

In my inimanager it is 1.1.5 updated 29 Jan (FS2020). I deleted the "inibuilds-aircraft-a300-600" folder but problem remains.

Same here, problem remains.

Any plans for the A330 to be available for MSFS 2020? Many people do not plan to upgrade to 2024 (personally not for the next 12-16 months)

I recently did some flights from high alt airports like Bogota and realized that the EFB take off calculations were wrong. It seems that high alt it is not taken into account resulting in power and speed settings much lower than those required. Can you please cheek?

Yes, most probably that was the cause. I deleted it too when the FBW A320 displayed a warning about it. Never thought this may be the problem for the A300 but it seems it was.

After further investigation: I changed my maintenance option from "realistic" to "disabled" and the symptom was reversed, it started pulling to the left. That means something was corrupt with the maintenance function. To be sure I deleted all contents inside the "work" folder (content is recreated next time the A300 will load, it is located at "C:\Users\username\AppData\Roaming\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a300-600" for steam) and that fixed it -permanently I believe... 🙂

Unfortunately for me the B738 does not fix it permanently, every time the sim restarts, i have to do the same procedure again and load the 738 first, otherwise the A300 continues to pull to the right. Very strange indeed!

Can be done from "options"

I had exactly the same. I loaded the pmdg 737 for comparison to check if it is a controller problem and it was not. I reloaded the A300 and everything was OK. Maybe the A300 was not compiled correctly initially (?)

This is correct according to v1.1.2 update log: Fixed - ILS freq selection: Only ILS freqs should be avail – uneven after “.” E.g.10/15/30/35…) .20/40/60 are not valid ILS freqs [Feedback from real A300 pilot]