Are you using Developer Mode or made changes in it?
Yes - ive used dev mode to view wasm debug
Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.
Yes
Which aircraft are you reporting an issue about? (Please also add the proper tag for it)
Airbus A310
Which aircraft version are you experiencing this issue on? (You can find this listed in the Content Manager under the Aircraft Name)
1.1.12
Brief description of the issue:
Aircraft button and displays are not working wasm debug shows a310 wasm is dirty
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Load aircraft attempt to use tablet or press any button/switches in the cockpit
PC specs and/or peripheral set up if relevant:
N/A
Build Version # when you first started experiencing this issue:
1.35.32.0
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
As OP said, loading in the A310 renders it unuseable, though strangely when selecting the A310 using the Aircraft Selector in Dev Mode it does activate the plane correctly. Additionally, performance is tanked and the console log gets spammed with messages.
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
Rolling back to aircraft version 1.1.10 works fine issue seems to be with 1.1.12. loading aircraft with dev mode as simtom2 suggests system to load but switches/buttons remain inop for me
If relevant, provide additional screenshots/video:
I have the same issue all of a suddeen. Loaded the A310 and no avionics and selecting the “Ready for Take Off” option on the tablet doesn’t seem to do anything anymore. None of the switches or button work either? I haven’t changed any settings or added content to the community folder so not sure what exactly caused this issue all of a sudden? Any ideas?
I decided to use it today to give it a go before buying the a300 version and nothing in the cockpit worked, it was like when turning batteries and external power the aircraft was still in cold and dark, no matter the state. Tried to reinstall two times and nothing changed. Unusable, I hope they fix it.
Man…am I “happy” to see this topic…I was maintaining my MSFS setup with all kinds of joystick profiles for the different aircraft I fly, while I discovered the problem with the A310, been busy for a few hours to try to solve it, deinstalled and installed a few times…did not see anybody mentioning the problem here…until I found this topic now.
I have the same issue. The plane is unusable right now. I get a weird loaded state which is neither “cold & dark” nor “on GPU”. And I doubt a patch will be pushed during the x-mas-new-year holidays.
This is however a very welcomed issue as I now know I won’t buy their A300-600 addon. They just lost a customer but they probably don’t care. I don’t want to fight their bugs (or worse: their regressions). I don’t want to pay for that.
Moreover their A300-600 already showed bugs that make the plane unusable:
At ~00:40:00 you can see the A300 crashing (I know it’s supposed to be a “prerelease”).
And for those who say the A310 is a freeware, it’s not. Inibuilds get paid for it by MS. We paid for it with MSFS2020. Nothing to compare to what FlyByWire is doing for the community
Relevant thread on Inibuilds forums (now locked):
Edit 1: add link to Inibuilds forums.
Edit 2: Inibuilds locked the thread yesterday + typos
I see a number of these Microsoft commissioned aircraft (40th Anniversary, Local Legends, Famous Flyers & Expert Series) developers take a fair amount of grief from the userbase for the bugs, issues and lack of fixes.
What is frustrating, to me, is the fact that rarely is Microsoft held accountable.
Here, IniBuilds is taking flack for the issues. Well, okay, but where is the producer at Microsoft who is charged with seeing these aircraft are maintained and updated as the sim changes over time?
We don’t know what the contract is between these developers (IniBuilds) and Microsoft, yet some are outright blaming the developers as if they do know the terms of the contract. For all we know, IniBuilds might be free of it and they have to accept a change order from Microsoft with an enclosed check to make changes.
We-just-don’t-know.
What we do know is that Microsoft commissioned these aircraft and it is Microsoft who should be held accountable for seeing them maintained.
Here, join me in asking them what their plans are:
I have not had any good experiences with Inibuilds plane (A310) - issues and bugs and the airport (KJFK) - Low FPS. I am very hesistant to purchase anything further from Inibuilds. As for the latest A310 issue, what changed from one hour to the next? I don’t recall receiving any updates (ARIAC) so what exactly happened to bonk the avionics on only this aircraft?
Had the same issue today. Started cold & dark, but nothing worked. I’ve reinstalled the plane using the content manager and got it to work. In the approach stage of a 2hrs flight, the instruments and FMC stopped working after I clicked “ACARS” in the FMC. The plane was completely useless…
I’m glad I found this discussion and knowing that I’m not alone in this. With all that hype for the A300, I wonder if this issue will be given the proper attention.
confirm, select a parking spot, and start to start the power and not working almost anything, after update
Did anyone of you notice a recent update? As the game is so looooooong to start I often do something else while it’s loading. Did I miss a recent update?
Do you have the same issue if you follow the OP’s steps to reproduce it?
Certainly Yes
Provide extra information to complete the original description of the issue:
Tried to change the panel states from the EFB, that also does not work. When loading on runway I can hear the engines running but every display is black. When loading on ramp/gate can’t turn on the electricals. I even checked the all 3 battery voltmeters and reading was 0. Same for AC power with GPU connected.
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes, A 310 does not function, does not take steering inputs, pfd and all other screens stay black. User can interact with tablet but changes are not saved. Upon loading you can hear engine sounds and systems turning off, despite aircraft loaded in cold and dark state.
Steering Inputs etc are not recognized.
Overhead panel appears to be clickable but, button clicking seems to have no effect. Depending on the livery selected, Buttons illuminate or not.
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
I hope this A310 bug is fixed soon. I just spent last week sorting out CTD issues with the A310 now this dead flight deck. Seems Inibuilds have done there part. [From inibuilds forums posted Dec 28].
For anyone who wants to contribute on this issue, Click on the button below to use this template:
is doing for the community 
