Broken rendering, red visual outlines and glitches on Black Ops II

dxvkclosed not a bug

doitsujin/dxvk#4622 · opened 2025-01-17 by nokia8801 · updated 2025-01-18 · 4 comments · github

Nnokia8801 2025-01-17 github

Red outlines and visual glitches in Black Ops 2.

It's everywhere throughout the game, not just where the screenshot is taken.

Software information

Plutonium Launcher for various old Call of Duty games.

System information

GPU: Intel Arc A750
Driver: Mesa 24.3.3 (Intel Xe kernel driver, instead of i915)
Wine: wine-tkg-git 10.0rc5.r0.gf6f66d11-327 ( TkG Staging NTsync )
DXVK: 2.5.3
Lutris: 0.5.18.r154.ge460565-1
MangoHud: 0.7.2.r146.g0575c8e-1
DE/WM: GNOME 47.3 on Wayland
OS: Arch Linux
Kernel: Linux 6.12.9-arch1-1

DXVK Configuration File

dxgi.enableHDR = False
dxgi.hideIntelGpu = True
d3d11.maxFeatureLevel = 12_1
d3d9.shaderModel = 3
dxvk.deviceFilter "A750"
d3d11.samplerAnisotropy = 16
d3d9.samplerAnisotropy = 16
dxvk.enableMemoryDefrag = True

Additional Info

System Wine is wine-tkg-git compiled with WoW64, Wayland, Staging and NTsync support. Using Lutris to manage everything. In a dedicated Call of Duty prefix just for Plutonium. Other CoD games don't exhibit this behavior, tried Black Ops 1, Modern Warfare 3 and World at War. No red visual bugs on those.

Ddoitsujin maintainer 2025-01-17 github

Please run the game without all those config options, forcing anisotropic filtering can and will sometimes break stuff.

If that doesn't fix things, most likely a driver bug.

Nnokia8801 2025-01-17 github

I just removed d3d11.samplerAnisotropy = 16 and it seems to have fixed it.

Nnokia8801 2025-01-18 github

Should I report to Mesa? Is it supposed to work or is this normal? Since the other CoD games I tried are DX9 and d3d9.samplerAnisotropy = 16 does not produce an error on those. But Black Ops II is DX11 and d3d11.samplerAnisotropy = 16 seems to break it.

Mmbriar 2025-01-18 github

No, forcing anisotropy is a hack and is expected to break in some cases.

Nothing extracted yet.