frank_m

That was a GSX Bug. There is a hotfix available for 3.6.4. Just click "Check" in the FSDT Installer.

I another forum I have read today, that some pushback toolbar or addon caused the issue.

The inimanager and the simulator are both using the same paths? In the inimanager you can now configure an install path and a community folder separately. You took that into account?

What was the solution? Please consider how other users with the same problem could benefit from your solution.

There are several WASM folders. You have to find the right one and delete it. That is senseless. Is the navdata for the flight plan, the simulator and the plane consistent?

Reinstalling won't work. That does not delete the WASM folder. You have to find and delete it yourself. In the Screenshot above everything is fine. If you have a problem, you should post a screenshot from the problem, and not one when everything is perfect.

As I said, don't do that.

If you use translation tools, you should correct the output. Yeah, that could be the problem.

I did a flight today using GSX, and everything worked flawlessly: fuel, catering, cargo, boarding. Are you sure, you did not sync the loadsheet before using GSX?

Can't confirm. I did it today. EDDL->EDDB, with GSX and BATC. The plane worked flawlessly after pushback.

Have you linked your Navigraph account in the A350? Is the Navigraph subscription detected?

Please show screenshots. I have never observed missed constraints.

You are right, there are no dots, but the dashed lines for spd and heading show the managed mode. And in managed mode the A350 observes all constraints. I did a flight today, and it worked perfectly. In the MFD you see the upper and lower constraints of each waypoint and the descend path observing it.

Yes, it has. And if everything is programmed correct, speed and heading are dashed. Of course the A350 calculates the descend path in an optimized way, but it observes for sure all constraints. If you do not have dashed speed and heading displays and the plane is not observing the constraints of the flightplan, then the MCDU is not programmed correctly.

If the flight plan is correct, the A350 will of course observe waypoint constraints in terms of both altitude and speed. I have no problems with this, even with the latest release. Please provide screenshots. If your glareshield shows no dashed lines for speed or heading, then the MCDU is most likely not programmed correctly. Perhaps the PERF setup is missing?

You must activate vsync in the graphic driver. It is not possible to activate it in the game. And you must save VRAM, in the game and by closing external VRAM consumers.

16 GB VRAM is tough for large Airliners and complex airports. Save VRAM by using low-res textures and close all other apps using VRAM. It depends heavily on your Monitor setup if you see stutters or not. Ensure a proper freesync/vsync setup, that is crucial.

I just did an Autoland in EDDL without any issues. Decelerated Climb active?

Maybe this is the Navigraph issue already discussed in this forum?

Do all your addons have a correct "package_order_hint" entry? If not, this may lead to missing STARS, SIDs or erroneous ILS approaches.

Of course it uses more resources than a GA plane, but compared to other large airliners (Fenix, FBW A380, ...) it is on the same level. FBW uses even more VRAM.

Do all your add-ons have an appropriate "package_order_hint" entry in the manifest.json? In particular for add-ons not designed exclusively for MSFS2024 this entry is missing very often. In this case the Navigraph Navdata is not working correctly, missing SIDs, STARs are the consequence, or ILS is not working any more. So make sure, ALL add-ons have this entry. Details and the technical reasoning behind it can be found in the Navigraph forum.

I have today performed a flight from EDDL to EDDM 08L and had no issues with ILS. Of course without Navigraph Navdata.

I can also confirm the issue.