Good morning, I’m here because, like all of you, I’ve encountered the same problem and can deduce that the cause is definitely the AMD 9000 series or its drivers. I’ll add some information that I consider essential: I switched from an RX5700 to an XT9060XT just a week ago, and before that, I had no problems with the RX5700, while with the XT9060XT I noticed a graphics bug just yesterday because I hadn’t flown at night yet. The graphics bug appears when the cockpit lights come on, so it must be a lighting issue. I see that this problem has been around for months without a solution, unfortunately. I should add that the sim version is the latest official one, not a Beta version. I hope AMD fixes this by now. Regards.
Hi. Just one thing regarding your conclusion that some others also seem to have forgotten. If you go back to the beginning of this thread, you’ll see that this issue did not exist prior to the release of SU2 back in mid May. There were no night light artifacts with SU1 and so no issue with the 9000 series or AMD driver (25.3.1) at the time. Only started with the SU2 update and whatever change Asobo made that they still have not yet identified.
Yep, actually it started the very first week in April in the SU2 beta release. That is when @Kubajs2011 created this thread and others began to experience the same issue. Asobo ignored those complaints and released SU2 for all May 15th and its existed ever since.
They didn’t ignore it, but they where too silent about updating us.
The lighting system got a big overhaul and that needed to be checked first and the engine devs concluded it was almost certainly a driver issue (new card new hardware libraries and probably new issues also) Asobo has access to MS (Directx) AMD/Nvidia/Intel so we can be sure this is well checked before making such claim.
If it is ‘planned’ for SU4 then that almost confirms it isnt a driver issue, but a game issue. So my scepticism about microsoft palming it off and shirking responsibility was correct.
Disappointing to see people still insisting it must be AMD as its is a newly released card or something. Especially when I have had it working on this new card without artefacts, on drivers it now produces artefacts on. Hopefully now microsoft have quietly assumed responsibility we can now focus on it being fixed. Ideally its fixed in an early (or the first) beta of SU04.
It actually changed a couple of releases into SU2 beta, which involved no lighting updates. SU1 worked on the 9000 series cards and initially SU2 beta (you could initially rollback to SU1 to fix the artefacts). The drivers it worked on in SU1 and SU2 now show artefacts.
So the fact it was working until a microsoft update, and they have included it in their list of bug fixes, makes me confident they have discovered its an issue their end.
It would be nice if on the next dev stream they explained this instead of just sneakily adding it to the dev log.
It was working until the new lighting update. Does it matter at what specific patch it was? You never got it working with the new lighting on Windows, that is what I was referring to.
Again, why would it only happen on 9000 series if it is Asobo’s problem on Windows? As I said before, it works perfectly fine on Linux with official AMD drivers which are ahead of Windows drivers.
Hey everyone, I started flying again and noticed the same visual bug. Initially, I thought it was specific to the Fenix A320, but I encountered it with the MS A330 as well. After Googling, I ended up here. I’m using an AMD Radeon RX 9070 XT with a Ryzen 7 9800X3D, and the issue persists. Is there still no fix for this? Also, what’s the difference between running the game via the Xbox app versus Steam? Thanks!
