protonscr

After opening 'wow', there is a bug with pure colors.

dxvkclosed windowsprobably not our bug
doitsujin/dxvk#5437 · opened 2026-01-08 by heyzayz · updated 2026-01-08 · 3 comments · github
Hheyzayz 2026-01-08 github

After opening, it becomes a screen with a solid color background. Moving the mouse pointer downwards on the upper half of the screen will restore it. When the minimized window of wow touches the taskbar, it will be fully restored.Restore after deleting d3d9.dll

Software information

Turtle WoW
nampower.dll
no1600x1200.dll
UnitXP_SP3.dll
VfPatcher.dll
Interact.dll
SuperWoWhook.dll
VanillaHelpers.dll

System information

  • GPU: AMD Radeon RX 6800 (16 GB) Intel(R) Core(TM) i5-14600KF 3.50 GHzRAM 32.0 GB
  • Driver:25.12.1~~~new
  • Wine version: Windows 10 Professional‌ 22H2 OS 19045.6691
  • DXVK version: v2.7.1

Apitrace file(s)

I haven't used Apitrace. If need it, please contact me.

https://github.com/user-attachments/assets/a86739b6-ce60-42a9-b3ab-4848995869e2

Log files

WoW_d3d9.log

KK0bin maintainer 2026-01-08 github

I don't fully understand your description and the video you attached is just completely black from start to finish.

This does sound like a problem with the Windows window manager more than anything else. It also happens to be the 3rd Turtle WoW issue now and all of them are on Windows and on AMD GPUs.

Probably duplicate of #5413
or duplicate of #5408

Also:

info: Effective configuration:
info: dxvk.hud = gpuload
info: dxvk.tearFree = True
info: dxgi.customDeviceDesc = AMD Radeon RX 6800
info: dxgi.hideAmdGpu = False
info: dxvk.allowFse = False
info: dxvk.nvapiHack = false
info: dxvk.maxDeviceMemoryAllocation = 256
info: d3d9.deferSurfaceCreation = true
info: d3d9.memoryTrackTest = false
info: dxvk.maxFrameLatency = 1
info: dxvk.logLevel = debug
info: dxvk.pipelineCache = true
info: dxvk.enableGraphicsPipelineLibrary = auto
info: dxgi.forceRefreshRate = 60
info: d3d9.samplerAnisotropy = 4
info: dxvk.enableMemoryBudget = false
info: dxvk.enableStateCache = true
info: d3d9.textureMemory = 256
info: dxvk.enableAsyncCompute = true
info: dxgi.syncInterval = 1
info: d3d9.dpiAware = false
info: dxvk.numBackBuffers = 3
info: dxvk.forceNoFlushing = true
info: dxvk.maxDynamicPipelineMemory = 32
info: d3d9.enableDialogMode = true
info: d3d9.cursor = 1
info: dxvk.enableShaderCache = true
info: d3d9.samplerLodBias = -0.2
info: dxvk.hideIntegratedGraphics = True
info: dxvk.pipelineCacheSize = 0
info: dxvk.trackPipelineLifetime = false
info: dxvk.syncGpu = false
info: dxvk.gplAsyncCache = true
info: dxvk.numCompilerThreads = 0
info: dxvk.enableAsync = true
info: dxvk.useRelaxedBarriers = true
info: dxvk.asyncPresent = true
info: dxvk.latencySleep = false
info: dxvk.preferDeviceLocalMemory = false
info: d3d9.maxFrameRate = 90
info: dxvk.useRawSsbo = True
info: d3d9.maxFrameLatency = 1
info: d3d9.floatEmulation = relaxed
info: dxvk.presentInterval = 0
info: d3d9.strictPow = false
info: d3d9.clampNegativeLodBias = true
info: d3d9.allowLockFlagReadonly = true

What the hell?

Hheyzayz 2026-01-08 github

Thanks for getting back to me.
The video is limited in size, but it can be played after being downloaded
I'll give the method you mentioned a shot.

KK0bin maintainer 2026-01-08 github

The video is limited in size, but it can be played after being downloaded

Oh, I see. That really does look like a problem outside of our control. (Probably the AMD driver)

I'll give the method you mentioned a shot.

What method did I mention?

DLLs