frank_m

I think you are doing something wrong with the code tags.

This is an English speaking forum.

Did you already start your engines before pushback?

As soon as you have activated 4x in the EFB, you can increase the sim rate further using the assigned keys for sim rate.

This means, your system is overwhelmed. If the system can't maintain a stable FPS with high sim rates, it is decreased. You have to reduce settings in order to use higher sim rates. I can use the A350 up to 4x all the time, and during cruise even up to 8x.

Yes.

I refuse to read the text until you remove the nonsense with the code tags.

This are missing textures from the plane or the livery. You should do a clean re-install of both.

This is the mistake. You can only program DIR TO waypoints out of your flight plan.

I'm not using the package reorder tool, but tr0mb0n1st does. I'm adding the package_order_hint entry to my add-ons.

This is most likely a wrong configuration in the controls. How are Rudder and Tiller Axes configured, and what is in the EFB set regarding Rudder, Tiller and Auto Disconnect? Please show screenshots.

Are you using Navigraph Navdata in the Simulator? Then it is most likely the package_order_hint problem. There was a similar issue a few days ago. Please look at the Navigraph Forum for details. Long story short: you are using old MSFS2020 addons lacking for the package_order_hint entry in the manifest.json. This disturbs other addons, although the critical addon itself works flawlessly.

For me it works perfect in SU5. Have you analysed the CTD in the Windows logs?

Yes, EVERY single addon. As I said, an addon don't has to be active or in use. It is sufficient if it is available in the community folder.

No, it is not the Navigraph integration. It is the "package_order_hint" problem. You have at least one addon not compatible with the FS2024 in your community folder. It has no package_order_hint entry in its manifest.json. This leads to addons sorted and applied in an incorrect order, and the Navigraph navdata does not work like expected. The addon don't has to be active or used in the current flight, it is sufficient, if it is in the community folder. Also the addon itself works flawlessly, but it distubs others. There are many and long threads in the Navigraph forum dealing with this problem. Long story short: You have to ensure, all your addons have an appropriate package_order_hint entry. Either by using only addons released for FS2024 or by adding the entry yourself.