ElCaramba

Aircraft: A350-900 Simulator: FS20 Navdata Method: NAVIGRAPH OFP: EBBR -> EDDM Specs: Ryzen 3900X, RTX 2080 Ti, 32GB RAM WASM: WASM: Exception c0000005 CommBus callback in module m178088ef2d4800fa V1.0.3, TCAS STBY, XPDR ON [Coherent GT] Failed to locate file vfs:///html_UI/Pages/VCockpit/Core/WasmGaugeLiveView_6 [Coherent GT] Failed to locate file vfs:///html_UI/Pages/VCockpit/Core/WasmGaugeLiveView_7 [Coherent GT] Failed to locate file vfs:///html_UI/Pages/VCockpit/Core/WasmGaugeLiveView_1 [Coherent GT] Failed to locate file vfs:///html_UI/Pages/VCockpit/Core/WasmGaugeLiveView_0 WASM: Exception c0000005 CommBus callback in module m178088ef2d4800fa WASM: callback execution for event NAVIGRAPH_FunctionResult, in module m178088ef2d4800fa, failed

When switching from the SURV page to the C/L Page and clicking "C/L complete", the MFD Page switches back to the last page opened before the C/L menu, but the dropdown stay in C/L menu

Climbing out of EBBR 25R SOPO3K departure, VD shows weird climb path (see attached screenshot).

Plane froze during the approach preparation. The plane itself kept flying and even kept track on the ND, however I wasn't able to look around or push any button or turn any wheel. WASM crash report (errors): [Coherent GT] Failed to locate file vfs:///html_UI/Pages/VCockpit/Core/WasmGaugeLiveView_15 [Coherent GT] Failed to locate file vfs:///html_UI/Pages/VCockpit/Core/WasmGaugeLiveView_14

Deactivate the AI auto trim in the settings. After doing so, restart the sim. It then should start aroung 24.5% and then trim one you start the engines.

Correct me if I am wrong, but the Autopilot seems not to be too precise in terms of keeping speed and often altitude during climb and descent. During cruise it seems ok. Example: I found the speed to be off the AP Input by a couple of knots quite often. The airplane seems to be trailing behind the commanded speed. Also, during descent, I found myself being about 1.000 ft above the vertical profile, however the AP apparently descended with the calculated rate and kept that 1000ft deviation (until it eventually cought up at a alt constraint along the route) instead of trying to be precisely on the vertical profile and descending just a little faster to get back on the profile. As you can see in the picture below, the speed is not going anywhere although the plane is slightly slower than it should be. Unless that’s for some reason the real world behavior, I guess that’s a AP bug. The Fenix for example is much more accurate in that regard, I assume that’s the way it should be.

Also, even connected with the Navigraph account, Airport Map is not available. Using 1.0.1 version.

When during cruise in plan mode while being in the temporary flight plan (e.g. after entering the arrival route), the ND and the MCDU show the full route, even the waypoints already passed. However, when browsing back to waypoints already passed, the ND shows their position along the route, but all are named as the waypoints already passed you are currently flying away from. Example: Enroute from waypoint MAPOX to SPY, I can browse back along my route (in TMPY FPLN) even to waypoints already passed, but they all are named MAPOX). Also, when centering on a waypoint before MAPOX, the route shown on the ND (green / yellow mixed line) toggles somehow as if the route was constantly being recalculated. Besides, my EFB stopped reloading the IFR Enroute map. Apparently once I was out of the map sector being previously loaded, the map is not being updated anymore. The little pink airplane moved out of the map and now flies peacefully over a black background…. Changing the map (VFR, World etc) and changing the zoom factor didn’t change a thing.