Yes, there are still problems with Radeon cards. And yes, they show little interest in fixing them. And yes, we will politely keep pushing them to be looking into those problems, especially since the problems manifest very clearly with the default aircraft without any add-ons.

So, pray tell, why are you still here? :D

Lefteris, allow me a quote: "I am noticing a strong tendency for a couple forum members here to be re-posting the same very unhelpful remarks." With all due and considerable respect, I see the same questions, that have been answered over and over again, asked in these forums, and not only...

You can't. It makes no sense to keep a version around that has known bugs that are resolved in a later version. Jorgen Not if those bugs are worse for customers than the previous bugs that people weren't even having issues with. I'd take a yellow horizon any day over a sim which might at any given ...

Alas, I am not the developer of Prepar3D so I don't have access to source code for it - and that's where the problem lies. I am sure Rob McCarthy or Beau Willis will find ways to figure this out, but for that, they need to actually allocate developer time to the issue. I understand that AMD card use...

Dear Vaughan, I appreciate your feedback. Thank you also for your report that it does not happen with NVidia - obviously, if it happened there too, the topic would not state "AMD Radeon artifacts" :D This is something that Lockheed Martin need to address. It happens regardless of aircraft ...

Even after the release of 5.3, the issue remains. We have posted several screenshots of what the issue is exactly but the P3D development team is paying no attention to it. If there are more AMD graphics cards users here, please add your voice to this post so you can be heard - we have customers com...

I replied to that link that there's no need to uninstall - simply update to latest version. Use FSL Control Center, switch to Experimental channel, presto.

StewCAl wrote: ↑Thu Dec 02, 2021 4:49 pm I'll have to give that a try when I get home from work...Maybe FSLabs will have an update by then...

Thanks!

Steve

Please use our FSL Control Center, switch to the Experimental channel (through Settings) and update to v183 of Libraries and the A320. This will bring compatibility with P3D v5.3.

While not saying the top image is what I consider best, I have to admit the bottom one looks way too blurry for my taste.

We've posted this time and again until we're blue in the face, but nobody is paying much attention apparently. There *IS* an issue with AMD cards, evident VERY clearly also in default aircraft. Beau was in this thread, the easiest thing to do is get an AMD card and try it. 2D panels will show exactl...

Have you asked FSLabs about this? Jorgen, our products only use the SDK-suggested way of adding/removing an add-on, that is the invoking of P3D with the appropriate command-line parameters through the installer. The user should look into why add-on.xml is not being changed by P3D itself - usually a...

You are asking me? :D This is a question directed to LM!

We have long complained about this issue. It's evident in default aircraft as well. We posted a topic on this awhile ago.
It's an AMD issue for sure - it's only evident on AMD cards.

Those settings didn't make a difference either. To clarify: There is no problem starting Prepar3D or going into the sim itself, if I click "OK" in the starting preview window. The sim will start fine and go into the 3D to fly. It's when trying to change airports where the issue occurs. P3D...