While playing Crysis foliage has flickering shaders(?) or something like that, here's an image example of an extreme scenario.
Crysis, any settings. The object detail setting is the only setting that has a noticable impact on the amount of flickering foliage, setting it to very high is ideal for maximizing reproduction of the effect, if set to high there will be noticably less of foliage flickering (even if the amount of foliage itself is not reduced)
The latest Vulkan beta drivers have a fix for that which hasn't made it into the stable branch yet.
https://github.com/doitsujin/dxvk/issues/267#issuecomment-422794125
@K0bin I see, since I'm using proprietary drivers I don't think I can test that, but if this is true then I'm sure glad to hear it'll get fixed soon.
@Rabcor We are talking about proprietary here. Just a different branch. 410.57 doesn't have the fix. 396.54.06 and 396.54.09 (released today) both have it.
Ah, so it's an nvidia specific issue then?
Indeed. And since 410 series is behind on the vulkan side, it's only been fixed in the vulkan beta drivers as of yet.
It seems that I'm going to have to just wait on the driver update; getting the beta drivers installed on manjaro is a lot harder than it should be. The 396.54.09 fail to build from AUR, it looks like it's gonna be a pain in the ass to troubleshoot. I hope it won't be too long before the 410 series catches up...
@Rabcor You can give my PKGBUILD a try : https://github.com/Tk-Glitch/PKGBUILDS/tree/master/nvidia-dev-all
I just confirmed it to work on Manjaro.
@Tk-Glitch I'll give it a shot, does it require kernel 4.16? or will it work on 4.14?
Edit: failed to build regular version
.../Downloads/pkgbuildnv/pkg/nvidia-dev-tkg/usr/lib/modprobe.d/nvidia-dev-tkg.conf: No such file or directory
==> ERROR: A failure occurred in package_nvidia-dev-tkg().
Edit2: successfully built dkms version, testing...
I have confirmed, the nvidia beta driver solved the issue. Seems like the time to close it.
Most helpful comment
I have confirmed, the nvidia beta driver solved the issue. Seems like the time to close it.