Xenon341

That's a reasonable expectation, the problem in this case is that it's a platform bug, that mean that code must be added to do "wrong" things in order to make the thing work again. Code that will need to be reverted again when SU4 will release (as the platform bug has been fixed in SU4 it seems). I guess the problem is that if Asobo release a SU3 hotfix for that it can break what a dev could attempt to counter the bug.

That's a platform bug, see https://devsupport.flightsimulator.com/t/rain-is-distorting-hud-textures-when-viewed-from-inside-aircraft/13563/2 Ini responded while ago on their discord.

Yes SU4b bug related to WASM, below a message from the team.

FYI, SU4b bring some bug related to WASM so expect some problems with the plane. Below a message from the dev team.

Know issues from SU4 beta. Some platform bug on the WASM side have been raised. See the developers response here. You can use Sim default nav data as a workaround.

Hello, The errors in the console are not A350 related but I guess that maybe the following lines might. Can you please follow this guide to report the crash and add OFP, autosave, nav data source, last actions made etc. ? I'm always using BeyondATC and don't have WASM crashes so I don't think it's related. Thanks !

Hello, Can you please add the information from this guide (ofp, autosave, last actions made...) ? Thanks

I'm just giving you the answer they gave. I'm no 350 pilot nor airbus engineer to confirm or deny.

Ini already answered that, it's a real setting that cabin should be ready before TO Config based on their A350 real life pilot feedback.

Hello, You need to enter the new lowest altitude the plane can descent then either push the ALT knob (managed descent, VNAV equivalent to Boeing where the plane follow the FMS calculation) or pull the ALT Knob (selected descent - Open Descent, equivalent to FLC mode where speed is the limiting factor and the plane descend with idle power untill it reaches the selected speed) Regards,

Know issue, message from their discord : The LOD system has changed following Sim Update 3 (SU3). We’re aware of the impact this has had and are actively working on a fix. An update will be released as soon as possible. In the meantime, a community workaround can be found here: ⁠🚁msfs-community-support⁠Invisible Cabin/Cargo in 3rd pe… Please note that this workaround forces the model to load at "LOD0", the highest level of detail, at all times, which may have an impact on performance. And the workaround : C:\Microsoft Flight Simulator 2024\Community\inibuilds-aircraft-a350\SimObjects\Airplanes\A350\common\model Change "withExterior_showInterior_hideFirstLod=true" in Model.cfg to "false"

Hello, Last message I see on ini's discord from an ini member :

Hello, If I recall correctly, AI taking control with cursor mode is inevitable, developers can't disable it 😕

I have decent perf yes but if I check the official forums a lot of people have perf issue in SU3, not necessary with A350. Mainthread seems to be a big one https://forums.flightsimulator.com/t/mainthread-loads-up-more-and-more-and-doesnt-recover/729018/184 To be clear I would not say no to more FPS 😄 but even OP said that in SU2 it was OK and in SU3 it's not anymore but the plane did not change so for me, the platform brought some stuff that maybe don't work well. If ini can fix some stuff that great but IMHO, something from the platform may have caused this.

You have beefer PC than me and I have 70-90FPS with 2xFG on 4k Ultra so that may not be as easy as "optimize it"

Yeah the solution should work. There is another one if you are using VR but this one should work if you are not.

Hello, Did you check that your Hoppie API key is still in the EFB ?

Oups, good catch indeed that’s not the one I wanted to post. This is the one :

Hello guys, can each one of you add the informations from this guide in order to gather data on the crashes you had ? Thanks !

I had some things to say but that was to basic for you sadly. Have a great day.

I don’t know what advice you are expecting from people that doesn’t experience your issue beside « basic steps » like you said. This is a community forum not an engineering one. Contact direct support if you want more. https://inibuilds.com/pages/contact

Are you even reading what we answer you ? The solution has already been given and it should be re applied until SU3 is released and supported.

A330 Driver on youtube use SayIntention with CPDLC and ATIS with the last update and it works fine so maybe something with your config ?

Sim freeze is not a "basic malfunction", and it's not because OP system is freezing that every system are freezing. A lot of people can use the plane without any sim crash. A sim crash is not a WASM crash and a WASM crash is not a sim crash. I think people in this thread are not even talking about the same problems. Now if OP want to do something that can help him find the root cause, open windows event observer, find the trace of the sim crash and check inside if there are any hint at what caused it. Another thing you can do is try with only the A350 in your community folder to find if something else is causing the sim freeze.

Works fine here, just passed over the Alps and had terrain on FO screen. Even over Italy it works, see screenshot. Maybe try a WASM cleaning following this guide :