kevink817

And yet you've failed to provide any debug or troubleshooting information to help iniBuilds sort the issue. Many people, myself included are flying the A350 just fine, including long-haul flights 9-12+ hours so, if you're experiencing issues with this plane still, then it's likely something on your end - either your hardware or another addon interacting with MSFS and causing a WASM crash. Maybe try to provide some relevant data to iniBuilds, and maybe even provide an autosave and perhaps they can reproduce and fix your issue before you come to the forums and whine that it's not working for you without providing any meaningful, helpful, or constructive information.

I solved it my disconnecting and re-adding my navigraph account in the EFB. Then it was able to download.

Ah those yellow footprints... January 2006 for me. West coast.

Xbox or PC? What version?

...but it wasn't to idle. It was an AT disconnect and the throttle went to %40-50 where my physical throttles were set.

This happened to me once. I honestly felt like maybe I had accidentally hit the AT disconnect button I had mapped. But in 30+ flights it only happened once on 1.0.9 while I was trying to reproduce another error. Maybe it wasn't just me. It happened exactly after rotate, just as the mains lifted off the ground.

180kts let it intercept perfectly. Any more than that and it was drawing an overshoot.

Tested in v1.0.9 and this all appears to be resolved.

Tested in v1.0.9 and this all appears to be resolved.

Just tried out the CONT2A SID from MMCE with the new v1.0.9. It followed the DME ARC perfectly, though i had to manually select speeds on waypoints to make sure the plane would not overshoot.

Seems to be a bug with the APU not shutting down properly. See this topic:

One final test: Unlatching and pulling the APU fire handle while fully running appears to fully shut down the APU (EGT drops to OAT, and N1=0), but fuel drain remains as well as the exhaust heat and noise effect.

Additional note: Unlatching and pulling the APU fire handle does not cut off fuel to the APU either when its in it's bugged partially shutdown state, even though the valve is marked as SHUT.

Yep this appears to be an issue/bug with the APU shutdown process. Starting with the aircraft (v1.0.8) cold and dark w/ the default 6000kg of fuel in the left and right outer tanks: - Connect Batteries 1, 2, and 3 - Connect Ground Power - APU Master ON - APU Start ON - Wait for APU to spool up - Review APU LVARS: INI_apu_n1=100, INI_apu_PSI=10, INI_apu_RUN=1, INI_apu_egt=479.99, INI_APU_CONSUMPTION=300, INI_apu_available=1 - APU Master OFF. APU Running ECAM is removed. N1 starts decreasing until it suddenly drops to 0. APU N1 then proceeds to spool up again before announcing AVAIL. N1 falls to 31, EGT falls to 150. - Review APU LVARS: INI_apu_n1=100, INI_apu_PSI=3.15, INI_apu_RUN=1, INI_apu_egt=149.63, INI_APU_CONSUMPTION=300, INI_apu_available=0, INI_APU_SHUTDOWN_ACTIVE=1,INI_APU_SHUTDOWN_PHASE=0 - Review external CAM. APU exhaust heat effect and noise still active. - Monitor fuel level: Fuel continues to drain. It looks like there is a bug with the APU shutdown process where it never fully shuts down, and continues to drain fuel as if it's still running at 100%, while the exhaust heat and noise effect remain. Interestingly, using the EFB Panel State "Ready for Takeoff" will fire up the APU to start the engines before shutting it back down again. the N1 and PSI do correctly drop to 0, but the EGT remains at 150 on one attempt and 340 on another attempt. The heat and noise effect remains on the APU exhaust. Fuel weight in the left outer tank drops faster. Setting the EFB Panel State to "On GPU" or "Cold and Dark" appear to correctly reset the APU to the off state. No detectable fuel flow, no heat effect from APU exhaust.

Tried that departure a couple of times, and every time it flew it perfect. I even recorded my last one here, maybe you are doing something different? -