ChunkyMonkeyHustler

I’ll second the motion for window shades on MSFS A350 with no cabinet, please.

Thank you @dectenor1 for taking the time to thoroughly document and present supporting evidence for some of the more frustrating deficiencies and inaccuracies of the iniBuilds A350 program. Thank you @Eddie for actively engaging with your customer base and reassuring us that the iniBuilds team is actively investigating and addressing our concerns. Personally, I am hoping for fewer new features, and more currently available features working accurately, correctly and consistently.

I too have this appearing in my iniBuilds app. So, what does this mean? Is it an update? any changelog? Do we dare install this unnamed, unidentified "update," or is this an app glitch? Edit: to clarify I am a MSFS2020 user.

Excellent, thank you Eddie. You always set me straight so gently, so thanks again. I'm looking forward to putting the HUD to good use.

There are a few threads going around with this issue. IniBuilds has indicated they are aware, are seeking more information on the problem and hunting for solutions to the challenge.

I cannot answer your question as to when, but iniBuilds did say in the HUD announcement that it will be functional in a future update. It seems to suggest they released and announced the HUD as a PR gimmick at FSExpo, even though it was not ready for launch and didn't need to be added as a "tease" to existing customers' flightdeck.

Thank you for reassuring me that iniBuilds is on the hunt for the cause of this issue. There has been a video uploaded to the other thread (we are both monitoring) that shows how the plane loads unpowered and unclickable. Thanks again, ChunmkyMonkeyHustler

It is time to stop pretending this is a viable solution. It is not. Please address this issue with a more vigorous response.

I too am suffering from this issue, and was curious if any of the before mentioned items were relevant to you. I seem to be able to just reload the flight and the plane comes up on GPU power, which is the profile i have load when starting iniBuilds A350. I'm hopeful iniBuilds will begin to address this as these reports are starting to popup all over the forums. I have tried all the alleged "fixes" to no avail. Thanks, ChunkyMonkeyHustler

Hello, The FeelThere KLAS in the iniBuilds store and app are listed as version 1.0. However, there is a more recent version available. Is it possible to get the iniBuilds app offer an update to the latest version. Version 1.0 is severely outdated and suffers from several terrain and photogrammetry issues, among other problem. The updates allegedly fixes these issues. Thank you, ChunkyMonkeyHustler

Thanks for pointing this out. Look like the update pushed.

Questions for both of you: Is MSFS2020 crashing on exit? Do you have to use Task Manager to End Process? And, have you tried spawning a new flight in a new A350 livery at a new position?

I had a WASM crash, while enroute from YBBN to KLAX, four times on four separate days attempting this flight. To reproduce After taking off and reaching altitude (FL350) about an hour into the flight the clock freezes. No keys or buttons pushed. No obvious WASM crash inducing event that I am aware of. Happens in both 1x and 4x sim rate. Panel becomes non responsive and the aircraft appears to be flying straight, but the NAVIGRAPH moving map shows the aircraft in a large righthand turn. Information Aircraft: A350-900 Simulator: FS20 Navdata Method: NAVIGRAPH OFP: Not required, happens on any route between YBBN and KLAX (possibly others).1749842793.bin Specs: Intel i9-10900KF, RTX 3090, 32GB RAM Autosave: Attached latest .BIN file before crash WASM: Exception c000001d in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm

I have had serval instances over the last two or three updates where the A350-900 and A350-1000 flies .02NM to the left just after departure and upon autopilot engagement all the way through the autopilot intercepting the ILS on approach. I've tried disconnecting the autopilot and manually recentering on the route. When I reengage the autopilot the aircraft will drift back to the 0.2NM left. Take note of how the autopilot commands the ailerons. (This phenomenon occurs regardless of wind speed and direction.) Thoughts, suggestions or solutions?

Thank you so very much for your reply. As someone new to Airbus doctrine, I am learning quite a bit thanks to the iniBuilds A350—so fascinating. Apologies for wasting time and energy, but perhaps this will clear things up for other recent Boeing converts. Thanks again.