frank_m

Well, I have a Co-Pilot as well in the -900 and the -1000. Sorry, the images are made in HDR and look too bright. A350-900: And A350-1000: I did not know, that you can do something (wrong) in order to let them disappear.

Well, first question: why are you setting the speed manually and are not in managed speed? And: you are too slow and set the speed manually even slower. Why? But in order to evaluate the problem we need to see your settings and configurations, also in the beginning of the flight.

You are far too slow, and your speed setting is even slower. Why?

You mean automatic tuning if the ILS frequency? It worked for me around 1 hour ago with SU4.

Switch on the wipers.

1.0.5 or something? I'm using it for a long time now.

That has already been fixed several revisions before.

I had never a problem with 8x, even before SU3. Ryzen7900 and RTX4080.

The workaround mentioned above has nothing to do with nVidia or AMD. It is a setting in the developer mode of the simulator.

That is a problem of the controls, most likely a double association of a key.

Thats a complete different problem. It has an own thread in this forum.

A setting. Just switch it off. They have been adjusted for the ULR Variant. Outdated liveries cause max 7 hours flight time.

Yesterday there was no issue. So either Simbrief has a problem today, or you are doing something wrong.

I did today a flight to EDDM 26L RNAV approach. No issue. I'm using Navigraph Data in simulator as well as in the A350.

I think, it is more likely an issue of the scenery.

I do sometimes long haul flights > 12 hours Block Time in 4x or even 8x (e.g. Munich -> Tokio). No issue here.

It is described in the GSX manual, when the passengers are visible and when not. There are several different trigger conditions (e.g. signs).

Seems, you have CFD visualization active. That is due to incompatible liveries. Use updated liveries directly from the inimanager.

It's easy. Please take into account, that this setting will influence the performance, since all objects will be fully drawn all the time.

Just a few minutes ago I have opened a thread describing the same issue: The workaround described there should help for the time being.

Hi everyone, In SU3 1.5.25.0, the new LOD curve has also been activated for VR. As it is a significant improvement, I am fairly certain that the curve will be included in the final version of SU3. Unfortunately, there are some problems with the A350 v1.1.3 and the new LOD curve in SU3 1.5.25.0 in VR: Several objects are invisible and therefore unclickable. It is impossible to start the plane due to the invisible battery switches. Please see the attached screenshots. By the way, activating 'Debug Model LODs' and setting 'Force LOD 0' shows all objects and the plane becomes operational. I think it would be worth addressing this issue in good time; otherwise, there will be a lot of complaints as soon as SU3 is published. Regards, Frank

It IS a performance issue. The A350 needs more computing power than other planes.

No, BATC and the A350 are harmonising perfectly.

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.