
ElCaramba
Member-
Posts
19 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
ElCaramba's Achievements
3
Reputation
-
See attached video Aufzeichnung 2025-04-05 171057.mp4
- 1 reply
-
- 1
-
-
I performed a go around procedure at EDDP. After having retracted the landing gear and re-enabled auto thrust and AP1, the plane took an right turn off the caluclated route, the ETP was somewhere in the middle of nowhere, although NAV mode still had DO55U as the next waypoint and estimated to be off the route about 30 Nmls to the left....
-
I have found multiple autopilot / FMS bugs: 1. Although at the target altitude (3000ft), the ND still shows the level off arrow along the planned route (being fully automated flight with NAV and ALT active): 2. ETP calculation: I found the ETP being falsly recalculated on two occasions: One after I inserted an "Direct to from P. POS" the ETP show up in the middle between the P. POS and my destination, the other one strangely more or less on the thrashold after having performed a go around. 3. The level off arrow showed up even behind a --MANUAL-- Discontinuity - how would it know when I was going to turn und hence when to reach the target ALT?
-
Hi, I just wanted to get your opinion on the spoiler impact during descend. During descend (-3500 ft/min, 35.000ft) I found myself slightly accelerating, so I decided to deploy 1/4 spoiler, just to find the airplane strongly decelerating. The Fenix decelerates a lot less compared to the A350 with spoilers deployed, so I wondered if the spoiler effects are somewhat too strong. Interestingly, 1/2, 3/4 and 1/1 spoilers don’t add that much deceleration (not linear). Opinions?
-
Hi, that’s what I ment. The Fenix doesn’t show any distance at all, so I guess it should rather show no distance than 0.0nm.
-
On the EDDH RARUP5S arrival, plane reads the ILS identifier (IHHE), but distance constantly shows 0.0 nm all the way down to touchdown (see screenshot attached).
-
investigating A350 ARPT NAV NOT AVAIL (NAVIGRAPH)
ElCaramba replied to Sebastian M's topic in Systems
Is this being fixed already? Still getting this in V1.0.4. -
Same issue here.
-
Once you have entered a hold, the MFD / FPLN shows an "IMMEDIATE EXIT" button on the FPLN page. After having it pressed, the plane should directly (and immediately) turn towards the holding point from which it should continue the planned route. However, the Inibuilds A350 contiues on the holding pattern until it reaches the holding point and only then continue on the planned route. Please fix. Additionally, the VD shows strange vertical profiles (see below) and somehow displays the fix name (INPUD) and the hold (HOLD R) overlapping (see pictures below).
-
I am not 100% sure, but is the lateral flight path supposed to extend way up to the upper border of the display and overlap with the written information?
-
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
-
-
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