All Activity

This is an issue I have reported on the A350 since release. It is really disappointing to see yet another aircraft release with the same issue (it is also on the A340).

Because I had this same problem with the NAMAC autopilot system

Tried again with my Logitech autopilot i think it might be a streaming issue

uninstall then reinstall solve the texture issue

Can confirm all my issues have been resolved with the steps PeteC56 mentioned. As of now, I'll keep the aircraft on streamed and not installed locally.

Thanks, will try this too.

For me, I have a similar problem but not quite extensive... I updated via Marketplace and also re-installed all the liveries via inimanager. For all aircraft variants, some texture of the outer turbine section seems to be missing: Also, the Emirates Cabin on both engine variants is not displayed. Standard cabin works normal. If I select the Emirates cabin on a livery and cycle through performance mode on/off, with performance mode off I get the cargo hold displayed when I open the cockpit door but the rest of the cabin is missing. With performance mode on, cargo hold is also not displayed.

Thanks 559AS. Yes, I uninstalled the three liveries that I'd installed from IniManager, started the sim and went to My Library and uninstalled the A380, so it was now streamed once again rather than Installed. I then went back to IniManager, and re-installed the three liveries, started the sim again and all is well! Hope this helps you too, Matteo Spacca.

4 but i have 2 throttles controlling 4 engines and the 2 inboard engines reverse thrust.

I believe you have to update your installed liveries via the iniManager. They've all been updated along with the aircraft itself. Edit: Nevermind, I see that you installed the livery updates too.

Market place does show that I have an update available under my library, however after I select to install the update, it still shows as version 1.0 and its confirmed after loading the aircraft and checking the version number in the EFB. I've attempted to install the update 3 times with the same result to include a restart of the sim. Any timeline on when we can transfer the A380 to our iniMananger accounts to avoid the mess of a circus that is MSFS Market Place? Soon please!!!

Minor error I just found. The FMS POSITION drop down menu. GPS should be replaced by GNSS (Global Navigation Satellite System) and a subsequent page with a top GPS selection menu and a GNSS Data subsection below. Secondly, FMS Data, Waypoint. Should open up a box where you enter database waypoint. Ex, KJFK31L, enter KJFK31L into the page, will give the lat/long for quick return (Not working or simulated). Reason for needing this Lat/Long. We insert the landing LAT/LONG into the standby navigation display. Will give a direct distance and direction to the runway for a quick return. As an additional comment, ETP needs to be implemented. Just a few minor detail to consider.

with the windows open there are identical polygon protrusions either side see white spikes in corner of window frames

I'm getting the same too - along with no cabin/s stairs etc.. Hope theres a fix before too long.....it's totally unflyable now!

with the windows opened can see daylight on both sides

Just fly over long stretches of water and the terrain radar works just fine 🙂

After update I get this. How do I fix it? I tried to reload the aircraft and restart the sim but no luck. Liveries also updated Thanks Matteo

Thanks, already logged for the team!

Awesome, I'm glad you got it working!

Kyle, I tried Chicago and had the same promlem. GSX menu no jetways and multijetway a rotation warning. I exited and went to the GSX live updater page I hit the check file button. It verified the files. After this I tested at EGLL with the A380. Both GSX and the INI multi jetway menus both worked fine. I tested at 4 different gates and all worked Inc multiple jetways For anyone else that reads this. May be of help

exactly and this is the attitude of a company that sees the benefit and appreciates the constructive criticism rather than discouraging it like some other very well known developers still do, good business sense and we can all see the results

Agreed, 100%

Hi, We have identified the issue, unfortunately it did not make it into the 1.0.1 build. I have been told however, that it will make it into the 1.0.2 build! Thanks for your patience!