Tim Cui

This bug was introduced in V1.2.1 and still remains unfixed in the latest V1.2.6, and I have no solution to it. After entering weight data, the 90-degree right-angle turn route between AA263 and AA262 deviates during rendering, and the autopilot will follow this offset path in full managed mode. Even removing speed and altitude constraints of this waypoint cannot fix the issue. This problem exists in SID and STAR procedures at many airports.

But this can be treated as a low-priority fix, since I’m not familiar with how the A350 behaves in real life either. Thank you for your reply.

I asked my friends today and also checked the NOTAMs — in reality, the route is indeed flown directly without passing those waypoints. However, shouldn’t the LNAV’s improper handling of two consecutive turns be something that the development team should pay attention to? I’ve flown the same route with other aircraft before: although they deviated a little, they were still able to correct themselves and return to the proper path. But the A350 kept circling continuously. I believe this is an issue with the coding.

Hello everyone! For two consecutive days, I have encountered a situation where the aircraft's LNAV malfunctions and keeps circling repeatedly between the ORAVA and UNSEK waypoints (as shown in the figure). Other pilots have also informed me that they have encountered the same issue. Could the cause of this problem be incorrect LNAV coding or something else? Everything in the aircraft cockpit is normal with no alarms whatsoever— the only issue is that the LNAV is not following the planned route.

As described in the title: if I change the flight direction and set a StepClimb in the FMS to descend from FL390 to FL380, can AutoStepClimb execute this operation automatically? Additionally, if I switch from metric RVSM to imperial RVSM and need to descend from FL371 to FL370, can AutoStepClimb complete this descent process?

Is there a cabin paintkit available for the A350 V1.1.8? Ever since the release of V1.1.7, the previous cabin seat textures have become unusable due to model changes. I’m currently struggling to adapt those old textures to fit the latest version, but I’m facing difficulties. Is there any good method to make them compatible, or perhaps a more complete set of paintkits that I could use?