Hello,
I am new to Unreal Engine and I’m trying to set up my scene but in the Lit view mode it seems like the reflections and anti aliasing are now working properly. It is probably some settings that I don’t know but can you help me fix this issue? I will post some screenshots to demonstrate this problem.
Note that everything is without any material assigned.
I think you’re running out of VRAM. Does it go away if you restart the editor? What GPU do you have?
also try to update your machine to latest drivers, especially for the GPU
Hey there @MV199866! Welcome to the community! As Clockwork and Doru mentioned this is a graphical issue. After checking your drivers are up to date, verify your system meets requirements, and if everything is good you may need to profile the project.
If that doesn’t work out, you may have another issue that we might have to troubleshoot more directly.
It does not. I tried with diferent scenes and different assets and it keeps appearing. I have a brand new Radeon RX 6700 8gb VRAM
I will try that. Thanks
I have a Radeon RX 6700 8gb VRAM and I’m using the adrenaline Pro drivers. Maybe I’ll try to use the gaming oriented ones.
Thank you. I will try to check all the drivers.
Oh I forgot to ask, did this persist once the shaders finished compiling?
Yes. I took the screenshots while compiling the shaders but it persisted afterwards
try creating a new scene, maybe that one got corrupted somehow
I installed new GPU drivers and the problem persists. It happens in different scenes also. I tried using UE 5.0.3 and it works perfectly but on the newer 5.1.1 that problem keeps appearing in different scenes with different objects.
1 Like
Well, I just figured out the problem has to do with Virtual Shadow Maps. And it happens only when I enabled SM6 on the Targeted Shader Formats. Either way, I’m still figuring out why. Maybe I’m missing some DirectX driver or something?
There’s been a couple hiccups when it comes to the move to DX12/SM6 only for some of the new tech and I’ve seen a myriad of possible issues. Most of them being environmental in nature. I’ll dig up some threads and info for you to glance at, most of it won’t pertain 100% to your issue or VSMs but they are related by the thread that specifically drivers or their setup can fix. To give you a short rundown of a couple that I’ve worked through with other users:
Do you use anything like iCue, Rivatuner, MSIafterburner, or any GPU touching overlay? These can sometimes cause all sorts of rendering artifacts, usually culminating in crashes.
Since you reinstalled your drivers, you may need to reset the settings for them as well (they tend to persist between installations). My frame of reference is Nvidia here so not 100% comparable, but resetting the settings for the card has solved this issue numerous times.
You can check your system’s DX version by running the dxdiag in your windows search. It’s likely up to date though, so it’s often drivers themselves causing issues.
Lastly, I’m seeing a rise of issues now with VSMs and 5.1.1 but couldn’t find a corresponding bugfix that could have made it happen. Some users are Win10 and some Win11 so I don’t think it was a windows DX shift.
Try shifting the bias like this thread here, if it doesn’t effect it at all, you may need to turn of VSMs while this gets sorted if it is indeed an engine bug.
Thank you very much for all of your replies. I found a couple of threads about this issue to and figured out that on recent AMD GPU’s it’s becoming a common issue because (somehow) the drivers are not supporting Shader Model 6.6 and only support 6.5 and that way I can’t turn on SM6. So I guess I’m stuck with SM5 for now and hoping the AMD developers address this issue soon.
Ahhh that would explain why I’m seeing a myriad of issues with AMD cards. I had read they supported SM6 but apparently the minor version updates tripped us up this time. One quick question before we close this out (to help other users with the same issue), are the artifacts gone when you swap shadow mapping? ie for users that aren’t using VSMs but want to use Nanite/Lumen this might be a viable option.
Yes, I noticed the same thing happening in my projects without an answer. I also noticed 5.03 worked fine but since 5.1 and now 5.1.1 it persists. I tested it on a 6800XT and a 6700s laptop GPU, same result. Whenever I TURN ON ray-tracing shadows it comes. I have updated drivers, win10 both machines.