Tveo

Hello, my contribution to the matter: In the last two days, I obtained two CTDs with the combination of this aircraft + FLSTL activated through its injector (not through BATC). I must say, I hadn't obtained CTDs in the system for many months, almost as many since I installed the simulator, MSFS2024. In my case: - Flight from TLS - DBX: 8 hours without CTD Followed: - Flight DBX - AKL: CTD at 9:47 hours It was stopped for almost 4 hours until I realized (seen in the Pegasus client of vAMSYS). I started MS24 WITHOUT ACTIVATING FLSTL this time, and in the air. The aircraft has its systems in C&D, so I couldn't activate the save through the dashboard. Ok, I started a new flight on a runway near the CTD location with the engines running. Everything's up and running, and I activate the last autosave via the tablet. Less than 15 seconds later, I'm in the air, and everything is proceeding normally except that the PA is in HDG mode and the EFB flight plan has disappeared (a minor issue). I activate a direct to the next waypoint, and the plane heads off. I didn't have to do anything else on the plane. Well, yes, I had the arrival runway entered in the MCDU with its STAR... and I think this is why the TOD was lost from the flight plan, but a simple descent calculation resumed the descent in managed mode at the calculated point. I landed at AKL almost 6 hours later without further problems. - Just today, in fact, a few minutes ago. Flight MAD - NRT. New CTD with FLSTL active this time, at 6:58 hours. I restart the flight on the nearby airport runway and activate the last save without FLSTL activated. Just like the previous flight, less than 15 seconds, and I'm in the air at the same point, so much so that Pegasus doesn't detect any route changes. Everything is fine, fuel consumption, route, etc., except for the minor EFB details mentioned earlier. Now, this time, I haven't missed TOD because I didn't have an arrival runway in the flight plan. Just to test, I activate the runway, STAR, and APP, and... if the TOD appears. I still have about 5 hours of route time left to arrive... if I arrive. I mean, FSTL has something to do with it... although on one of my flights, having it enabled wasn't a problem, on the other two, there was CTD. My next flight, I'll fly without FLSTL from the start... whether or not the theory is confirmed. PS: the autosave works VERY well.

The same thing is happening to me, but in my case, on the ILS W 32R approach to LEMD. In this case, the ILS information appears correctly in the NAV section of the MCDU, including both the frequency (109.1), the identifier (MBB), and the heading (323 degrees). In the ND, the frequency and ILS indication appear in magenta, but the magenta diamonds for LOC and GS are never present, nor is the DME distance. In other words, everything is correct, but the signal is not being received and, therefore, the signal is not being intercepted. I must say that I have tried manually entering the data, including the frequency, identification, and heading. Nothing works. I must also say that I have detected this, at least in my case, since version 1.0.3. When version 1.0.4 came out, I deleted WASM, updated the Navigraph data with my subscription... I did a test flight and everything worked on that same ILS, but today, after I just arrived on a new flight, it's down again. I haven't done anything different or updated anything from the flight I took yesterday, where it did work. Finally, I did the test with it and that ILS works perfectly with other aircraft, like your A300 and the Fenix A320. I fly a lot out of Madrid for Iberia Virtual, and it's a widely used approach daily with all of these aircraft, and none of them show errors except for the A350, so it's not a scenario issue. I've also seen with other colleagues that it's very random, meaning it works for some, and not for others. I don't know which version they fly. In my case: latest version of MSFS24, W11, updated Navigraph, and aircraft version with the latest update 1.0.4. If you have any additional questions or need additional screenshots, please feel free to contact me. P.S. I'm sending you some screenshots (number 1, 2) where you can see what I'm explaining and where it doesn't work correctly. I'm also sending you a screenshot of the test I performed after recently deleting WASM and installing version 1.0.4, where you can see that it did work and received a signal at over 25nm.