P3D v5.4 P3D V5.4 Heavy graphical glitches at night

[PaulKSim]

Got P3D V5.4 on my recently formatted computer. I installed P3D V5.4 and a Boeing 737 with the FSX default VC with edited textures, nothing more. When turning on landing lights at night, I get some heavy graphical glitches with squares blinking on the screen and extremely low FPS. I already tried turning off Enhanced Atmospherics, Dynamic Lights, and HDR Lighting, but nothing has worked so far.
Problem here

My specs are:
Windows 11 23H2 Build 22631.3880
Intel Core i5-1135G7
16GB RAM
1TB NVMe SSD
Intel Iris XE 8GB VRAM

When flying in daytime, it runs flawlessly at 60FPS with no graphical glitches,. however, when flying at night and turning on landing lights, all those graphical glitches start. I tried everything I could but nothing worked. I couldn't find someone with the same problem on the web, so had to create my own topic about this.

[JonP01]

Unfortunately your GPU would be quite a rare one in use with P3D so unless someone else has specifically solved this previously I would think the only answer might be the hope of a future driver update that resolves it (assuming Intel have been made aware of it). The only other thing I can think of (since I have seen for myself how the night lighting puts a disproportionate load onto the GPU in P3D) is to see if there is some configuration utility for the aircraft that allows you to adjust the night lighting characteristics (for instance, I have this with my A2A bonanza) by disabling the dynamic lighting of the model itself, for instance. This adjustment would of course be something completely independant of what you can achieve in the P3D interface (or editing the cfg).

It does strike me (your image) of the sort of thing I used to see when GPU memory was being exhausted or not properly manage by the driver. No harm (just to experiment) in trying different AA settings to change the way the GPU is used and the load / memory usage.

Edited July 14, 2024 by JonP01

[PaulKSim]

Thank you for your reply, I forgot to say but it happens in every P3D plane, including the default ones. Maybe the only thing I can do is wait for the Intel update. I was in P3D V4.5 before upgrading to V5.4, and in V4.5 I've never had those problems, but I'm looking forward for resolving that.