JonnyT1041

It might need to have the length of flight behind it. Will see if it occurs again but I'm not that keen on setting up 8+ hour flights with the intention of finding a wasm crash shortly before TOD

Attached log and panel image WASM crash occured after I loaded the SIKOU STAR to VHHX, no approach was selectable so I assume theres also an issue with navdata as Navigraph does include full navdata for VHHX. Would like these crashes to be fixed, since the 1.0.6/7 update 70% of my flights in the 350 have ended in WASM crash, previously it wasnt so high. Routing: VTBS - VHHX SELKA1R SELKA A1 SANOT Y15 GUROK A202 VILAO/K0887F410 A202 ASSAD/K0887S1250 A202 SIKOU/N0478F410 SIKOU13 RTX4070, Ryzen 7 5800X, 32GB RAM.

The behaviour in Go Around seems generally quite poor. Today I tested 1.0.7 at FAOR 03R using the ILS Z approach. On the first approach I went around around 500AGL using the soft GA (works quite nicely on a superficial level) However passing 7000ft the Missed App calls for right turn to 206. The aircraft simply maintained runway heading and climbed as usual. When I checked the FPL page, the approach had reset and the next NAV point was "Manual" which is not correct for a missed approach. Additionally, on the second approach I landed the aircraft before performing a second Go Around again using Soft GA. This time however the autobrake never disengaged, so the aircraft was at full soft GA power, whilst DECEL was lit up. I dont imagine this is how it works in reality so please confirm? I would assume upon application of GA thrust even on the runway you would expect disengage of AutoBrk?

This was the panel setup when the crash had occured. EDDM-FAOR is correct. ANF only on CPT side. ND was set to ARC

I've made a post or two in the discord community forum but here for officialness: Regarding WASM: Upon entering the ANF menu to plan BTV exit: WASM: Exception c0000005 in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Aircraft: A350-900 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: TURBU7S TURBU Y107 TOBSO DCT BAKOR DCT CHI DCT GOTMO DCT ALAXI DCT TEA DCT SOR DCT ROSAS DCT ADEXI DCT NIBLO/N0497F380 DCT ABRAM/N0498F370 N163 GRT A403 SHATI/N0491F390 A403 SEB M214 GARIN UG655 ILDOR UM214 IVDIG/N0485F410 UM214 OKLAP/N0488F400 UM214 ETMIT UZ35 ITROL UQ44 AVAGO AVAGO1D if related to FMS/Route Procedures crashes WASM Error: WASM: Exception c0000005 in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Specs: Ryzen 7 5800X, RTX4070 and 32GB RAM. Regarding FBW Rudder, NAV in Go Around, ground roll FMA glitching: https://youtu.be/Wc0fuUod4Qw FBW Rudder: Seems very commonly out of coordination during roll, with and without autopilot engaged. Can be seen quite clearly at the end of the video. Lack of rudder coordination - sluggish turn rate and "delays" to input (I think this is what people are feeling without knowing its the adverse yaw). On Go around, the aircraft deletes the turqouise line and follows a weird track not sure where to, but definitely not the standard missed approach procedure that is associated with the approach just performed. Additionally during ground roll, FMA freaking out between G/A, soft GA and roll out. https://youtu.be/Wc0fuUod4Qw