IniJamir

[X]\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\inibuilds-aircraft-a350 and then delete the work folder. This is the 2020 Clear WASM Link

Hi, Can you do me a favor and press the CTL switch next to the Dome Switch on the Overhead Panel. I want to see something as I just finished a flight and noticed some lighting behaviors and wondering if this could correspond with it.

Hi, It just occurred to me, do you have Hues Core installed when using the A350?

Thank you for this information, I'll raise it to the team.

Alright so what we can go ahead and try next is clearing your WASM folder; this can be done by following the instructions down below

Logged and will be attached to a master wasm thread. Thank you and please attach all future wasm crashes with autosaves to the thread linked below.

Hi, I will pass this suggestion along to the team 🙂

Hi, Thank you for the suggestion, I will pass it along to the team.

How old is this livery from Flightsim.to, it's possible that this specific one is out of date, can you try a livery from the IniManager?

The update has been sent to Asobo.

Glad I could help 🙂

Hello, This is an issue that is still being actively investigated. It occurred during my flight last night 8 hours in with only 2 hours left to go, trust me when I say the frustration is felt on both ends and this issue has not been forgotten. Thank you.

Liveries from Flightsim.to are updated on their website whereas liveries from Inibuilds can be found in the IniManger Liveries Section then navigating to the aircraft and simulator you are using. There liveries can be installed, uninstalled, and updated when updates are available. Are you using any mods that need to be updated?

Hi, Approximately how long is it taking to load, the first time initialization of the A350 can take a good 5 or 10 minutes on some systems including my own, this is the case after updates as well as it recompiles. You can also attempt to clear the WASM folder here,

Hi, Please try to keep it to English as the forums are English only. That being said if you have a Navigraph subscription then you will be able to update the AIRAC, and can do so via the OIS > Options > 3rd Party Settings then sign into Navigraph and Update Navdata. If you do not have Navigraph then you will have to wait until Asobo updates the navdata in the simulator itself. Hope this helps.

Yeah, it's pretty cool and you'll notice differences in the startup of the screens as well. I personally love EIS1 more than EIS2

Hello, Can you try leaving all the liveries loaded and then switching between 2-3 of them in sim and testing that. I usually leave all of my liveries in the community folder and only link sceneries externally so I am curious if that could be the issue.

Hello, EIS1 (First Generation) Technology: CRT screens. Era: Older A320 family aircraft (production up to early 2000s). Visuals: Slightly smaller, rounded-edge display units. System: Often associated with earlier, more basic ECAM layouts and older Navigation Display (ND) logic. EIS2 (Second Generation) Technology: LCD screens. Era: Newer A320ceo (mid-2000s onwards) and standard on A320neo. Visuals: Improved, square-edge displays with higher contrast and resolution. System: Updated ECAM layout, often integrated with newer avionics systems like digital chronometers or ISIS (Integrated Standby Instrument System). Hope this helps, thank you.

Correct, there is actually a list that I have from 2020 that has all of the handcrafted airports as well as which versions had which airports that I use to make sure there are no conflicts as there are quite a lot of default sceneries. Even though it's for 2020 all of the Defaults from the WUs are shared between sims. https://flight.fandom.com/wiki/Microsoft_Flight_Simulator_(2020)/List_of_hand-crafted_airports

That is quite alright. The game comes with a default handcrafted Dallas Fort Worth which does conflict with the Inibuilds KDFW. The Asobo Scenery, which can be disabled by going into Marketplace > My Library and then search for KDFW in the Content Manager and ensure that the FS2020/2024 versions are disabled and only the one with Community on it is enabled.

That is quite alright. I am gonna lock the thread currently so it doesn't get bloated with other comments as well as link the route from your other post into here so that we have it for investigation. Thank you.

Hello all, The issue has been identified and a fix will be rolling out in the next update. Thank you.

Glad I could be of help 🙂

Hello, this is a known issue between varying sceneries that is being investigated. Unlike other sceneries which have toggleable POIs that we've suggested users disable, YBBN does not posses this function, sorry for the inconvenience at this time.

Hi, Thank you for this information, I shall pass it along, one recommendation is disabling the crash options in the assistances menu so that way if you encounter any bumps whether it be here at DFW or any other sceneries; you don't have to restart and lose all your progress. Additionally make sure that you have no terrain mods or alternate sceneries installed just to be on the safe side. Thank you.