I don’t think so, because if I switch off all interior and turn on landing lights, it also happens and it also happens around all objects, not just the plane (pushback tug, jetway, etc.) and around the plane body. It has something to do with lights in general.
Hello, same problem here, with a 9070 XT as well. I think it’s related, everyone experiencing these issues has an AMD 9070 GPU …
I did a topic too with a video : [VIDEO] Graphical bug with multiple artifacts and high GPU usage, but only at night...?
I’ve tried everything as well, and the only thing that works for now is to revert to SU1. Unless we wait for a fix, I don’t think there’s much else to do.
Let’s hope they will fix it before it goes live, but I don’t have much hope.
ISSUE DESCRIPTION
Description of the issue: Hello, before starting, I want to clarify that this bug occurs only on the SU2 beta, i have with no issues on SU1.
In-game, when it’s nighttime, I see multiple graphical artifacts appearing outside and sometimes even inside the cockpit. These artifacts are visible around the “edges.” I’ve tried changing many settings, including anti-aliasing, but the problem remains.
In addition to that, only at night, the lights flicker (a known issue), and I experience severe display problems, sometimes heavily impacting the GPU (see the video, I drop to 5 FPS).
Did you experience this issue before you joined the Beta? : No
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes and yes
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)? : Each time at night
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
- Launch the game
- Be at night
What peripherals are you using, if relevant:
i5-14600kf
64 Go of RAM
SSD 1 To
Reaper 9070 XT 16Go VRAM
[PC Only] Are you using Developer Mode or have you made any changes to it?
I tried with and without
[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:
Driver ok
MEDIA
Please add a screenshot or video of the issue occurring.
A little video 
[END OF FIRST USER REPORT]
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•
Seems to te be same issue than reported here specifically with cockpit at night: Weird graphical artifacts around cockpit at night
1 Like
Thank you! Indeed, it seems to be the same issue 
Same issue here at night too. Using the beta version.
Specs:
rx 9070 xt
i9 13900k
64gb ram
Well now I think we can say that it is bug, currently present and only limited to beta. Would ve nice if it got logged, or at least acknowledged.
I’d recommend that you also open a bug report with AMD via the Adrenalin app as it may be an issue related to their driver for the new 9000 series gpu’s. Just click on the little bug on the top right on the Adrenalin home screen and fill out the form.
I will do it . But something must have changed, because SU1 is fine and the visual error is in SU2
Only just noticed this as it’s the first night flight on the beta, so can’t say if it was present in the other builds.
RX9070 adrenaline 25.3.1
here is my experience. Maybe it got something to do with night shadows?
1 Like
Have the same issue here with Radeon RX 9070 XT
1 Like
Will do, but like other said, it isn’t present in SU1, if it were AMD driver issue, it would be also there. I think this is on Asobo.
Same issue here, and only occurred in the SU2 beta. AMD 9070 (not XT) graphics card and have the same issue. Only some light sources seem to cause the artifacts. The “headlamp” is one of them.
does it happened to you personally?
Since I created this bug report then yes, it also happens to me.
2 Likes
Same issue here with 9070XT.
Using the lastest 25.4.1 driver still has this issue, so I assume it’s something Asobo has to fix. It’s a bit harder to really pinpoint the cause of it. But probably a shader problem.
Thank you for the bug report.
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
4 Likes