protonscr

Mirror's Edge (D3D9): Effective anisotropic filtering differs between PROTON_ENABLE_WAYLAND=0 and =1

dxvkclosed not our bug
doitsujin/dxvk#5793 · opened 2026-07-14 by LucasOe · updated 2026-07-14 · 5 comments · github
1 matching comments, n / p to jump
LLucasOe 2026-07-14 github

I've found what appears to be a difference in effective anisotropic filtering depending on whether Proton's Wayland driver is enabled (PROTON_ENABLE_WAYLAND).

With the default X11/Xwayland path (PROTON_ENABLE_WAYLAND=0), floor textures become noticeably blurrier at grazing angles, consistent with a much lower anisotropic filtering level.

With PROTON_ENABLE_WAYLAND=1, the textures remain sharp as expected.

The in-game anisotropic filtering setting is 16x in both cases (MaxAnisotropy=16 in TdEngine.ini).

Forcing the anisotropic filtering via d3d9.samplerAnisotropy = 16 completely eliminates the difference. After doing so, the PROTON_ENABLE_WAYLAND=0 output matches the PROTON_ENABLE_WAYLAND=1 output.

This makes me suspect that the game's requested anisotropy level is somehow not being honored in the default X11/Xwayland path, even though the game itself is configured for 16x AF.

Screenshots

X11/Xwayland PROTON_ENABLE_WAYLAND=0 Wayland PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_WAYLAND=0 DXVK_CONFIG="d3d9.samplerAnisotropy = 16"
Image Image Image
Image Image Image

Software information

Mirror's Edge (2009, D3D9). I'm using Mirror's Edge Tweaks to set the anisotropic filtering to 16.

System information

  • GPU: NVIDIA GeForce RTX 3070
  • Driver: NVIDIA 610.43.02
  • Wine version: Proton CachyOS 11.0-20260702
  • DXVK version: v3.0.1-6-gc8c49cc156f5044

Apitrace file(s)

  • The trace using X11 (PROTON_ENABLE_WAYLAND=0): Link
  • The trace using Wayland (PROTON_ENABLE_WAYLAND=1): Link

Log files

Ddoitsujin maintainer 2026-07-14 github

The window system has literally nothing to do with anisotropic filtering, DXVK isn't even aware whether you use the Wayland driver or not.

Given that the dxvk.conf override works, i guess whatever you're doing to run the X11 path makes your mod not apply or something.

Ddoitsujin maintainer 2026-07-14 github

Case in point, game requests 4x aniso in your x11 trace. Everything on the DXVK side is working as intended, has to be user error.

Image
LLucasOe 2026-07-14 github

@doitsujin I know this issue sounds crazy. The mod only changes MaxAnisotropy=16 in Documents/EA Games/Mirror's Edge/TdGame/Config/TdEngine.ini, it isn't actually part of the games runtime itself, so it's not possible that it only applies sometimes.

LLucasOe 2026-07-14 github

Maybe you have an idea as to what could cause the requested value to change when using X11 so I can open an issue?

Ddoitsujin maintainer 2026-07-14 github

The issue is most likely that your config file isn't being picked up for whatever reason? I don't know what's happening here, I'm not sitting in front of your PC, but no part of Proton would randomly decide to change sampler anisotropy, especially not on the D3D9 side.

Launch options