All Activity

I don't use repaint and just use the default white color. Every time I update, there are always problems.

I think it is necessary to stress that CDU itself works, you just cannot interact with it using a VR controller. It doenst register any clicks. You can see the cursor move, but no clicks are registered unless using a mouse.

This issue very much still exists (last checked with 1.1.17 and SU4). The CDU cannot be interacted with using VR controllers while the OIS can. This issue has been around for a while. The A350 CDU is unusable in VR without using a mouse. The same issue also exists with the Airbus A400.

May I also show this… sent as a Facebook link because your forum won’t take the video. https://www.facebook.com/share/v/1Bp7iK3eE1/?mibextid=wwXIfr

I'm having the same problem since the latest update. The sim,(msfs2020) crashes on loading the flight. This is only happening with the A350, no other aircraft in the sim does this. I'm not sure but there have been suggestions that the textures need updating. If this is the case could inibuilds give us some idea when this is going to happen please.

Since a few weeks i get the a350 without a cockpit right after start. I Can start Msfs24 again, I Can reboot my computer. Nothing helps. What to do??

Can we get an answer anytime from you as to whether or not the devs have actually identified yet what this is? This issue seems to be cropping up primarily in SU3 still, not SU4.

I had this WASM crash after I had completed loading my flight data and was about to push back. No specific action was taken to cause the crash; I was on the external view and the plane systems froze when I returned to the cockpit. Information Aircraft: A350-900 (1.1.8) Simulator: MSFS24 Navdata Method: NAVIGRAPH OFP: Attached SimBrief OFP Specs: Intel i7-13700K, Nvidia RTX 4070ti, 32GB RAM Autosave: Attached latest .BIN file before crash WASM: Error during EFIS_gauge_draw execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty 1764752551.bin EDDMKORD_PDF_1764749112.pdf

Hello, This is resolved with the coming 1.0.5 update. The error only indicates that the "EFB MY FLIGHT - ROUTING" section fails to show the route from your OFP; it has no functional impact.

I also updated to the latest one, but I dont have any issues, Maybe any of your files maybe conflicting with A350, I guess

Same Issue

I had this WASM crash when I clicked the CMPNY WIND REQUEST button on the MCDU. To reproduce Load at gate Power on aircraft (Battery, GPU) Complete MCDU setup (weights, fpl, SIDs and STARS) Click CMPNY WIND REQUEST on INIT Page Orange WASM Crashh on Screens Information Aircraft: A350-900 (version 1.1.8) Simulator: FS24 Navdata Method: NAVIGRAPH OFP: Not required, happens on any route Specs: Intel i7 12700k, RTX 40080 Super, 32GB RAM Autosave: Attached latest .BIN file before crash WASM: Module: /SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm Gauge: EFIS wasm crash.txt 1764751760.bin

Hi Steven, my first flight was the Virgin livery and went without a hitch, I since tried on emirates, FIN and DAL special livery.

See my reply to you in general -A

I'm the same. I wrote about it on the forum, but they completely ignored it. This manufacturer is the worst.

Good. That’s how it’s supposed to work. Unfortunately I still experience the freezing. Hopefully ini can provide a universal solution. Blue skies, -A

I had no freezes since simapp version 1.16.72

I had no freezes since simapp version 1.16.72

Happened to me after last update, and fresh deinstall/reinstall solved it. Did same for latest update, and this bug is back. What gives?

Just flew from Newark to Minneapolis ... all perfectly fine until below 10000, then all hell broke loose. Got icing warning, turned on de icing systems, and plane went haywire. Automated systems failed, speed tape showed stalling at 220 kt, and plane wanted to plunge. Had to manually recover and barely made it to runway. Is this the icing bug in action? Never experienced anything like it before. Fenix does NOT do this. 🙂

fixed it by deleting cache files.

Thanks Rerem, I've found the issue. If you're on the NEW WAYPOINT page and press LSK R5 the key BELOW return, it crashes. I've passed it on to the team.

Actually, the AMKEN waypoint was considered nonexistent. I tested with PPPPP (you know, to enter a custom waypoint), and the next page works fine, but when you click the back button, everything turns red and the whole system locks up. I don’t know why the AMKEN waypoint was treated as a custom point. But there’s a major bug and it’s 100% reproducible.

Hi, could you provide the full flightplan you tried to enter? And is this repeatable or it just happened once? Were you on Navigraph or Sim Default navdata? -Steven