Hello,
I encounter a rare bug from a long time but still present on the game actually.
It’s a shaders bug, I experience this bug from the AMD drivers 22.7.1 update with my AMD Radeon RX 6900 XT.
The 22.7.1 was changed many thing on AMD GPU with Direct3D 11 and OpenGL performance optimisation. (https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1)
Sadly, this update make many big rendering issues, I got the same issue with the Elite Dangerous (https://www.amd.com/fr/support/kb/release-notes/rn-rad-win-22-10-3) game with the same rendering glitch but it’s solved by a collaboration with AMD and Frontiers Development, but this glitch still exists on Tower Unite.
Today the recommended driver version is the 22.11.2.
The temporary solution against this issue, is using the 22.5.1 version or the PRO 22.Q4 version.
For me, the three best solutions is waiting for an DirectX 12 (Agility SDK 1.602 minimum, Unreal Engine 5.1 support this version) release of Tower Unite.
Or waiting an better AMD drivers version.
Or trying fixing the shaders.
EDIT: This bug start only when a new map is loaded.
Anyway, if you need more information, I’m here, I’m also a game developer. (more inside engine and graphics development)
Don’t hesitate to send me more questions.
Cordially Linuxydable
Steps to Reproduce
This bug randomly appear, it’s depend on how the shaders cache is loaded and it’s very depend on how the D3D11 API is called.
Maybe switching many time between maps can load this bug.
What I expected to happen
An normal rendering.
What happened
An broken rendering on the lightning, maybe inside the SSR and Bloom shaders.
