Skyrock

Did they at least fix the Time bug where it's showing an ETA in the past for the next waypoints? I missed that in the changelog...

A fixed derate is useful in cases where you need to lower Vmcg (Minimum control speed on ground) and subsequently V1, e.g to increase your performance limited takeoff weight on short and/or contaminated runways. On for example contaminated runways, Flex takeoffs are not allowed, hence you would only be able to do TOGA takeoffs. The main problem in these cases: if you have an engine failure. Now, you have to have a higher VMCG and V1 in order for the rudder to have enough authority to counter the asymmetric thrust during an engine failure with TOGA power. With a fixed derate, in case of engine failure, the remaining thrust on the operative engine remains at the derated thrust level. It's actually prohibited to advance to TOGA with a fixed derate (unless during a windshear or if above F-Speed), because it might lead to a control loss. Therefore, with a fixed derate there is lower asymmetric thrust and with that, the VMCG/V1 can be lower since the rudder can achieve enough authority to counter the moment by the asymmetric thrust at a lower speed. The Performance Limited Takeoff Weight increases in those cases. Most of the time, your takeoff performance calculator will still present a Flex temp and only in rare occasions (like contaminated runways) it will provide a fixed derate. On Boeing aircraft, a fixed derate and a flex (here called assumed temperature) can be combined (e.g TO-1 42°C), so in case of engine failure by pressing the TOGA button, only the assumed temperature would be removed but the fixed derate would remain. On Airbus aircraft, a fixed derate can not be combined with a Flex, so it's either one or the other.

And it happened again...this time (yes I said I wouldn't do it, but I did anyways) enroute from SIN to JFK, after 9hrs over the pacific. I was not doing anything (again) and everything froze. I forgot to check the console for the WASM crash, but at least this time I managed to save the last autosave. The WASM crash or display freeze happened about 10min after the autosave... I'm done with this. Uninstalling the A350, will revisit next year or so. It's way too frustrating (despite the autosave feature) to always be waiting for the WASM crash to happen. But I'm not willing to deal with this anymore 1757833492.bin

Same. Yesterday I did SIN-SYD without any issues so I was kinda hopeful that I could do SIN-JFK tonight. But nope, not under these conditions. 50% reliability is not enough...

Hello, Aircraft: A350-1000 Simulator: FS2024 Navdata: Navigraph OFP: included Specs: CPU: AMD Ryzen 9800X3D, RTX 4080 Super, 32gb RAM Autosave: unfortunately already deleted. WASM: apparently none? I'm currently enroute from SYD to SIN in the A35K and after about 2hrs, overhead Alice Springs (AS), my displays froze completely. Why did I not write "WASM crash"? Because apparently there was none. According to this screenshot: I don't know whether this helps to trace down the issue or not. This was the only error shown. I was not doing anything, in fact, I was laying on my couch and realized that the time in the ECAM had stopped 30min prior and with it all other displays. The ND was showing me going offtrack though before it froze. I was cruising at FL380 using Sayintentions. I merely just realized because my FO kept checking in with new sectors despite CPDLC not showing any handoffs or messages apart from the usual "connected". At this point the A350 is just frustrating for me. Every 2nd flight I get a display freeze (WASM crash or not, idk) and despite the autosave feature, it kinda ruins the experience. Last time I got it enroute from EDDF to WSSS after 4hrs into the flight. Unfortunately I didn't check the log. I attached the OFP just to be sure. VS119_SYD_SIN.pdf

Had the same. At some point, waypoints that were 20nm in front of me where shown with an ETA 2,5hrs in the past and were only updated after overflying said waypoints. After 4hrs then, I had a WASM crash. Unfortunately I didn't check the cause. After loading the autosave, the ETAs for the next waypoints were correct.

Hello, when flying in south east Asia, there are currently (and also in general, but especially now) really high OAT at altitude. You can generally observe ISA+20 temps up there. Still, the OPT FL shows FL up to FL380 and higher even though the climb performance is abysmal, even with CLB and no Auto-derate. Is the OPT FL even taking the OAT into account? Best regards, Martin

Do you actually read the posts before? They fixed it.

https://forum.navigraph.com/t/inibuild-a350-not-working-with-last-2506-rev1/19892/6

From Navigraph Forum:

Hello, I was flying 8h16min today from YPAD to VTBS today with the A350-1000 and 300 pax, so far from full load and after around 5-6hrs the water tank was empty while the waste tank is full. This seems rather excessive given this is an aircraft that can go 16hrs+ nonstop. Maybe you can check this out and refine the passengers biological needs? 🙂 Thanks!

Hello, so this is a longer one, but bear with me... Since I got the A350, I observed a strange behavior when it comes to Fuel Burn with different CRZ FL. Usually I plan my flights as close to the OPT FL as possible and even wrote down most of the OPT FL from the FMS since Simbrief is often choosing lower FL than the OPT FL would be. With this, I usually arrive with ~1t-1.5t of fuel more than what Simbrief calculated, so less fuel consumption. Today, however, I was flying NTAA-YPAD with a friend. He was flying the 350-900 and I used the 350-1000. Due to strong headwinds enroute, we figured it actually makes sense to fly at FL340 all the way which would've saved ~15min and around 400kg of fuel according to the calculations. Simbrief suggested 360/380/400, with my OPT FL it would've been 380/400. ZFW 186.2t in the -1000. After T/C my FOB was already 1.5t lower than calculated and I was 4min behind schedule. Then I went into my crew rest and when I got back 6hrs later, my FOB was a whopping 6.2t lower than calculated and 11min behind schedule! I decided to climb to FL400 then to save some fuel. At the same time, the cruising speed did not match the Simbrief profile. After reaching T/C I was flying at Mach .85 (Cost index 30) which matched Simbrief, however, after I came back from my crew rest, I should've been cruising at Mach .83 according to Simbrief but I was actually going Mach .80. My friend was going as slow as me and had lost 2.5t in the -900. We both use the standard Fuel Bias, so 0.0 for the -1000 and +3.0 for the -900. The weather can be ruled out as the enroute winds/temps matched the forecast pretty well. So, to summarize, in my opinion something is very off with fuel consumption and speed at different levels and is disproportionately diverging from Simbrief the higher or lower you go. Below FL350 you burn a lot more than what Simbrief calculated and above FL370 it is significantly less. I think the problem lies with the 350 rather than the Simbrief profile as the profile makes sense in my eyes. I'm using version 1.0.11 in MSFS2024. I would appreciate if you revisited the Fuel flow and cruising speeds for further refinement! 🙂 Thanks for reading my ted talk.

When turning on ALT RPTG, then the TCAS STBY message goes away. However, I fail to see any traffic on my ND (I selected TRAF and ID but neither of them showed anything). This is on sayintentions and I'm flying with a buddy who is 15nm away. Can't see him

Hello, so in my experience, v.1.0.6 has been the most stable and enjoyable version so far. Now with 1.0.7 I have this weird CG issue where the CG is way too much forward (FWIW, I never suffered from early rotations in earlier versions) and I also experienced a display freeze after 9,5hrs (weirdly without any WASM crash logged). I would appreciate to having the possibility to downgrade back to 1.0.6 or have a standalone installer, especially when the next update is going to take a while to fix these issues. Would be great if you guys considered it! Thanks

Hello, as the title suggests, the Before Takeoff Checklist asks for Packs set to off even if I set them to on in the Performance page. Can you please check? Thank you! Best regards, Martin