Not sure if it’s been reported before, but this video speaks for itself. Pretty much completely stops me from being able to do anything with UE5.
If you want help you should communicate what you have done to bring up this bug. Without this noone can help you
I am also experiencing this. I had initially assumed it was because my VRAM was dying and I would have to replace my GPU, but after significant stress testing I find the GPU is fine and this only happens in the UE5 editor.
I am not sure what causes it, as it’s happening in pretty basic scenes for me (although limited to the edges of the viewport)
@HAF-Blade, hard to communicate what one has done to bring it up when there is no obvious cause.
However at the very least I can confirm that OP is not alone in experiencing this
2 Likes
@HAF-Blade: this comment is not helpful. If I had any idea whatsoever, I’d have included it. I’m reporting it as an issue since this is for EA / beta feedback. If the dev team has things they’d like me to look into to investigate the issue, I’d be happy to.
This is common in ue4 too.
Generally. Delete the project and start over 
What? No I’m not kidding.
That’s why I moved to a different engine with most projects.
Check your reflection captures. Remove them. Replace them. See if that makes any difference.
If it doesn’t. Move your content folder over to a new project made with an older engine version.
If you are on ue5, then I’m not sure what an older version would be.
Probably, you are just stuck with the bug.
You can try to reset your gfx with windows shift control B or whatever that combo is.
It could potentially stop it in the moment, but it would likely happen again. That’s one thing I hadn’t tried actually.
Also you can disable/enable temporal anti aliasing to test if it stops…
Sometimes in 4 that had results.
1 Like
Sorry for trying to help…
It is common to post things in the forum for many people, without adding any information, so I asked for more.
Possible information would have been if it happens on new projects or with specific lighting settings and so on but it seems that you don’t want help, at least by me.
There actually really isn’t any common element that triggers this behavior.
I once had it happen after removing all the texture from temp while the materials were all being rebuilt.
It’s some sort of rendering issue due to drivers or similar. But it doesn’t happen consistently.
Also on both dx11 and dx12…
The same issue happens for me as well. I haven’t been able to find the exact cause of it however I’ve noticed it almost always happens in projects where much VRAM is used.
1 Like
Restarting the engine did the job for me. thought it would be harder…
Ive been working in ulit mode for a while and when i turned it back to lit, this effect came up. Ive tried turning all my lights in the scene off but the effect remains even with no light. (exept emissive materials). luckily I back up my project on a daily basis, so this might make it easy for me to find the cause if it happens again. ill keep you all updated.
Got this issue pop up in 5.4 preview, never had it before.
Few comments I’ve seen are leading me to believe it’s to do with “Allow Static Lighting” being enabled.
I don’t know if this will help anyone now, but I had a very similar bug and I tracked it down to one line in the project’s DefaultEngine.ini file:
r.ClearSceneMethod=2
I changed it to 1 and the issue is fixed.