protonscr

[x32/d3d9] 1.9 Blank Screen in Unreal Tournament 3

dxvkclosed d3d9windowsamd proprietary
doitsujin/dxvk#2131 · opened 2021-06-29 by s7hoang · updated 2021-06-30 · 7 comments · github
2 matching comments, n / p to jump
Ss7hoang 2021-06-29 github

I get a blank screen when using the x32/d3d9.dll with Unreal Tournament 3 running on Windows 10. The console works but backspacing text does not remove the characters leaving you with garbled text. This is specifically with version 1.9.

I can confirm it works fine with 1.8.1, 1.7.3, 1.6.1 & 1.5.5 (I stopped here).

A diff of the log files from 1.8.1 and 1.9 shows these lines as the only significant differences (other than version number change):

1.9:
info: VK_EXT_conservative_rasterization
info: shaderStorageImageExtendedFormats : 0

1.8.1:
[empty]
info: shaderStorageImageExtendedFormats : 1

Software information

  • Latest Unreal Tournament 3 version 2.1 (patch 5)

System information

  • GPU: Radeon RX Vega 56
  • Driver: 21.5.2
  • Wine version: N/A
  • DXVK version: 1.9

Log files

apitrace

https://drive.google.com/file/d/1cW4TwcgJ_n6VcyKvq5puqj702ZxgpyAP/view?usp=sharing

Ddoitsujin maintainer 2021-06-29 github

Can you try to record an apitrace?

shaderStorageImageExtendedFormats being 0 is expected since the feature isn't used for D3D9, and we (finally) disabled the feature for llvmpipe compatibility.

Ss7hoang 2021-06-29 github

The issue specifically happens with the release 1.9 d3d9.dll though. When I replace the d3d9.dll file with the one provided in apitrace the issue does not occur.

Does it still make sense to do the api trace in this case?

KK0bin maintainer 2021-06-29 github

Yes.

Ddoitsujin maintainer 2021-06-29 github

The whole point of recording a trrace is to record what the game does so we can replay it with DXVK and (hopefully) see the breakage there.

Ss7hoang 2021-06-29 github

Ok. The instructions said to reproduce the issue which I can't so that's why I asked.

Updated the original post.

Ddoitsujin maintainer 2021-06-30 github

Works fine on RADV, not really sure what the proprietary driver is choking on. Can confirm that it's broken on that though.

Ddoitsujin maintainer 2021-06-30 github

Same problem as #2110.

DLLs