Noise/visual artefact in UE5 emissive materials and SkySphere

Hi everyone!

I have just migrated my project from UE4 to UE5. I’ve noticed that all my unlit emissive materials looks very weird in UE5. The same goes for the sky (using a SkySphere). As shown in my attached image, you see how the UE5 version looks terrible.

I don’t know how to approach this issue, where to start? I’ve tried making some changes in my postprocess volume, enabling/disabling Lumen and Nanite, but nothing seem to solve the issue.

So, does anyone here know what may cause the problem and how to fix it?
(many thanks in advance)

2 Likes

It seems to be more than an update of Unreal Engine 5. Do you have a powerful graphics card to run Lumen properly? Are you using the highest settings?

I don’t believe graphic card is the issue. I have a GeForce RTX 3060 Ti 8GB, and my colleague got 3070 Ti and gets the same result. Also, the material looks the same whether Lumen is turned on or off.

Hmm, well in that case, it is very strange. I wouldn’t know where to suggest you start looking. Here are some general things you can try however:

  • Make sure your material settings are set up correctly. In particular, make sure the emissive settings are set to your desired brightness and color.
  • Make sure your lighting settings are set up correctly. In particular, make sure your skylight is set up properly, and that you have a directional light or other light sources in your scene.
  • Make sure your post-processing settings are set up correctly. In particular, check your exposure settings, which can affect the brightness of your scene.
  • Make sure your engine scalability settings are set up correctly. UE5 introduces new features such as Lumen and Nanite, which can affect performance and visual quality. Adjusting the scalability settings can help optimize performance and visual quality for your hardware.
  • Make sure you have the latest version of UE5 installed, as updates can include bug fixes and performance improvements.

I have exactly the same issue.
Did you find a solution for that ?

No, unfortunately not. I still have this issue.