Esa Ahonen

In the following file (of course the drive may vary too, depending how your system is setup): C:\Users\[youraccount]\AppData\Local\MobiFlight\MobiFlight Connector\Scripts\ScriptMappings.json Change the following line: "AircraftIdSnippet": "A300", To: "AircraftIdSnippet": "a300", I reported the solution to Mobiflight a good while ago but it hasn't so far been included in update. NB: If you update Mobiflight, and they haven't included the fix yet, you have to do the edit again. Edit: it will of course have the errors reported above. I'm really hoping Inibuilds would take a look at this.

I went through the MSFS mappings and can't find anything conflicting (I do not have many mappings there at all). I'm using Spad.Next for the throttles. Similar Spad.Next mappings work for eg. Inibuilds A300, A340 and A350. So I do not believe that is the issue. Did reinstall too but that didn't help. Problem also exists after 1.0.1 update.

For me trying to use Panel state just doesn't work. If I try to put the plane to "Ready for takeoff" state, some of the engines won't start up. Usually it's engines 1 and 3. If I repress the "Ready for takeoff" it might get the engines going but not always. Also using the "Autocomplete" buttons under "Flight engineer autocomplete" do not work: some of the steps stay red. And when I do get the airplane runnning, engines will shutdown seemingly random.

Not asking for updates or trying rushing anybody - I'd only like to give my vote to A300 premium support. It's an amazing plane and Wingwing support for it would be so good.

Yeah, a terrible decision. Who will actually buy this from Marketplace when it's been said the Inimanager version is coming? And another truly bad decision is to release it only for 2024. Those who are still sticking with 2020 have done so for good reasons, and in that case, the only option is to skip this aircraft.