frank_m

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.

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

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

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

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.

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.

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

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

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.

So you can tune the radio, but you can't communicate? Also, if you manually tune the radio? If the frequency is shown, the radio is tuned. So it seems, you don't have an issue with tuning, but with communication. Right? BTW, it works with BATC, so it is most likely not an issue with the radios, but with the ATC.

The waypoint is next to you on the right side. There IS a need to make a turn.

You are too fast and too close at the next waypoint. The Airbus has to make a sharp turn to reach the next waypoint and is then at the wrong angle for the following waypoints. To solve the problem short way use a DIR.TO to VEBIT.

Same happened today at EDDM for me.