The only thing that removed the issue was removing the d3d9.dll from my game folder (Disabling the ENB entirely) Using Accumulative Anti-Aliasing in enblocal.iniĭisabling Hardware AA and using an FXAA effect.txt,ĭisabling Hardware AA and not using an FXAA effect.txt Using Edge Anti-Aliasing in the enblocal.ini, Using Multisampling x8 in the Nvidia Control Panel, Setting Negative LOD Bias to Clamp in the Nvidia Control Panel, Using Transparency Anti-aliasing from the Nvidia Control Panel, Using ENB Anisotropic Filtering (With hardware disabled), Using the hardware Anisotropic Filtering, Setting the LOD Bias to 1 in the FalloutPrefs.ini,Ĭhanging my LOD textures back to Vanilla,Ĭhanging LOD Bias to 1 in the enbseries.ini (Not recommended but I wanted to be sure) I have tried many different things to solve this including Apparently some NVidia Chipsets don't actually clamp the Negative LOD Bias to zero, so setting it that way in the Inspector or Control Panel does nothing. Through research, I have found a possible reason is that this is Temporal Aliasing being caused by Bethesda's notoriously bad Negative LOD Bias. This effect has been described in the past as a "Shimmer" or "Flicker" when moving, but I don't know what to call it. Unfortunately, my game has a lot of graphical artifacts or pixels showing up on distant objects whenever I move, and I have yet to find a way to make them go away.
I have recently installed the wrapper ENB in order to add environmental shadows to my game and to allow me more freedom in changing its graphics.
0 kommentar(er)
