protonscr

[Hammer++] Material rendering swapchains are being overdrawn

dxvkopen d3d9
doitsujin/dxvk#5090 · opened 2025-07-12 by Glebux · updated 2026-04-11 · 2 comments · github
GGlebux 2025-07-12 github

I've applied Hammer++ to a clean Garry's Mod depot. Added dotnet20sp2 - dotnet48, vcrun2003 - vcrun2015 and dxvk as winetricks. Everything works fine except for material rendering, which is done through Direct3D9 swapchains compared to Hammer 4.x. It appears to overdrawn by, what I can assume is, WinAPI

Here's a comparison between Hammer 4.x and Hammer++

Hammer 4.x Hammer++

Software information

Hammer++ 8869 for Garry's Mod

System information

  • GPU: GTX 1060
  • Driver: Proprietary 575.64.03
  • Wine version: wine-10.11.r0.g3e94d124 ( TkG Staging NTsync )
  • DXVK version: 2.7

Apitrace file(s)

(https://drive.google.com/file/d/1Qw2tjl3-TRwJNSG2_5X92GvKBIKF19er/view?usp=drive_link)

Log files

hammerplusplus.log

Ddoitsujin maintainer 2025-07-12 github

Yes, known issue. We don't universally support presenting via GDI so you end up with a Vulkan swapchain on a desktop app, which cannot work.

TThespikedballofdoom 2025-11-10 · hidden on GitHub github

I don't know if wine-cachyos-opt is using this, but I'm getting at least 144fps very stably on it, without any degraded material viewer names/display. (at least after CSMT in the staging tab was turned off, but CSMT didn't do this bug, just skipped some names on top).

Image

Does using apitrace activate that debug info in the corner? I'm hoping I can test on my end if it's using it or not, or just provide useful info for anyone

Operating System: CachyOS Linux
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-3-cachyos (64-bit)
Graphics Platform: Wayland (hammer is running by xwayland afaik however)
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3070 Ti
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C56
System Version: 2.0

wine-cachyos-opt 2:10.0.20251015-1 as reported by pacman -Q
Hammer++ Build 8870 as reported by 'About', launched by WINEPREFIX=/home/spike/.local/share/wineprefixes/hpre /opt/wine-cachyos/bin/wine '/run/media/spike/Widows/Program Files (x86)/Steam/steamapps/common/Team Fortress 2/bin/x64/hammerplusplus.exe

P.S. Ticking 'Show Alpha' in the H++ texture browser seems to be a reliable way to refresh image display, at least whatever Hammer++ tries of it.

(hiding as off-topic, doesn't apply for AMD on wayland, and I really can't understand any of this...)

Launch options