frank_m

You are way too fast. You should observe the constraints of the Charts: 220 kn are allowed, you are flying > 300. It is clear that the aircraft has a much too large turning radius under the edge constraints and cannot possibly make the approach. And no: you cannot rely on the flight plan to have entered the appropriate constraints if they do not refer to a specific waypoint. It is up to the pilot to reduce speed in good time.

It is a texture loading problem. By the way, there is a workaround in 1.2.0, so it works for the time being.

The issue described in this thread is no WASM crash.

Since it does not happen very often, there is an easy workaround and the reason behind it is a simulator issue, it is really no showstopper.

I never head this issue.

As it is mentioned in the known issues.

That is mentioned in the known issues.

There is obviously an error in the flight plan. You are flying from DUGDA to CALVY, then backwards to SILTO and finally to ONTOK. 🤪Of course, the plane is making circles in that case. Two 180 degree turns on short notice - this won't work. You can see the colors in your plan, STAR and APPROACH are overlapping. Maybe you have chosen a wrong transition?

Just use the search function:

Which platform? On PC the A350 and SU4 are perfect partners.

Please follow the instructions for a WASM Crash.

Please read the Release Notes: There are no cabins from 1.1.7 onwards. And you should uninstall them, as they cause a lot of trouble (invisible plane and cockpit).

Low-res textures are meanwhile standard. So topic closed.

You can fix it like all others with the same problems. Its described at least 10 times in the forum.

Most likely still the same as in all other threads regarding this question.

When the "Shift+C" is shown to enter the plane, just wait a few seconds till the plane and all ground equipment is fully loaded and enter then the plane. Afterwards it works reliable.

what is your setting in the OIS for the start configuration of the plane? Maybe Cold&Dark?

Seriously? There is less than 18 GB free space on your hard drive? You are aware of the fact, that you should have AT LEAST 25 - 30% of free capacity on an SSD, so the wear levelling can work efficiently? So, buy a new SSD. Or clean up your storage. The simulator with addons needs several hundred GB. BTW, the a350 needs 15 GB on the hard drive, and the download archive is 5 to 7 GB. So in total you need around 22 - 25 GB free space for installation. And as I said: Never less than 25% free capacity on a hard drive.

Where did you buy it? Maybe the plane is streamed in MSFS2024?

Rollback is not possible. Just use compatible Liveries.

You are surprised, that a MSFS2020 addon disturbs the MSFS2024? An Addon, which even the provider recommends not to install in the 2024? Really? REALLY?

Ok, then I think, I know, what happens. LT and RT are both analogue axis, so you can assign them to the tiller. BUT: LT only steers to the left, while RT only steers to the right. Since you can assign only one axis to the tiller, you will only steer in one direction and have no chance to put the tiller in neutral position again. You need a control with a regular axis, preferable one, that returns automatically to neutral position for controlling the tiller.

Which Controller do you use? What is the "normal" stick? On my controllers are 5 "normal sticks". Assign an analogue axis. "Shoulder button" sounds for me like a digital input. This will not work of course.

That is for sure a problem in your controller configuration. I use a dedicated axis on my controller for the tiller moving back to neutral position automatically and have no issues. Maybe you assigned not the analogue axis but the button event of your axis?

SU4.