Apologies if a solution exists somewhere and I haven’t found it.
I downloaded the aircraft and put the folder in the community folder today.
I know the systems are largely based on the stock a320, and I have no problem starting that one.
If I try to follow the tutorial linked on flightsim.to, I seem to get hydraulic yellow cautions that won’t go away until I toggle the hydraulic switches seemingly randomly.
If I’ve got the hydraulics looking acceptable, and the APU running with bleed on, engine mode in ignition, and fuel on, I still don’t get anything looking like an engine startup. I wonder if I’m missing a step, or the aircraft is buggy.
I’ve even scrapped the manual startup in place of using the tablet to bring it straight to ready for taxi state. The tablet gets hung up on the fact that the FMC and the FWC aren’t initializing.
Any difference if you enable external power? Trying to figure out why your ND and MCDU aren’t on.
Also just a side note, I’ve heard the Airbus philosophy on the Overhead is a “No white lights” one, so if you have white lights on, you need to fix that. If having they hydraulics on causes some other error message, then something else might be wrong.
Any mods or liveries installed? Clear all that out, too.
Forgetting the APU, initializing everything off of ext power only, and adhering to the no white lights policy, I still get several warnings cautions that I can’t seem to dismiss.
I have navigraph installed, but no mods or other liveries otherwise I think. None running at the moment. I was attempting to play with FSLTL traffic today, but I’ve kept that off since running into the a330 issues.
The ND and MCDU are still not initializing. Of course, I can’t test startup without APU bleed.
In case it matters, I’m using the Honeycomb Alpha yoke, the Thrustmaster Airbus throttle quad with addons, and Logitech pedals.
I believe the flight control warnings are because you don’t have hydraulics to drive them, and you don’t have hydraulics because your engines aren’t running. So fixing the engines should clear all the rest up.
You mention Honeycomb. Do you have any switches that could be turning off avionics or systems, or do you have any mixture controls mapped that could be preventing fuel from reaching the engines? “Hidden” keybinds or control binds have caused all sorts of weird things with aircraft that don’t even have those controls. Mixture is notorious for causing issues on airliners because no one would think that should cause issues in a plane w/o a mixture lever, yet it does.
Not having the ND and MCDU on is very odd. Are their brightness settings turned down to min/off maybe?
If you did, ensure there are no other mods of any type, whether from the Marketplace or any that may be in your Community folder.
If you have none, try using the installer to uninstall and reinstall the aircraft.
If all else fails, you can go to their discord for support.
There’s been a recent post on the FBW Discord that outdated Windows Defender profiles have been deleting A32NX and A339 files, causing among other things, blank displays.
Updating Defender and delete and reinstall the aircraft is supposed to fix it
I really appreciate all your help. I’ve completed some more testing without success.
I confirmed that the Honeycomb yoke doesn’t interfere (left it unplugged during startup)
Confirmed that ND and MCDU brightness all the way up.
Forgot to set ADIRS in earlier screenshots - confirmed that having them set to NAV has no effect.
Importantly, I realized that I initially downloaded the aircraft file from flightsim.io, so I removed those files and reinstalled via the Headwind Installer. This gave no change
Finally, I couldn’t understand the instructions for updating Windows Defender that I could find, but I turned it off, removed and reinstalled the aircraft via the Headwind Installer. Still no luck.
Still, the ND and MCDU are not firing up. I noticed that a few of the black screens were acting glitchy, as if the LCD was physically jittering.
If it helps, here is my Community folder. I don’t think I have much that could interfere, but I could be wrong.
The first thing you will probably be asked is if you tried the 330 with all other addons disabled.
The easy way is to just rename the Community folder, and let MSFS build a new empty one.
Then install the A330 via the installer.
This was successful. I renamed my Community folder to “Community_backup”, and created a new Community Folder with ONLY a fresh A330 install. (and Simbridge) Once I confirmed that worked, I started replacing my other add-ons. I think the build had an issue with the community liveries (admittedly pretty old).
The A330 works with my Navigraph, FSLTL, Concorde, and DC6 files. Left out the old liveries.
