sirupflex

<removed> Looks like a weird filter thing ...

I fed your error log to the Gemini AI and got the following analysis back. I have no clue if it is of use but suggest to give it a try: WASM Crash Analysis: inibuilds A350-900 Conflict The provided error log points to a classic memory access violation (0xc0000005) occurring when multiple complex WASM modules compete for resources. While the inibuilds A350 is the "victim" here, the log reveals several other active modules that are likely triggering the instability. Identified Conflict Candidates Skyline Simulations (WMKK) - Primary Suspect: Log Entry: [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: Initializing... Reasoning: This driver belongs to the Kuala Lumpur (WMKK) scenery by Skyline Simulations. Interestingly, the log shows this driver actively reading the AIRCRAFT_TITLE of the A350 right before the crash. This interaction suggests a direct conflict between the airport's custom logic and the A350's WASM environment. Noolaero VDGS (Multiple Airports): Log Entry: [noolaero-vdgs-xxxx.wasm] EXCEPTION 25 Reasoning: These modules manage the Visual Docking Guidance Systems for various airports (LPPT, ESSA, EIDW, LSZH, etc.). The log shows a flood of "EXCEPTION 25" errors. While these might not always cause a CTD (Crash to Desktop) on their own, they clutter the SimConnect stream and increase instability. FSDreamTeam (FSDT): Log Entry: [fsdt-msfs-bridge.wasm] Reasoning: This is the bridge for GSX or FSDT sceneries. It is active but generally stable; however, it adds to the overall WASM load. The Fatal Sequence The crash occurs immediately after the SS_WMKK_Airport_Driver identifies the aircraft. Simultaneously, the A350 fails to locate several PNG texture assets: WASM: Error during EFIS_gauge_draw execution. Error code : 0xc0000005 This indicates that the memory address the A350 was trying to use for its gauges was likely "stepped on" or blocked by another module (most likely the WMKK driver). Recommended Troubleshooting Steps Isolate WMKK: Temporarily remove the Skyline Simulations WMKK folder from your Community folder. This is the most likely fix, as the crash occurs exactly during its initialization phase. Update/Disable VDGS: If you are using a standalone VDGS package or sceneries from Aerosoft/JustSim that use Noolaero, ensure they are up to date. Clear WASM Cache: Delete the contents of the WASM folder located in your LocalState directory (the path varies for Steam/Microsoft Store). The simulator will rebuild these files on the next launch. Use Addon Linker: Since the A350 is a resource-heavy aircraft, use an Addon Linker to disable unnecessary airport drivers (like the ones for Dublin or Stockholm) when you aren't flying to/from those specific locations.

Wow, this is sad. IniBuilds is censoring postings now. Posted about the frustration of my teenager son who bought the A350. Didn't use any inappropriate words or explicit expressions, but iniBuilds does not want to hear negative feedback any more. I guess this says it all. Good bye.

Unfortunately, iniBuilds is the only brand in the premium segment who does not care about supporting the most popular flight sim hardware manufacturer. I will not buy any further iniBuilds products until a) they have full WinCtrl support incl. MCDU and b) the A350 is stable and usuable for realistic long-haul flights.

@IniJamir Do I understand correctly that V1.2.3 solved (at least part) of the MCDU-entry triggered crashes, which is good, but did not yet address that "ghost WASM" issue where some cockpit modules silently freeze and the plane cannot be controlled any more? Just curious to understand, because that "ghost WASM" issue is the big one preventing me to use the A350 for months. Will try again once a reliable fix for this has been released. Please clearly communicate the fix once available, I think a lot of people are looking forward to that fix. Thank you.

Not surprising, the release notes didn't mention any fixes of WASM issues or the sim connect issues, unfortunately.

What does "best done via a 3rd party control process" mean? The input-only way via Mobiflight is not what I want to use. Given that the A350 is one of the the most expensive airplanes one can buy for MSFS2024 and it is promoted as "Premium", I do hope iniBuilds will be taking the effort to make it work with the probably most popular airbus MCDU hardware, also given the lack of a proper consumer-targeted A350 MCDU hardware.

Does this mean iniBuilds has finished their job and exposed an API that allows the integration with the WinCtrl MCDU? If yes, why haven't you updated the A350 to be compatible with the MCDU, as this aircraft is under your full control? Yes I know the A350 MCDU is a bit different especially with the screen but you still can make it work with the WC MCDU hardware. Would be really appreciated.

Thank you very much for these insights. They are really important and helpful for all your customers to understand where we are and that iniBuilds is taking care of issues, still. It is great to hear that you could reproduce "my" WASM crash, that gives us hope that it will be fixed in an upcoming update. Please continue communicating and responding to reported issues so the community can go though that journey together with you and so that you can build up some trust again. I was very interested in buying the A340 as well but given the issues with the A350 that currently do not allow me to use this model in any reasonable way, I decided not to buy any further iniBuilds airplanes. If issues with the A350 can be fixed and trust can be reestablished, you will have me back as an A340 customer.

@iniSteven Thank you so much for providing a reply to this discussion. I already lost hope that iniBuilds still cares about the ongoing issues with the A350. It is great to see that you acknowledge the issue and are willing to provide a fix. Could you please confirm if my reported issue here has the same root cause (although it clearly says "WASM Crash" on the screen)? If yes it would be great if you could copy&paste your reply there as well so people get that feedback. FYI, by mistake I've created that linked bug report in the MSFS 2020 section, please feel free to move it into the MSFS 2024 section for the A350 to avoid any confusion (I can neither move not delete that thread anymore). Thank you!

I can confirm that this happens to me as well quite regularly. During flight at cruise altitude, without any input or activity from my side, some functionality of the A350 stops working and/or modules freeze and you have to abort the flight. It is hardly possible for me to have a 3-4 hours flight without the A350 crashing rather sooner or later. It is then also a bit frustrating when iniBuilds celebates the A350 in their 2025 review but in fact for me the very expensive airplane is actually useless. A long-range model that crashes on nearly all long-range flights. For me, stability of the A350 has not improved. All other airplane models in MSFS 2024 are stable and I hardly have any issues with anything else than the A350. Today I logged a WASM crash report in the forum (in the MSFS2020 section of the forum by mistake), hoping it helps resolving issues. iniBuilds says they are seeing less A350 WASM crash reports than in previous months and conclude that the A350 is much more stable now. My perception is rather that many customers gave up on the A350 at all or stopped reporting bugs out of frustration because not a lot changed in all those months. I cannot confirm that the A350 is even close to stable.

Winwing had the iniBuilds A350 on their list of models they wanted to support with their MCDU. Functionality is very similar. Display is different, of course, but having it in hardware with a A320 style display is still much better than clicking each button via mouse.

Thank you Eddie for confirming that you / iniBuilds are working on enabling the Winwing MCDU for at least the A320. I think this is the minimum confirmation most people have been waiting here for. Would it be possible to confirm if you plan to also enable the MCDU for your A350? Not asking for a date, just checking if it's part of what iniBuilds intends to do. And talking about timelines, is it possible to give a hint of the kind "potentially still in 2025 if things go as planned", or rather "Unlikely before 2026". That might prevent people asking you here every few weeks about the status.

Dear iniBuilds team, the WinWing devices are a fantastic way for regular enthusiasts to have a realistic flight sim experience that otherwise would not be affordable. It would be amazing for iniBuilds to enable MCDU support for the A320 / A321 in MSFS 2024!